This aired back in May, but I just learned of this and saw it so apologies if it's a repost. I know we can all see the level of detail and care that goes into the show's visuals and characterizations, but it's cool listening to the creators talk about what it takes to do that.
I'm looking forward to seeing the movie when/if it ever comes state-side.
Hello! This is a game engine I've been building using Opus 4.8 with a little help from Fable 5.
It all started by asking Opus to build me a raytracer. That took about 20 minutes. So I added a kd-tree, GI, and it could render a noisy Cornel Box.
But, then I wanted to visualize things in realtime and I had Opus build out a renderer using Metal since I was on my Macbook Air. Fast forward 2 weeks later and I have this. It's a realtime renderer with shadows, GTAO, screen space reflection, and HDR. The engine also has Lua for scripting procedural generation and game component stuff, ECS, Jolt physics, imGui, joystick support, and a Qt shell that acts like a really paired down "Unity-like" editor. The raytracer hasn't been neglected either. It's been built out as more of a path tracer that's able to render the realtime scenery. The AI actually uses it as an offline renderer to see the visual stuff it's doing. It's all built in C++ using clang as the compiler. The AI wrote the CMake files, all of the code, and it keeps track of all of the tech debt, decisions, and roadmap based on our discussions.
The AI also created all of the assets. The only thing I really am using asset-wise is an .HDR cubemap in the background that I got from polyhaven of some grasslands. All of the trees are built from an L-system grammar. The AI made the leaf card. The "gun" is also AI made -- it's 3 cubes and a tube. I never bothered to ask it to fix the iron sight. It shoots out a yellow cube which can bounce off the trees and tumble around since they have static colliders.
I look forward to seeing what I can do with all of this...