Search Issue Tracker
Fixed
Fixed in 7000.0.0a1
Votes
0
Found in
2023.2.0b4
2023.3.0a1
7000.0.0a1
Issue ID
UUM-46164
Regression
No
[RayTacing] enable_ray_tracing_shader_debug_symbols pragma doesn't include shader source into debug symbols
When using #pragma enable_ray_tracing_shader_debug_symbols in HLSL code, the pragma doesn't cause the shader source to be included into debug symbols.
How to reproduce (have a ray tracing ready GPU):
- Clone and open the project from [https://github.com/INedelcu/PathTracingDemo]
- Open RayGenerator.raytrace from Assets/Shaders and add #pragma enable_ray_tracing_shader_debug_symbols to the HLSL source.
- Build any of the scenes.
- Open the built player in PIX or NVIDIA NSIGHT.
- Notice that HLSL source code is not included and cannot be debugged. !WinPix_7HuTPuNehF.png!
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note (fix version 7000.0.0a1):
2024.1.0a1.git.main.11890046
Revision: main b56d7e63884d
Built: Fri, 27 Oct 2023 03:58:04 GMT