screen-13 VS FallingSandJava

Check out Screen 13; write shaders and use the render graph to run them easily. Resources can be created individually or as part of an automatic pool. Lots of examples, fully documented. Triangle is 100 lines including shaders.

I'd like to share what I've learned over the last week while adding a point light shadow mapping example to Screen 13, my Vulkan rendering engine.

This example in Screen 13 uses pixel shaders for a spilled-paint effect; which is similar to moving sand through advection. If you want to focus on compute and pixel shaders which update buffers and display images on the screen: this engine is really well suited.

https://github.com/attackgoat/screen-13 is an easy-to-use render graph which allows you to run shaders and handle resources with very little code. As the author, I would recommend it!

Screen 13 is an easy to use render graph library - it doesn't have opinions on your shader code or render passes and can be easy to use kind of like a modern OpenGL. Runs where Vulkan runs: Windows/Mac/Linux/Mobile - no web.

Have you considered Screen 13?

I take it this will show up at https://github.com/attackgoat/screen-13/releases and the announcement just pre-empted it?

I am working on porting a falling sand simulation I originally built in Java over to Rust. I have chosen ggez as the framework to do this since from what I read Piston development has mostly stopped and falling sand simulations are not well suited to ECS engines like Bevy, etc.