Current preview of my no-dependency real-time PBR renderer, with some over-the-top bloom, ACES tonemapping, FXAA, and IBL

Am I doing this right?

Longest documentation I have written so far. But it's worth it -- it's definitely a step up from my (now legacy) False Color Utility LUTs pack.

Writing documentation always takes longer than I expect.

Even wrote a blog post about my new config format. I'll use this for so much! My header-only test library came in clutch as well for testing.

I wanted a specific config format so I made this. It's v0.1, so don't kill me.

I think the only build system I like are the batch files I write myself for my projects.

Anything that claims to be AI powered should be approached with caution. Most are scams, some are just wrappers and almost all currently are unethical.

I'm still fairly new here. I like:
- Post-production
- Image processing
- Nerding out about colour
- 3D
- Film emulation
- Colour grading
- Low-level languages, like C
- Game dev
- Tool dev
- Photography
- Kendo
🔥 Let's connect if you like any of this or you're just a cool person overall #promosky

Running John Wick through my vectorscope. Look at all the color 😍

Blender's Principled BSDF has got so much better. Their memory management is still not ideal though. Anyway, made this quickly.

Using dx11 is a surprisingly good experience coming from Vulkan and OpenGL.

The only reason the red and white company made that commercial fully AI is because they wanted us to talk about it. And we do. Otherwise it's clearly terrible. I hate it.

Trying something new where I finish my projects instead of perfecting them forever...

All I want for my code editor is to be native, have multi-cursor support, and absolutely no AI.

How cool that every time I open photoshop I get an ad. Even if I check the "Don't show again". Thanks, Adobe! This is why everyone ❤️ you.

Oh how much I love working with the Photoshop SDK -- beautiful docs, helpful comments...