Debugging variable compute shader rates
Vorxel » Devlog
With compute ray marching it means part of the shading rates logic must be done in the compute shader (in addition to it still being done in the fragment shader for the gbuffer render pass) for performance benefits in ray marching.
This means the compute shader has a shading rates buffer with the same data that is fed to the rasterization pipeline and the compute ray marching shader casts minimal rays based on said buffer.
Here's a screenshot of visually verifying the correctness of the shading rates in the compute shader:

Vorxel
Status | In development |
Author | Teknologicus |
Genre | Adventure |
Tags | Exploration, Open World, Voxel |
More posts
- Fixed bug with dynamic direct sunlight and level of detailFeb 04, 2025
- Voxel Cone Tracing ExperimentFeb 04, 2025
- Dynamic direct sunlight working with level of detailFeb 01, 2025
- Improved dynamic direct sunlightJan 27, 2025
- Dynamic direct sunlightJan 26, 2025
- Previous folly and finally successJan 19, 2025
- Rasterized triangles are evil!Jan 10, 2025
- Procedurally Generated Blocks (Video)Jan 07, 2025
- Fog is working againJan 04, 2025
- Improved fragment/compute shading ratesJan 02, 2025
Leave a comment
Log in with itch.io to leave a comment.