My Windows desktop had its power supply unit crap out like a month ago, so I was forced to use my Linux laptop as my daily driver. I still haven't put my replacement power supply in my desktop. I love Linux now. it's just great

I'm not that excited about Claude Fable honestly. I don't want to spend way more money for what Sonnet 5 already does reasonably cromulently. Maybe as a thing that can break through on tougher issues only, perhaps. I want efficient cheap AI tools, not lumbering beasts that drain my wallet.

order of the sinking star is a pretty great puzzle game with some other confounding unfortunate circumstances

stop caring what other people think about what the right way to write software is if you're doing it wrong, you'll know, because it will suck more. make it suck less. that's all there is to it (this also means - don't foist your opinions onto others. what works for you is not what works for them)

1024x1024x1024 terrain generation distance on my desktop, in seconds it's more likely than you think

This was a beach to optimise

The jqwik incident really boils down to a few things: - open source projects are provided as-is and you can't hold the maintainer liable for breaking your stuff - however, a maintainer intentionally breaking your stuff when you're not looking is absolutely a violation of trust

genuinely can't believe that people think it's OK to fantasise over threats of violence to the rsync maintainer over the most mild-ass LLM use. Whatever moral system you think you have, it's so incredibly fucked up, get help for the love of god please stop posting on the internet

officially announcing that i am bored of ai takes and that a lot of people need to go outside me included i need to go outside more

claude code is nice in moderation. helps me properly unwind in my free time while still being able to make a little progress on my projects, whether that's helping out with getting my plans into documents, adding small features, or doing well scoped tasks it's also nice to take a day to read code

i can simply only apologise for the way the people i agree with choose to poorly behave themselves on the internet

honestly very glad i did the terrain generator before the renderers, because this is the best Lorem Ipsum content you could ask for

Finally set up Claude to run in a super-locked-down container so we can skip the permission fatigue (which inevitably would've caused me to accept bad commands). aka: I gave my Claude guy their own room. (A basement room, padded cell, locked door, and I feed them through a slit in the door).

goodnight world

bevels + new terrain generation = win

higher render distance

Pair programming with Claude on laying out chunks in a more cache-friendly way in memory & reducing memory overhead/bandwidth of terrain generation. Now boasting fast startup time and very smooth & consistent frame pacing.

Auto exposure, courtesy of Claude running in the background while I do other things - still needs a lot of tuning, but I'll do that later when I can give it more attention.

goodnight

Accumulating multiple samples per pixel in the ray traced path now. (Not TAA, no reprojection - just to get cleaner reference stills.)

If you think you can tell AI generated stuff from human stuff: 1) No, you can't. I've seen so many people lash out at actual artists for using AI when they _haven't_. You're hurting the people you're trying to evangelise for. None of us want it. Stop.

As an aside; since switching from rust_gpu to Slang, shader development has been going a ton smoother. I suppose it really does help to use something that is both reasonably complete and reasonably documented after all. (I never got to the point of sharing any Rust code because of the toolchain.)

Now rendering albedo, normal and combined AO/emissive maps in the ray tracing path! Still no water pass as that's more complex to pull off. Next up: going to start setting up a proper tonemapping pipeline and get some antialiasing in there.

Building the ray tracing acceleration structure on the fly from actual voxel data.

One year ago; the original ray-traced lighting solution I was tinkering with for Cavey. Funny that exactly one year later, I'm still playing with rays.

2048x512x2048 GPU voxel ray tracing renderer test.

Oh shoot I guess it’s time to follow it up with something more profound…. lets see…. WGSL is terrible and badly equipped for anything GPU driven. But I still haven’t found a shader language I like, so maybe that makes it relatively less bad. Subscribe for more insightful video essays or whatever.

Anyhow, for my first post… Having an opinion about AI is not a replacement for a personality trait. It’s a complex, nuanced, multifaceted issue with real world weight. I don’t care *what* your opinion is - even in my field, reasonable people don’t agree on fundamentals here - I care about *why*.