been getting back into my hobby renderer / engine project and have done basically nothing to the rendering itself for a week or two (after fixing a fun GPU race condition that caused memory faults and flickering); I’ve been all in on infrastructure and editing, turning it into less of a “one viewport to look around in” toy and more of a workbench.
the mildly interesting data-model thing I’m doing, which is also a source of some grief, is that the entire world state is a value type: it’s a struct containing more structs, so there’s no lifetime stuff to handle—if you have a World then you can do what you want with it without affecting anything else. this makes concurrency kind of a non-issue since I can just hand the renderer a copy of the current World to chew on. it also makes editing the world—dragging things around, or editing properties in the inspector panel—a little funky because somebody has to own the “real” world and handle propagating changes between that and the UI. which adds a little complexity compared to just handing around reference types, but hopefully will produce fewer bugs.
there’s still lots to do on this editing infrastructure—those inspector fields aren’t editable yet, obviously, and they also don’t yet respond to changes in the world like moving the camera around—but once that’s done I’ll be able to get back to the fun part, and will hopefully have some more interesting pictures.