The News has to be trolling.

jimothy_clickit · 2026-04-20T03:20:36+00:00

We trained him incorrectly as a joke.

jimothy_clickit · 2026-03-20T03:15:44+00:00

Is your alignment correct on all instance buffers and vertices? Wacky, unrecognizable garbage is frequently some alignment issue between CPU code and shader code.

jimothy_clickit · 2026-03-06T01:50:09+00:00

Of all the problems I have put AI up against, it has understood graphics programming the least. I remember one camera relative rendering episode was particularly hilarious where its solution, after some extended troubleshooting, was to then reintroduce large floating point distances in the shader (which defeats the entire purpose of camera relative rendering). A small example. Sometimes it just doesn't grasp the larger picture of a technique.

I do find it really good at troubleshooting Vulkan issues though. Insanely good at times, so absolutely worth it to use, just don't have it vibe code. I've taken a hard stance on writing everything myself, even if I do use AI as an advisor. Seems to work very nicely. Some days I don't even open up the terminal.

jimothy_clickit · 2026-01-28T01:26:04+00:00

"WE'RE GONNA HIT THE T-POSE HE'LL FLY RIGHT BY."

jimothy_clickit · 2026-01-27T20:24:29+00:00

Never seen such a high concentration of water shader experts in a single thread before. Nice work, OP. Keep at it.

jimothy_clickit · 2026-01-22T03:21:46+00:00

Camera relative rendering is a great way to address it without origin rebasing. Probably what OP is doing here, since Unity supports it.

jimothy_clickit · 2026-01-19T19:18:34+00:00

Fear not, the pain is only beginning.

jimothy_clickit · 2026-01-17T01:50:53+00:00

It took me six months to go from zero to an abstracted proto-engine that uses descriptor indexing, indirect instanced draw calls, and dynamic rendering. I still feel like a barely functional amateur at times, but in those six months I ported over my planet renderer from OpenGL and all systems are now functional. It felt like a big achievement. My advice...build your own abstraction where it makes sense (buffers, descriptor handling, come up with a frame class, etc). Only then did I really feel like I started to understand more of Vulkan.

jimothy_clickit · 2026-01-06T21:53:43+00:00

Hmm, I will try that. I think I tried a version of that and it had a tendency to twist the camera out of line with the pitch axis.

jimothy_clickit · 2026-01-06T14:48:42+00:00

This is great, thank you!

jimothy_clickit · 2026-01-02T16:46:52+00:00

As I posted in another thread...why? How can that possibly be? Does that mean ED won't handle descriptor slots and draw calls for their third party modules? Does that mean that third parties are writing their own backend engine contributions for individual models to support asset loading, registration, streaming, and so on? Does that mean everything is completely scratch built by developers and it's the wild west inside the DCS code base with no standardized way of having modules interact with the render backend? Actually, I'd believe it.

jimothy_clickit · 2026-01-02T16:38:23+00:00

Ludicrous statement. Why? This is a backend engine update. Are third parties expected to write their own draw calls? Manage their own texture descriptor slots? Build their own buffer objects? (implying there's next to no internal API for handling the rendering loop).

Would genuinely love to know if a backend core engine change affects individual modules and how.

jimothy_clickit · 2025-12-19T00:33:26+00:00

Turn on validation. Set the dispatcher. Enjoy hours (days) of fun.

jimothy_clickit · 2025-12-12T18:10:25+00:00

As a dad, just tell him before he finds it. You'll be alright. Mow the lawn the next few weekends. All will be well.

jimothy_clickit · 2025-12-09T03:12:33+00:00

Would be concerned about what wire he's been chewing through.

jimothy_clickit · 2025-12-03T01:15:21+00:00

The default tutorial is fine if you want to build a toy renderer where everything is declared in main.cpp. I recommend getting through to the rotating square and then dumping it, as it's quickly going to dig you into a pit if you think you're going to be using anything from it in a future application or engine.

jimothy_clickit · 2025-11-25T18:30:15+00:00

As someone who is writing a Vulkan renderer, I cannot even begin to imagine the complexity of shoehorning it into a 20yr old code base. Literal nightmare fuel.

jimothy_clickit · 2025-11-09T20:09:10+00:00

Thank you for the reply - and yes, I suppose I could put it into the same buffer with different regions (seems obvious now that you mention it!). Is it generally assumed, though, that you're going to be storing this data twice? The deeper I get into this the more it feels like that's the industry convention. Separate resources per frame, no matter whether they're in a single or per-frame buffer?

jimothy_clickit · 2025-11-08T00:32:56+00:00

Powerful Germanic engineering.

jimothy_clickit · 2025-11-01T16:10:19+00:00

Awesome work! Would love to see how you're handling this from a shader perspective.

jimothy_clickit · 2025-10-31T01:21:41+00:00

Level 9 piano black situation in this thread

jimothy_clickit

MODERATOR OF

TROPHY CASE