diff options
| author | Tim Foley <tfoleyNV@users.noreply.github.com> | 2021-03-15 09:27:48 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-03-15 09:27:48 -0700 |
| commit | d8150e70612b58fb1cfefa262d3d862a6e6e79ba (patch) | |
| tree | 3a365fe5fea4a418e6b803968e4640b8739db41d /docs | |
| parent | fd304c6c02c73a0024f6d982b1936451e4812370 (diff) | |
Fix handling of RT accelerations structures for non-RT stages (#1753)
* Fix handling of RT accelerations structures for non-RT stages
The recent change that added support for the `GL_EXT_ray_query` extension made is so that a shader that declares a `RaytracingAccelerationStructure` as an input to a non-RT shader stage but then never *uses* it wouldn't enable any RT extension, resulting in a compilation failure in glslang.
This change reverts that behavior so that such shaders enable `GL_EXT_ray_tracing`, since that is the older of the two RT extensions that introduce `accelerationStructureEXT`. It is possible that we will need to revisit this decision based on which of the two extensions ends up being more broadly supported, but I think that right now it is fair to say that there exist drivers that support `GL_EXT_ray_tracing` but not `GL_EXT_ray_query`, so the former is the better default.
* fixup: failing test
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions