You know how Day of the Tentacle had the Chron-O-John? Yeah, I've joined a service that rhymes with that and starts with a big M. @janhsimon on the gamedev server. See you there!

Just released! OpenXR Vulkan Example project v1.0.0 github.com/janhsimon/openxr-… It shows how to use both APIs together and focuses on simple code. It features multiview rendering, staged, combined vertex/index and a single uniform buffer for high performance. #OpenXR #Vulkan #Khronos

I put together a basic particle engine recently using CPU simulation but hardware instanced rendering (OpenGL) and ImGui (I made my own curve editor widget). Surprising how much you can do with a couple simple parameters and random variation. First a smoke effect, then some snow!

This was far and away the coolest project I have ever worked on. I so want to get back to it some day!

Last but not least, the very end of the game had extremely difficult jumps (flag 20) and endless spike tunnels where extremely precise jumping and boosting was required. The rest of the game had managed to be fun and challenging without resorting to "I Wanna Be The Guy" methods.

Some lategame mechanics that provide a boost to the player seemed to not be set up in a way that they would automatically land them safely. Some would lead straight into spikes. Boosters/platforms should always line up nicely to support the player even if it takes time to polish.

An item later in the game provides a jump boost when touched and then moves to a new spot. This is frustrating because at first you can't know where it's going to move -> trial and error. Especially frustrating in difficult rooms. Lesson: All rooms should be beatable on first try

Unfortunately, the wind mechanic came back again. Lesson to learn here: If your game is awesome because of the controls, don't take that away from the player. If you have to, make the wind accelerate the player, rather than slowing them down. Don't mix moving platforms with wind.

I'm still working on my skeletal animation project. I went from storing fully baked transformation matrices to storing individual pos/rot/scale offsets (relative to the bind pose) per bone/keyframe. This has unfortunately caused a return of the eldritch horror, as you can see...

OH NO, I did it again. Switching from storing full transformation matrices to separate loc, rot, scale for bone keyframes has unleashed ANOTHER eldritch horror. And this one's even worse if you ask me, much worse. Kinda reminds me of Elden Ring enemies though. :)

Progress! Fixed the normals. I still have to find out what exactly went wrong with my bone interpolation/matrix decomposition, and why I'm seeing motion glitches when playing the animation back very slowly (keyframe blending). But it's getting there! :)