Julien Koenen

@OlexGameDev Cool! And good job doing you own memory manager.

@motor3d You are right. Thank you for advice. :) I've cleaned up the unnecessary copies.

It's nice to have my own GPU allocator. Writing a custom ImGui is easy. Here is a view into GPU images that are involved in my pipeline. A raytraced pass produces color and glow values, then a set of mipmaps for the bloom, and intermediary for FXAA pass in sRGB, and a depth buffer for the UI pass. I allocate out of 256MB blocks. (Configurable.) Everything is doubled because I have up to 2 frames in flight.

@OlexGameDev But only one frame is executing on the gpu at any point in time - so what exactly do you need to wait for?

@motor3d Otherwise you have to block and wait until GPU is done with the previous frame.

@voxagonlabs Very cool! Does it support late join?

Adding multiplayer to this game has been far more complicated than making the entire engine for single player. This is a project that spans 3+ years and dozens of developers and now it's finally time to let it out in the wild!

You can ignore the science, but you can't ignore the consequences of ignoring the science.

@EskilSteenberg Pretty similar to cpu features (avx ..) not sure why this is surprising

Spot the logical problem with Vulkans design: -Shaders are const assets that can be compiled offline. -Detect GPU capabilities at run time. -Make sure your shaders take advantage of GPU Capabilities.

@wookash_podcast I love the podcast - keep up the great work!

I made a reply video to convey how I feel about this comment

After nine years of development, meshoptimizer has reached its first major version, 1.0! This release focuses on improvements in clusterization and simplification as well as stabilization. Release announcement with more details on past, present and future is below; please RT!

@voxagonlabs @GabeRundlett Looking forward to your talk - and maybe a quick chat - I'm a huge fan!

Next week I'll go to Breda for the Graphics Programming Conference. @GabeRundlett and I will give a presentation on Tuesday about raytracing voxels, covering methods used both in Teardown as well as our new engine. If you are also there and would like to meet up, let me know!

youtube.com/watch?v=3KEYXq… #Enshrouded Update 7 is live now! Real time simulated water + lots of improvements.

With the end of October looming on the horizon, it was time for us to put on our wellies and wade into the shallows to bring you some well-deserved updates on Enshrouded: Wake of the Water! 💦

youtube.com/watch?v=I4qv3H… news about our next #enshrouded update

#water-simulation-rendering-in-enshrouded" target="_blank" rel="nofollow noopener">graphicsprogrammingconference.com/2025/#water-si… My collegues Andreas and Simon will talk about the new Water Simulation&Rendering in Enshrouded at the great #GPC2025

Tickets are up! graphicsprogrammingconference.com/tickets/

@matiasgoldberg Crying over here with players recreating Minas Tirith with thousands of tiny light sources :-)

And artists must be continuously taught about performance-aware methods. Of course it's hard when art is outsource and AAAA projects are huge. UE5's problem is that its material system can easily lead to bloat if not kept in check, and that remains unacknowledged. [3/3]

While Sweeney isn't wrong (devs not caring for perf -> perf sucks); UE4/5 prioritized artist-driven materials. They're a blessing for expressing artistic vision; but it *sucks* for performance. If you want a game to run fast, from day 0 appoint a savvy tech lead. [1/3]

@idSoftwareTiago Fantastic! Thank you for that!

We'll be presenting at GPC more details about #idTech8

@rfleury @neogoose_btw Sure, I get that - I just disagree. In the majority of cases dividing by zero is a bug in my code.

@motor3d @neogoose_btw The whole point of what I’m saying is that in the majority of cases, the fix is to default to zero.

omfg unsigned integers are the most important thing ever existed. If only you’d know how many crashes happened because APIs like “max_threads” accepts int instead of unsigned int. Having in your type system ability to ban negative numbers is crucial, and having unsigned easily accessible via shortcuts like u32 is alone a solid reason to migrate to Rust/Zig

@rfleury @neogoose_btw I'd rather find my bugs and fix them - so exceptions please!

Division by zero should simply produce zero. always. If you wanted something special to happen (especially a damn exception), then you should just have to check for a zero divisor. The vastly common case is that you want to gracefully decay to some default, zero being the most useful one.

@rfleury @wookash_podcast @TheGingerBill sure, maybe better type annotations are even better - I just have to use what I can here - and in that context signed vs unsigned is better than nothing.

@motor3d @wookash_podcast @TheGingerBill It’s very much not a good way to do that. What you want are just type annotations which go far beyond “unsigned”. There is no reason this should be coupled with what ops are generated.

„Hey @rfleury, what would you remove from C?” This was wild! It’s a snippet from our discussion C language with @rfleury and @TheGingerBill! It’s unclear whether it will be out this Saturday or next one… but it’s coming! Soon!

@rfleury @wookash_podcast @TheGingerBill Disagree in the last point. Its a good way to document intended use in apis. Having an additional set of explicit ops would be interesting though.

Somehow this video unfortunately made it to PLT Twitter, and since they lack inference abilities & because the clip omitted all context, some clarifications: - I am not saying you only allow signedness (or only unsignedness). - I am saying signedness should live on the *op* rather than storage types—same as with atomics. I do not think atomic type operators are ever useful. I just want to write the explicit atomic operations in code. Same when signedness is important. Just let me write the ops I want the CPU to do. - Using unsignedness as a way to “disqualify negative values” is absolutely awful and is not a good example of type systems being used to make things “safer” or more robust.