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
bhouston 21 hours ago [-]
I have been a contributor to ThreeJS since 2012 with over 100s of PRs merged.
I use hybrid techniques. I have a swarm of agents and external context where my plans are refined. This series of blog posts is extract from that refined external context. It is generally right as I have refined it over about two months now. Probably a hundreds of prompts and refinements. I am also a 30 year computer graphics veteran and the fifth largest contributor to three.js by commits of all time.
doctorpangloss 19 hours ago [-]
how do you think it compares to babylon? i am finding its support with stuff like babylon-react more robust than plain three.js
what i am saying is, an expressive scenegraph is just as important for what we call AAA quality as, recreating pipelined non-ubershader multipass deferred (modern) rendering
bhouston 19 hours ago [-]
> how do you think it compares to babylon? i am finding its support with stuff like babylon-react more robust than plain three.js
Babylon is great! If you like Babylon-react you may also like React three fiber, which is what Babylon-react was inspired by. I especially like the approach used by Babylon-lite. I would think a three-lite in the future would be amazing, but it is API breaking of course.
giancarlostoro 19 hours ago [-]
You should have lead with the fact you're one of the contributors of threejs because the refined, agents, swam, etc all that just made me tune out.
jkahrs595 19 hours ago [-]
or maybe, just maybe, acknowledge you're the one in the wrong
giancarlostoro 4 hours ago [-]
Wrong about what? I wasn't the original comment, I have no issue with using AI for coding if you're paying attention and working with the output, not just ignoring the output and letting it go out as-is.
12 hours ago [-]
tarcon 11 hours ago [-]
Doesn't render on firefox 161.0b4
neomantra 6 hours ago [-]
Why the haters? Somebody explored a topic deeply and shared the knowledge. They had LLMs help them, probably on both fronts. Would some AI tag have helped? The prose doesn't seem sloppy or too dense.
For me, I'm so used to reading AI tone/density now, it's fine. If I was looking for some deep heartfelt sentiment on Three.js and the community, then maybe then pure human authorship would be heralded.
Anyways, I'm building a Golang game engine. I've built these several times before over 30 years and the state-of-the-art changes and I only kept up with things that were relevant to my domain, such a data visualization and representations like Gaussian Splatting
So I loved seeing this. Yes, I read it with my eyes to learn. Then I told an LLM to read it and explore what would fold well into my engine. It helped fill holes in my knowledge (GI, SSR), as I'm not in the industry and not making scenes. So, Ben, despite the downvotes, keep building and sharing as there are people who will appreciate your manifestations.
matthova 15 hours ago [-]
This is really cool and I learned a lot about it. My only question is with all of that information that you have and given that threejs works so well in browsers why not include some interactive examples in the browser?
I kept scrolling through looking for the payoff and didn’t find it, lol, all the same, I appreciate the technical details and the effort behind that.
bhouston 14 hours ago [-]
Many of the ThreeJS PRs linked usually have live demos in them:
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 can see it has a shelf life. I think the same is true of most of these graphics libraries and game engines from the last 15 years.
bhouston 17 hours ago [-]
My answer to this is simple. Libraries are stores of knowledge / optimization in the end. Yes, an LLM could write everything from the OS up to the application, but that is wasteful in terms of tokens. If you want something be done fast that is not trivial, it makes sense to lean on a library that already does the basics well. And just built your unique aspect on top.
Who wants to re-write a glTF importer, a SSR algorithm, a UV unwrapped, a proper BRDF, etc. That can cost a lot of tokens. Might as well just bring that in and built on top of it your differentiator.
That said, inefficiencies in ThreeJS can come back to bite it long-term. It should aim to get simpler and faster.
If you do not use libraries LLMs will spent extraorbitant amount of tokens
bhouston 5 hours ago [-]
> If you do not use libraries LLMs will spent extraorbitant amount of tokens
Which is a bit of a perverse incentive for LLMs to avoid library usage unless you tell them to. :)
11 hours ago [-]
franciscop 17 hours ago [-]
I've found LLMs will reinvent the wheel in the form of doing manual things when a library already solves it well, and with all the bugs and edge cases that the library was originally created to solve. So you either had a simple enough case where it didn't matter, use a library, or have to iterate with the LLM until you've basically reproduced the original library in your own code.
Disclaimer: not a 3d-specific comment though, more of my general experience.
soniczentropy 13 hours ago [-]
It's nice to see someone else saying this. I have been trying to convince my friends for several months that off-the-shelf engines are a booby trap for indies now compared to finding the right libraries and having your buddy Claude assemble them into a bespoke engine.
I think Unreal is safe for a while just by virtue of having such an ungodly large amount of tools crammed into it that AAA studios actually using those tools are still better off starting from UE5 that their new hires already know than scratch, but for indies, the ship has already sailed imo and most people just haven't noticed yet.
For reference, my hobby graveyard has 20 years worth of crummy self-written game engines running the gamut from baby's first SFML C++ asteroids clone to raycasting vulkan monstrosities in pure Rust. I fed Kimi a list of crates I hand-picked and we planned the engine, then Deepseek Flash did all the work in a couple evenings. By the end of week 2, I had a fixed point deterministic physics engine, networking + client prediction + test suite ensuring determinism, an audio pipeline, immediate and retained mode GUIs, an editor build from them, a hybrid ECS, controller support, a custom hot-reloadable scripting language made to my exact specifications for prototyping, and a whole crate worth of integrations I told the AI it could build to help itself.
All the things I wanted, nothing I didn't, performance screams, all the gamedev parts and knobs and features work exactly the way I want them to. Best part is I actually own this engine and will never have to pay anyone else a dime to use it or beg devs not to do X/Y/Z. Total cost? 13% of a $10 OpenCode subscription's usage for the month. Total features I asked for that the AI could not provide: 0. I would literally never go back to using off the shelf stuff now
slopinthebag 12 hours ago [-]
have fun releasing a game on iOS, android, macos, linux and playstation with your custom engine
wilberton 6 hours ago [-]
There's nothing special about those platforms that an llm can't handle, the dev process is exactly the same - just prompt for it. (And yes, including PS5, point them at the documentation and they'll happily add support)
slopinthebag 4 hours ago [-]
the ps5 and xbox sdk’s are not public. even engines like godot don’t really support it…
11 hours ago [-]
soniczentropy 11 hours ago [-]
That is exactly my point. My games are indie games, I'm never going to release a game on any of those platforms anyway. I don't need support for any of them, so my engine wastes nothing on them. "Steam-only" games aren't even remotely uncommon.
ranguna 10 hours ago [-]
> My games are indie games, I'm never going to release a game on any of those platforms anyway
Speak for yourself, mate. You don't want to release your game on those platforms because of your own decision. Not because they are indie. Plenty of indie games release on all those platforms.
If I'm making a game on, say, unity, I just point my agent at the game and console SDK and say "port please". In your case, you're gonna have to spend a bunch of tokens just to have the agent read your code and the SDK, then a bunch more porting, a bunch more testing and develop-test loop. Hopefully you have a good AI plan to support that endeavor.
slopinthebag 10 hours ago [-]
for consoles they won't even get access to the SDK to do it. i wonder if claude can reverse engineer it?
starkparker 2 hours ago [-]
proprietary console SDKs are enforced by lawyers more than APIs. reverse-engineered SDKs are useful for homebrew (i.e. https://github.com/SvenGDK/SharpProspero for PS5) but that typically requires jailbreaking the console
dead_hn_theory 18 hours ago [-]
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.
Art9681 18 hours ago [-]
Disregard all of the haters here who would have rather you toiled for hours writing something that is easily automated when you would rather spend your time building systems. They will be irrelevant soon enough. But your work will not. None of them would have won awards for prose either. And if they got with the times and used an agent to parse your blog and retrieve the bits that are relevant, no time would have been wasted.
Onward.
nnevatie 5 hours ago [-]
> But your work will not.
Technically it's Claude's work, at least for the blog parts.
That is an unsupported claim. For it to be ai psychosis it would have to be disconnected from reality and not work. But if it does work and it is grounded in reality, then it is just AI-assisted work.
suddenlybananas 12 hours ago [-]
>They will be irrelevant soon enough.
People who write blogposts instead of handing them off to an llm? Are you listening to yourself? Go touch grass.
17 hours ago [-]
Animats 12 hours ago [-]
Nice. Questions:
- How do you do translucency? Depth sort and painter's algorithm in the CPU, order independent transparency in the GPU, or something else?
- How do are large scenes lit and shadowed without a cost of O(objects x lights)?
This is where you tend to need access to a scene graph.
bhouston 5 hours ago [-]
> How do you do translucency?
While a fun technical challenge, in games you just render translucency last and back to front. You can add some distortion when you render it by reading the beauty.
> How do are large scenes lit and shadowed without a cost of O(objects x lights)?
I guess you could do clustered forward lighting. That can be added on top of this work. There is some work on that in ThreeJS.
I am proposing in this work to do light baking for GI, and then normal lights at run-time. I am not actually specifying how you do your GI bake (Ray Radiosity is the best engine in ThreeJS right now) or how you do your run-time lights.
Those are orthogonal to the design of this lighting pipeline.
eska 10 hours ago [-]
First paragraph: G-buffers, screen space reflections. These are considered outdated for years now in computer graphics and modern games have moved away from them.
bhouston 7 hours ago [-]
WebGPU, which is the main API Three.js runs on, does not expose ray tracing at this time. Trying to emulate raytracing via compute shaders is possible but it is too slow to be usable on the majority of the devices. I am trying to make a solution that works on the majority of devices, see:
half of engines are still regular gbuffer deferred, and screen space reflections are basically in every engine still, because a non RT path is required even in 2026 because its just too slow for a lot of people still.
but as a "goal" maybe regular deferred isnt the best target
sph 8 hours ago [-]
Are you from 2040? G-buffers and deferred shading are still very popular.
Oarch 21 hours ago [-]
I love it when a post leaves me dumbfounded and awed like this.
I thought I had the slightest idea about Three.js and computer graphics until this post burst that bubble!
nsainsbury 21 hours ago [-]
Ben - since you're active in the comments here...what motivated you to fill your blog with Claude/AI slop? You're obviously a talented person who has been active in the space for a long time - don't you want to speak with your own voice? Who is your blog even for at this point? Humans don't want to read that - it's immediately off-putting (and in parts quite non-sensical). So who is this written for? For other Claude instances to use?
I don't understand at all people who are immediately surrendering their entire voice, personality, audience, credibility, etc. to Claude? I mean at this point why not just rename the entire site to "Claude's Blog" and tell it to adopt the persona of a Graphics Developer and "Write a post a day".
sansseriff 21 hours ago [-]
If feel like this points to different people having ideas about what a blog is for. Some people will think the written word is downstream of the actual content they want to share (new features in three.js), which for all we know they put a bunch of time into. The blog is like a compile target, even if its describing something the author thinks is meaningful.
Other people think of a blog more like substack or poetry where the whole point is to read what a human wrote.
The lack of editing is central, because it's one person who's responsible for every word. When you click the Publish button you should feel butterflies, at least sometimes, because there's no one to pass the buck to. If someone else wrote the headline, or did a copy edit, or even reviewed what you wrote and critiqued it before it went out, it's still writing, but it is not a blog.
bhouston 17 hours ago [-]
I think that some people value their "voice", and others just "get things done." And by "get things done" I mean I am an engineer and create things. That is what I value. Everyone is different and I am not going to argue your values are wrong.
suddenlybananas 12 hours ago [-]
This is such a ridiculous dichotomy because by half assing it and sending it off to an llm, you're making something worse for others and putting the burden on them.
You're not "getting things done", you aren't even doing the relevant thing here of writing at all.
micromacrofoot 20 hours ago [-]
Some people write because they like to write, some people write as a byproduct of doing cool shit. I can't speak for everyone but it's clear a lot of people posting LLM content are in the latter category.
dorkwood 16 hours ago [-]
[dead]
darig 21 hours ago [-]
[dead]
augment_me 20 hours ago [-]
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.
bhouston 19 hours ago [-]
> If you intend no-one to use what you built except for LLMs, this is fine.
This is a plan for moving ThreeJS towards this new pipeline. It isn't intended for teaching new people how to use ThreeJS in this area, rather it is a detailed and specific implementation plan, intended to be read by fellow computer graphics people, with justifications, that is half way towards being realized. It isn't intended for ThreeJS users to actually use this plan. It is intended to talk to other ThreeJS contributors/maintainers and other 3D experts so they can understand what is being done, and why. So that people can make sense of the stream of PRs I have been submitting.
17 hours ago [-]
wonnage 15 hours ago [-]
...then why post it to HN?
polotics 13 hours ago [-]
I thank the author for having posted this, it's useful information about what progress is being made.
bhouston 15 hours ago [-]
> ...then why post it to HN?
It was upvoted, thus I guess it was accepted by HN none the less. Most posts are not.
bahmboo 12 hours ago [-]
Wow. You add nothing to the context or content and then complain about the form since it's not tailored to your ear. Sad
nnevatie 12 hours ago [-]
Reading the first paragraph, it's clear it is just slop.
Slop has no gravity - why would I use your slop, when I can create mine?
thunky 6 hours ago [-]
Stop it.
kkukshtel 21 hours ago [-]
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".
bhouston 21 hours ago [-]
I am using AI of course but it is a multi month project of which I’ve had over 20 PRs merged in the last two months.
mediaman 19 hours ago [-]
That's great. We'd like to hear what you have to say. Not your thoughts shredded by the woodchipper teeth of an LLM.
Not anti-AI on code, but LLMs are really not good at clear writing, and they are not getting better, so please write your own words if you wish to be heard, even if you feel they are clumsy or if you feel you are "not a good writer."
And even though it may feel like it is a waste of time, or that it can be done quicker with an LLM, the life returns are really high to you to have an audience knowing who you are and how you think about problems, and you're not going to get that with an LLM, so there's no point to writing about it at all if you're not going to be authentic.
rpdillon 11 minutes ago [-]
> life returns are really high to you to have an audience knowing who you are and how you think about problems, and you're not going to get that with an LLM
Ben already has that. I think he's perfectly justified in using AI assistance in this project.
bhouston 19 hours ago [-]
> That's great. We'd like to hear what you have to say. Not your thoughts shredded by the woodchipper teeth of an LLM.
I have written introductions to new features when they have landed, such as this https://ben3d.ca/blog/how-to-use-threejs-native-gaussian-spl..., but this current project is more of a technical justification, tracker, and guide for a major reworking of how ThreeJS does interior rendering that is in-progress. It is more for 3D nerds and ThreeJS contributors/maintainers so that they can understand the larger perspective behind the PRs I am submitting.
dorkwood 16 hours ago [-]
[dead]
pandemic_region 21 hours ago [-]
> the only thing I care about is "does it work or not".
This matches general AI supported work. We have the result but no idea how we got there and nobody learned anything valuable along the way. Shareholders never cared anyway so that's that done with.
sansseriff 21 hours ago [-]
Agreed. But then what do we make of it when a single user moves more rapidly with their fork of a library than the library maintainers. Both are probably using AI, but the maintainer is much more concerned with compatibility, politics and maintainability.
So are compatibility, politics and maintainability the things that differentiate 'slop' from 'not slop' now?
sph 21 hours ago [-]
Please don't waste my time with slop. If you ain't written it, I ain't reading it.
jkahrs595 19 hours ago [-]
rereading this same comment over and over again i feel the same
latentsea 18 hours ago [-]
Reading the same criticism of the same comment I feel tired boss.
jkahrs595 18 hours ago [-]
not sure why my comment disappeared, i swear a lot but i wasn't being malicious
it was essentially "let's all agree to... be quiet"
jkahrs595 18 hours ago [-]
[flagged]
latentsea 16 hours ago [-]
I wish we would. It's like we keep prompting one another in an endless circle, and we can't not respond to the prompts.
rpdillon 7 minutes ago [-]
Some people's slop is better than other people's handwritten blog post.
nnevatie 12 hours ago [-]
This is the right response. Slop goes to my own agent - no wasting human-time reading it.
jackb4040 21 hours ago [-]
As someone who is actually trying to improve Three.js, this is almost pure slop and you may as well have just posted the prompt you used to generate it instead.
bhouston 21 hours ago [-]
> As someone who is actually trying to improve Three.js
Hmm... Since spring, I have contributed Gaussian splats, uv unwrapping, and the light baker and much of material x support as well as ~70 other PRs. I am the fifth largest contributor by commits to threejs. I have contributed since 2012.
dwaltrip 20 hours ago [-]
That is very impressive and quite commendable. However, it doesn't really address the comment you are replying to.
bhouston 19 hours ago [-]
I replied to his claim I wasn't improving ThreeJS. But you mean this part:
> this is almost pure slop and you may as well have just posted the prompt you used to generate it instead
The blog posts references dozens of PRs that I have made, many of which are accepted. It isn't just a random plan created by a single prompt but over 400 hrs of focused work. It was distilled by AI true, but it is a large project that is hard to keep track otherwise for one person. I have to jump from the high level plan down to specific implementation details, profiling, and memory usage while maintain backwards compatibility in each of these PRs to get them accepted.
sansseriff 21 hours ago [-]
Impressive!
sansseriff 21 hours ago [-]
Are the goals in the post even in line with how three.js wants to improve in the future? Its a web rendering engine after all. I love it, but trying to achieve AAA graphics in a javascript ecosystem seems a little odd to me
bhouston 19 hours ago [-]
> trying to achieve AAA graphics in a javascript ecosystem seems a little odd to me
It is quite possible in the way I outline in the post. I have everything prototyped and working, it is mostly just about getting it into ThreeJS in an incremental way that also respects maintainers wishes. It really isn't that much code, mostly reworking what ThreeJS has and replacing the parts that are problematic.
everything that strays from the "easy-to-use, lightweight" headline goals of the project feels like it should go into a project actually pursuing AAA features
if that changes, the biggest blockers to AAA use of three.js, for agents and humans alike, are the documentation and test holes for best practices and footguns in its existing features
there are outstanding requests for just examples, documentation, and/or test coverage of SSR, GI, reflection, Gaussian splats, virtual textures, multi-canvas rendering, lighting, even TSL (happy 2nd birthday, #29829)
it'd be a lot easier to stomach scope-creeping three.js out of its founding principles if that process included bringing support for already implemented table-stakes AAA features up to AAA level. and whatever benefits vibe-coding, or even measured use of AI to improve PRs, can bring to the codebase, they aren't going to be as effective in improving the already strained support and docs for those advanced features
bhouston 19 hours ago [-]
> there are outstanding requests for just examples, documentation, and/or test coverage of SSR, GI, reflection,
I am redoing SSR in fashion - my full analysis has identified that it is pretty broken:
To be clear this AAA quest project is to fix GI, SSR and integrate it with reflection and diffuse probes along with light baking - that is what I am doing. It is a large task but I've made a lot of progress already and nearly every feature is prototyped and working.
starkparker 1 hours ago [-]
you can fix everything you want, just begging you to add docs, tests, examples that agents _and humans alike_ can read and understand. generated posts on your blog don't do that
if you add and expand features but only agents can figure out how to use them, you're going to leave out a chunk of the audience for those tools
Rendered at 18:57:33 GMT+0000 (Coordinated Universal Time) with Vercel.
I use hybrid techniques. I have a swarm of agents and external context where my plans are refined. This series of blog posts is extract from that refined external context. It is generally right as I have refined it over about two months now. Probably a hundreds of prompts and refinements. I am also a 30 year computer graphics veteran and the fifth largest contributor to three.js by commits of all time.
what i am saying is, an expressive scenegraph is just as important for what we call AAA quality as, recreating pipelined non-ubershader multipass deferred (modern) rendering
Babylon is great! If you like Babylon-react you may also like React three fiber, which is what Babylon-react was inspired by. I especially like the approach used by Babylon-lite. I would think a three-lite in the future would be amazing, but it is API breaking of course.
For me, I'm so used to reading AI tone/density now, it's fine. If I was looking for some deep heartfelt sentiment on Three.js and the community, then maybe then pure human authorship would be heralded.
Anyways, I'm building a Golang game engine. I've built these several times before over 30 years and the state-of-the-art changes and I only kept up with things that were relevant to my domain, such a data visualization and representations like Gaussian Splatting
So I loved seeing this. Yes, I read it with my eyes to learn. Then I told an LLM to read it and explore what would fold well into my engine. It helped fill holes in my knowledge (GI, SSR), as I'm not in the industry and not making scenes. So, Ben, despite the downvotes, keep building and sharing as there are people who will appreciate your manifestations.
I kept scrolling through looking for the payoff and didn’t find it, lol, all the same, I appreciate the technical details and the effort behind that.
https://github.com/mrdoob/three.js/pull/34944 https://github.com/mrdoob/three.js/pull/34991 https://github.com/mrdoob/three.js/pull/35480 https://github.com/mrdoob/three.js/pull/35052 https://github.com/mrdoob/three.js/pull/35174 https://github.com/mrdoob/three.js/pull/35430 https://github.com/mrdoob/three.js/pull/35429 https://github.com/bhouston/three.js/pull/171
But the full payoff will be in a couple weeks time as everything lands and some of the more complex ones that tie everything together land.
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 can see it has a shelf life. I think the same is true of most of these graphics libraries and game engines from the last 15 years.
Who wants to re-write a glTF importer, a SSR algorithm, a UV unwrapped, a proper BRDF, etc. That can cost a lot of tokens. Might as well just bring that in and built on top of it your differentiator.
That said, inefficiencies in ThreeJS can come back to bite it long-term. It should aim to get simpler and faster.
I've written about this here: https://ben3d.ca/blog/coding-agents-underestimate-the-cost-o...
If you do not use libraries LLMs will spent extraorbitant amount of tokens
Which is a bit of a perverse incentive for LLMs to avoid library usage unless you tell them to. :)
Disclaimer: not a 3d-specific comment though, more of my general experience.
I think Unreal is safe for a while just by virtue of having such an ungodly large amount of tools crammed into it that AAA studios actually using those tools are still better off starting from UE5 that their new hires already know than scratch, but for indies, the ship has already sailed imo and most people just haven't noticed yet.
For reference, my hobby graveyard has 20 years worth of crummy self-written game engines running the gamut from baby's first SFML C++ asteroids clone to raycasting vulkan monstrosities in pure Rust. I fed Kimi a list of crates I hand-picked and we planned the engine, then Deepseek Flash did all the work in a couple evenings. By the end of week 2, I had a fixed point deterministic physics engine, networking + client prediction + test suite ensuring determinism, an audio pipeline, immediate and retained mode GUIs, an editor build from them, a hybrid ECS, controller support, a custom hot-reloadable scripting language made to my exact specifications for prototyping, and a whole crate worth of integrations I told the AI it could build to help itself.
All the things I wanted, nothing I didn't, performance screams, all the gamedev parts and knobs and features work exactly the way I want them to. Best part is I actually own this engine and will never have to pay anyone else a dime to use it or beg devs not to do X/Y/Z. Total cost? 13% of a $10 OpenCode subscription's usage for the month. Total features I asked for that the AI could not provide: 0. I would literally never go back to using off the shelf stuff now
Speak for yourself, mate. You don't want to release your game on those platforms because of your own decision. Not because they are indie. Plenty of indie games release on all those platforms.
If I'm making a game on, say, unity, I just point my agent at the game and console SDK and say "port please". In your case, you're gonna have to spend a bunch of tokens just to have the agent read your code and the SDK, then a bunch more porting, a bunch more testing and develop-test loop. Hopefully you have a good AI plan to support that endeavor.
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.
Onward.
Technically it's Claude's work, at least for the blog parts.
That is an unsupported claim. For it to be ai psychosis it would have to be disconnected from reality and not work. But if it does work and it is grounded in reality, then it is just AI-assisted work.
People who write blogposts instead of handing them off to an llm? Are you listening to yourself? Go touch grass.
- How do you do translucency? Depth sort and painter's algorithm in the CPU, order independent transparency in the GPU, or something else?
- How do are large scenes lit and shadowed without a cost of O(objects x lights)? This is where you tend to need access to a scene graph.
While a fun technical challenge, in games you just render translucency last and back to front. You can add some distortion when you render it by reading the beauty.
ThreeJS supports OIT but it costs a lot and unless you are doing specialty visualization, it isn't worth it: https://threejs.org/examples/?q=transp#webgpu_oit
> How do are large scenes lit and shadowed without a cost of O(objects x lights)?
I guess you could do clustered forward lighting. That can be added on top of this work. There is some work on that in ThreeJS.
I am proposing in this work to do light baking for GI, and then normal lights at run-time. I am not actually specifying how you do your GI bake (Ray Radiosity is the best engine in ThreeJS right now) or how you do your run-time lights.
Those are orthogonal to the design of this lighting pipeline.
https://ben3d.ca/blog/how-aaa-games-light-indoor-scenes
https://ben3d.ca/blog/aaa-quality-on-a-web-budget
but as a "goal" maybe regular deferred isnt the best target
I thought I had the slightest idea about Three.js and computer graphics until this post burst that bubble!
I don't understand at all people who are immediately surrendering their entire voice, personality, audience, credibility, etc. to Claude? I mean at this point why not just rename the entire site to "Claude's Blog" and tell it to adopt the persona of a Graphics Developer and "Write a post a day".
Other people think of a blog more like substack or poetry where the whole point is to read what a human wrote.
A blog is the unedited voice of a person.
The lack of editing is central, because it's one person who's responsible for every word. When you click the Publish button you should feel butterflies, at least sometimes, because there's no one to pass the buck to. If someone else wrote the headline, or did a copy edit, or even reviewed what you wrote and critiqued it before it went out, it's still writing, but it is not a blog.
You're not "getting things done", you aren't even doing the relevant thing here of writing at all.
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.
This is a plan for moving ThreeJS towards this new pipeline. It isn't intended for teaching new people how to use ThreeJS in this area, rather it is a detailed and specific implementation plan, intended to be read by fellow computer graphics people, with justifications, that is half way towards being realized. It isn't intended for ThreeJS users to actually use this plan. It is intended to talk to other ThreeJS contributors/maintainers and other 3D experts so they can understand what is being done, and why. So that people can make sense of the stream of PRs I have been submitting.
It was upvoted, thus I guess it was accepted by HN none the less. Most posts are not.
Slop has no gravity - why would I use your slop, when I can create mine?
Not anti-AI on code, but LLMs are really not good at clear writing, and they are not getting better, so please write your own words if you wish to be heard, even if you feel they are clumsy or if you feel you are "not a good writer."
And even though it may feel like it is a waste of time, or that it can be done quicker with an LLM, the life returns are really high to you to have an audience knowing who you are and how you think about problems, and you're not going to get that with an LLM, so there's no point to writing about it at all if you're not going to be authentic.
Ben already has that. I think he's perfectly justified in using AI assistance in this project.
I have written introductions to new features when they have landed, such as this https://ben3d.ca/blog/how-to-use-threejs-native-gaussian-spl..., but this current project is more of a technical justification, tracker, and guide for a major reworking of how ThreeJS does interior rendering that is in-progress. It is more for 3D nerds and ThreeJS contributors/maintainers so that they can understand the larger perspective behind the PRs I am submitting.
This matches general AI supported work. We have the result but no idea how we got there and nobody learned anything valuable along the way. Shareholders never cared anyway so that's that done with.
So are compatibility, politics and maintainability the things that differentiate 'slop' from 'not slop' now?
it was essentially "let's all agree to... be quiet"
Hmm... Since spring, I have contributed Gaussian splats, uv unwrapping, and the light baker and much of material x support as well as ~70 other PRs. I am the fifth largest contributor by commits to threejs. I have contributed since 2012.
> this is almost pure slop and you may as well have just posted the prompt you used to generate it instead
The blog posts references dozens of PRs that I have made, many of which are accepted. It isn't just a random plan created by a single prompt but over 400 hrs of focused work. It was distilled by AI true, but it is a large project that is hard to keep track otherwise for one person. I have to jump from the high level plan down to specific implementation details, profiling, and memory usage while maintain backwards compatibility in each of these PRs to get them accepted.
It is quite possible in the way I outline in the post. I have everything prototyped and working, it is mostly just about getting it into ThreeJS in an incremental way that also respects maintainers wishes. It really isn't that much code, mostly reworking what ThreeJS has and replacing the parts that are problematic.
if that changes, the biggest blockers to AAA use of three.js, for agents and humans alike, are the documentation and test holes for best practices and footguns in its existing features
there are outstanding requests for just examples, documentation, and/or test coverage of SSR, GI, reflection, Gaussian splats, virtual textures, multi-canvas rendering, lighting, even TSL (happy 2nd birthday, #29829)
it'd be a lot easier to stomach scope-creeping three.js out of its founding principles if that process included bringing support for already implemented table-stakes AAA features up to AAA level. and whatever benefits vibe-coding, or even measured use of AI to improve PRs, can bring to the codebase, they aren't going to be as effective in improving the already strained support and docs for those advanced features
I am redoing SSR in fashion - my full analysis has identified that it is pretty broken:
https://ben3d.ca/series/fixing-threejs-ssr
To be clear this AAA quest project is to fix GI, SSR and integrate it with reflection and diffuse probes along with light baking - that is what I am doing. It is a large task but I've made a lot of progress already and nearly every feature is prototyped and working.
if you add and expand features but only agents can figure out how to use them, you're going to leave out a chunk of the audience for those tools