I don't often post about our game Enshrouded but seeing the great work our rendering team has done over the last years and the last patch is something to behold. Visually absolutely stunning. Especially since it is a voxel game which comes with its own challenges.

good talk, and some good solutions, despite the fact that i never hear about "Enshrouded", but could be just me & it is known game. The tech behind it sounds interesting.
Note: there are few more talks in the playlist about the same game renderer.
www.youtube.com/watch?v=57F1...

Those detailing tools makin' me weak in the knees. Direct painting workflows FTW!

The #Enshrouded building system really is in a class by itself.

youtu.be/jXPG8Od_PzM?...

Writing a Vulkan backend is a never ending "But wait there is more" meme of awfulness. Even with using 4 example from Github und AI.

Currently porting my App to Linux with Xlib and Vulkan and oh my god. Vulkan fits right into the usual Unix APIs. All orthogonal designed APIs are there but absolute no diagonal APIs. So just writing the code to pick a device and queue family turns into code screaming for bugs and inconsistencies.

This holiday season, give yourself the gift of wondering whether you'd enjoy working on the Playstation graphics stack and making life better for graphics programmers, because we're hiring for our rendering APIs! job-boards.greenhouse.io/sonyinteract...

Graphics Programming Conference 2024 talks are up. Looking forward to learning the new Tomasz magic :) www.youtube.com/playlist?lis...

Being specified down to environment, language and limits is still an underestimated feature of C and major contributor to its success. Ironically the biggest downside is that often not specified enough. Yet no "modern" language did the same thing and rely on their implementation as "specification"

After a month of debugging, finally found the bug that caused cloth to explode. Biggest hint was lag but was expecting it on the client side but turned out in the end it was server lag of upwards of 250ms causing jumps that required teleport (in place) and a reset of cloth to skinned position.

Decided for my own code to go full embedded mission critical flight software c code with additional own restriction on top. First gathering constraints and ensuring these are kept is very satisfying. Never liked unit test* but the feeling of control using asserts and validation conditions is great.

Rereading the ourmachinery blog and have to hold my self back not to start writing my own engine. Lot of ideas what I would like to do based on experience.

Yet given little time and how long it even takes me to (re)write just an sql viewer. Probably not a good idea to start a big project like that.

Finished the rewrite for my sqlite viewer: github.com/vurtun/tau?t... to only use fixed size arrays. No arena allocators/dynamic data structures.

Code got simpler since everything is constraint and more assert can be added for validation. But required more thought how to mitigate hitting limits.