Three.js Is Quietly Closing the Gap with AAA Game Engines
My Quest to push native Three.js quality match AAA Game Engines
A progress report on bringing AAA lighting to Three.js, stage by stage: octahedral normals cut G-buffer error over a hundredfold, light probe bakes got eight times faster, and most pieces are already in Three.js or in review. The biggest gaps remain in SSR, SSGI, and the pluggable BRDF that ties the cascades together.
SSR is unforgiving of normal error: a ray reflected off a slightly wrong normal lands somewhere visibly wrong at the end of a long trace.
- oooyay
This was written by AI as other comments suggest but I still found it pretty informative. I have a side project that I use three.js on where I ended up having to play with lighting and reflection settings, so this write up was relevant enough for me to understand what the AI was talking about. If anyone is interested: https://portland.ooo-yay.com
- greggman65
The question is why? LLMs will write this stuff without three.js just fine.
See 4 examples I posted yesterday: https://news.ycombinator.com/item?id=50514583
Without three.js the LLMs are more free to write whatever is appropriate for the specific project, instead of having to work around three.js:s architectural decisions when they don't match the thing being made. They further don't need any of three.s infra.
Whether or not those examples are AAA, they are proof IMO that the LLMs can do it without the libraries AND they can do it better without the shackles. Take the GTA like one above, the LLM split the city in 128 triangle chunks and culls them all on the GPU, taking inspiration from Nanite. Any feature you want they will happily recreate in 1 or 2 prompts. And no, you don't need any special knowledge. You just need to ask the LLM to optimize over a few prompts and it will figure out solutions.
I know people will jump to three.js defense because it's well loved and a great library. At the same time, so many people are acknowledging that so many libraries in general are no longer needed. See shopify getting rid of middleware because the LLM doesn't needed it: https://shopify.engineering/back-to-native
It's the same with 3d libraries and game engines. Epic sees the writing on the wall. They can tell that there's much less need for Unreal today than ever and while Unreal is great and provides a ton of tools etc, every day LLMs get better at reproducing all of it, meaning they […]
- dead_hn_theory
Ben! Nice to see you on here.
Neat article. My one comment in all of this is that so much of what makes AAA games and game engines is in the application of much more than just graphics themselves (and very often the graphics of AAA games are "understood" by the time they come out as to be technically uninteresting). And then there is all the texture work and dramatization done by the art department. The title in the article is a better reflection (ahrem) of the subject matter.
- augment_me
Excited about the idea but then immediately off-put by the slop.
If you intend no-one to use what you built except for LLMs, this is fine. If you intend for humans to read it and if you value your ideas in the context of other humans, you can't drop 15 pages of generated material. You can be a Nobel laureate and I will still feel like the text is a massive waste of time because I can't know if you even read it yourself.
- kkukshtel
This would be interesting to read if it wasn't just AI slop. I'm interested in this as an endeavor but if an AI is just writing about it's own progress with some nebulously defined goal, the only thing I care about is "does it work or not".