-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle naga's SpecialTypes #54
Comments
a minimal example would be really useful - just the wgsl. |
Try calling this function from a different module. @group(0) @binding(0) var tlas: acceleration_structure;
fn trace_ray(ray_origin: vec3<f32>, ray_direction: vec3<f32>, ray_t_min: f32, ray_t_max: f32) -> RayIntersection {
let ray_flags = RAY_FLAG_NONE;
let ray_cull_mask = 0xFFu;
let ray = RayDesc(ray_flags, ray_cull_mask, ray_t_min, ray_t_max, ray_origin, ray_direction);
var rq: ray_query;
rayQueryInitialize(&rq, tlas, ray);
rayQueryProceed(&rq);
return rayQueryGetCommittedIntersection(&rq);
} |
If I understood what's going on correctly when experimenting, naga can interpret |
@robtfm I modified naga to support writing out acceleration_structure. However we still need to populate the RT SpecialTypes. I worked around it by hardcoding them: JMS55@9bcdd3b |
The fix for being unable to write the acceleration structure binding is gfx-rs/wgpu#5261, but using RayIntersection across modules and stuff is still and issue and needs to be fixed by populating the special types. |
Ray tracing APIs do not currently work with naga_oil. DerivedModule throws out special_type info.
The text was updated successfully, but these errors were encountered: