Sébastien de Graffenried

Neat, going to update my dynamic array too, thanks!
Also, what a nightmarish bug. Glad you could catch it

Damn, that effect looks so cool on that artwork! Love it

YouTube video by Sébastien de Graffenried Adding "God powers" to the game

Streaming the addition of a new mechanic "God powers".

www.youtube.com/watch?v=scFx...

Oh sweet! Going to watch it tonight

Since posting my debugging tale, I've learned more:

- I can use an NVIDIA stats HUD to show dynamic changes to the GPU clock rate (which are very large).

- A D3D12 method, SetStablePowerState, is available to disable these dynamic changes.

Some numbers below!

1/

Interesting, I was wondering about how to do that recently. I assume it’s mostly BIOS settings?

The blog post about the upcoming experimental sokol-gfx Vulkan backend is up:

floooh.github.io/2025/12/01/s...

(as always I'll need to do a couple more edits to fix typos and repetitions but first I'll need some food intake)

Store fees over 10%

congrats!

HORSES cover with a banned from Steam logo

Our upcoming game HORSES was preemptively banned from Steam, with no path to appeal. The game will still launch next week on December 2nd and will be available on EGS, GOG, Humble, and Itch for $4.99. Here is a detailed FAQ covering what happened: horses.wtf/BannedFromSt...

Here's some cute bounding box functions for 2D shapes. A longer list here: iquilezles.org/articles/bbo...

Do you already have a present 🧑‍🎄? It is only a little more than a month away!
In other news, I managed to get tracks in the snow working 🥳
It just broke a few other systems, but I guess I can fix those 😅
I'm really happy how this is starting to look!

#gamedev #raylib #cozygame #puzzlegame

Quite interesting, I hit something similar the other day but couldn't find the reason.
If the stack was the same size for every platform, stack overflow could be caught while developing. I'll see if I can set the stack size to the same (modest) size for all platforms in my engine

damn right

nice!

Exciting! Custom engine I assume?
What's your approach to level editing, do you use a specific tool?

GitHub - Geolm/bc_crunch: tiny dependency-free lossless compressor for BC/DXT texture streams (C99, ~700 LoC) tiny dependency-free lossless compressor for BC/DXT texture streams (C99, ~700 LoC) - Geolm/bc_crunch

Just released bc_crunch: a tiny (~700 LOC), C99 library for lossless BC1/BC4/BC3/BC5 compression.
One .c/.h pair, no deps, no malloc
GPU-ready output
Zigzag + delta + popcount/dictionary tricks
Tested
Perfect for games, procedural assets, streaming textures.

github.com/Geolm/bc_cru...

Looks awesome, can’t wait to try. Thanks for sharing!

a game data editor that looks suspiciously like a spreadsheet

Streaming some tools programming on youtube in a bit: www.youtube.com/@seb_degraff
I'll add features to the in-game editor that the game designer requested!

For more complex cases like returning a dynamic array from a function, arenas are a simple and easy to use solution. That said you do have to put in the effort to make yourself a nice codebase for C to become enjoyable, which is both a curse and a blessing

vec2_t points[3] = { angle_to_dir(0), angle_to_dir(TAU / 3), angle_to_dir(2 * TAU / 3) }; for (int i = 0; i < countof(points); i++) { // ... }

C# for sure improved a lot with regard to memory management. I would still challenge the "almost always less work than using an unmanaged language" part though.

For this (arguably simple) example, it would look basically the same in C:

My fellow Europeans, I'm once again asking you to write or call your EU representatives and tell them this is unacceptable. They're essentially selling our sensitive data to companies, effectively destroying our privacy and risking our digital well-being.

Check the site!

fightchatcontrol.eu

Oh, I think I like the 1st one because you can clearly see the dispenser and the belt where the crates should be put. So you instinctively understand that the bot should transport crates from A to B, and that’s already compelling to me

I think I prefer the first one, but not entirely sure why. Perhaps because it shows better the grid based nature of the game, and has visually interesting props?
The idea of making the bot bigger and focusing on fewer things is good though, I’d say

HEADLINE - Double Fine shocks with unprecedented development transparency! Wait, what do you mean we do this all the time? ....33 episodes? Who has time for that in this day and age!? Thankfully,… The Making Of Double Fine's Keeper

🚨 "The Making of Double Fine's Keeper" is now available! 🚨

Many of you have been asking for this one; we're happy to say the cameras continued to roll here at the studio during Keeper's development. Come see how this very special game came to be, from the team themselves! 😊

youtu.be/1OOfRTfMnx0

I see. Never used rust or Julia. Used C# where references (ref keyword) work like ref arguments in cpp, and are not allowed in struct or classes.
Using C these days and appreciate the simplicity!

For me the point of ZII is to make things simpler and more straightforward. No need to think about constructors. "Initialize" a whole array at once to a valid state with just = {} or memset to 0.

Works well when composing data structures too, eg node structs can have pointers, null by default

Ah, we’re talking about cpp! Just learned that references in structs are a thing. I was thinking about references in the C pointer sense.
Then indeed they seem incompatible to ZII in this context

I didn’t know you could have class members that store references in cpp, interesting.
Also it seems you can’t assign them first in the constructor (makes sense, you could call other things from in there at which point the non-null guarantees would not hold).

I don’t get your point: you certainly can initialize a reference to zero, then assign it something else later. Is it that you want to avoid null refs at all time?