Ray Tracing Tracking Issue

[Vecvec]

For the current implementation see https://github.com/gfx-rs/wgpu/blob/trunk/docs/api-specs/ray_tracing.md.
For prior details see #1040

Acceleration structures

Features

• Basic Ray Queries #6291
• Compaction Ray tracing compaction #6609 [wgpu] Blas compaction #7285
• Update instead of build if possible and preferred.
• Custom intersections (AABBs). Custom geometry for acceleration structures #7701
• as_hal for acceleration structures. Implement as_hal for BLASes and TLASes #7303
• limits Add acceleration structure limits #6803

Nice to have (less important features / underlying APIs still in development)

• Micromaps (opacity and displacement)
• Partitioned TLASes - PTLAS - (may not require any / much API change)
• Cluster geometry (CLASes)
• Extended acceleration structure vertex formats (f16x4, snorm16x4 ect.)

Design

• Reconsider build_acceleration_structures_unsafe_tlas after as_hal has been added.

Known Bugs

• Raytracing Tests Failing on AMD GPU #6727
• [vulkan] acceleration structure in a descriptor pool are not properly allocated #6859
• Creating acceleration structure resources should require enabling a feature #8008

Support

• Vulkan
• DX12 Support DXR in wgpu-hal & naga. #6777
• Metal Implement Ray Tracing on Metal #7402

Ray Queries

Features

• Basic Ray Queries #6291
• Commit candidate intersections Allow for comitting candidate intersections #6759
• remove undefined behavior Remove undefined behavior for ray queries #6761
• ray query get vertex return support SPV_KHR_ray_tracing_position_fetch in naga #6763

Design

• Consider renaming instance_id to instance_index. #6778

Known Bugs

• Lavapipe causes access violation accessing intersection.world_to_object #6731

Support

• Vulkan
• DX12 Support DXR in wgpu-hal & naga. #6777
• Metal (naga support, not exposed due to no acceleration structure support yet)

Ray Tracing Pipeline

• Decide on basic design
• Implement basic design Decide & implement a design for ray tracing pipelines #6760

[baadc0de]

@Vecvec I'd like to get involved on this feature. #6609 seems like branch needs fixed to be compatible with upstream and tests fixed, is it a good starting point?

[Vecvec]

#6609 is in an odd situation - Mesa (which CI uses) has a bug in it that causes the test added to seg-fault, this bug is caused by resetting certain types of query pools, this has meant that that PR is not able to be merged (as it would cause everyone else's CI to fail). I was hoping that the patch would be merged soon, but that doesn't seem to be happening. Most of the other CI issues are caused by merging with trunk, and seem to be trivial.

[Vecvec]

Thanks for wanting to help! If you want to figure out how acceleration structure building works then implementing updating sometimes instead of building would be helpful too, it's probably also quite advanced though so a simpler thing to do would be general checking of code - the entire building process is quite large so it's likely that there are bugs in there somewhere. There are also #6803 and #6759 which would be nice to have implemented. General helping out is also useful, and so is testing the code using either the testing API or by writing code to use this.

[baadc0de]

Thanks for wanting to help! If you want to figure out how acceleration structure building works then implementing updating sometimes instead of building would be helpful too, it's probably also quite advanced though so a simpler thing to do would be general checking of code - the entire building process is quite large so it's likely that there are bugs in there somewhere. There are also #6803 and #6759 which would be nice to have implemented. General helping out is also useful, and so is testing the code using either the testing API or by writing code to use this.

Thanks, I'll look at the linked issues and check the acc structure building code for robustness.