Debugging variable compute shader rates
Hantverk'n » 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:
Hantverk'n
Status | In development |
Author | Teknologicus |
Genre | Adventure |
Tags | Exploration, Open World, Voxel |
More posts
- Fog is working again2 days ago
- Improved fragment/compute shading rates4 days ago
- Deferred gbuffer rendering update10 days ago
- Deferred gbuffer rendering via compute shader ray marching output11 days ago
- Fast and Accurate Color Depth Conversion16 days ago
- Update: Hilbert Curve surface grooved stone block18 days ago
- Hilbert Curve surface grooved stone block18 days ago
- Overhaul of buffer use in voxel engine30 days ago
- Tetahexacontree 4x4x4 Occupancy Bitmasks Lookup Table42 days ago
Leave a comment
Log in with itch.io to leave a comment.