@mcc thats why i always appreciate verbose argument names. No reason why they cant be named size_in_bytes, etc.
🎉 Blender Foundation and the developers community proudly present Blender 3.5!
🔶 A massive release featuring: Viewport Compositor, VDM sculpting, built-in hair assets, USDZ, and so much more.
🚀 What's new: https://www.blender.org/download/releases/3-5/
Huge thanks to everyone involved ❤️ #b3d
This weekend my partner Jane and I did a 48 hour game just for fun!
I made Devil Daddy Descent, a mostly functional turn based, side scrolling shooter about a stylish demon done in #pico8
It has:
💀 4 enemies
🎯 magic shooting
💣 bombs
🥾 stomping
🗺 procedural levels
📈 some difficulty scaling
🙅♂️ no sounds (ran out of time)
Play it here! https://andymakes.itch.io/devil-daddy-descent
I'm releasing my #Unity URP volumetric fog. Add it as a package to your project and have a play with it! #gamedev #techart #rendering
Coming back to my video feedback arcade shooter!
Added a new feedback setting and a big rotating laser to go with it.
Video had to be very short for compression to not totally eat it up.
Стимлянная Хамоника (1968)
@helvetica did you see this? lol
@mcc in my framework, i just have a templated buffer struct that wraps around a C++ struct that handles all of that, so all you do is just update your CPU data and call update() on it and it does the GPU memory update. if you have multiple frames in flight you also need to keep a separate device memory for each frame, so it has to handle all of that.
@mcc you keep a handle of a VkDeviceMemory which is bound to a descriptor set at a specific location, then you just map it to CPU memory, copy it and unbind when you want to update shader data.
@mcc ah i see, well not sure what the best approach then. fwiw in C, you don't update descriptor sets usually, you just map memory for a buffer in the set, copy it and unmap it.
a humble render farmer