Search Issue Tracker
Fixed
Fixed in 6000.0.5f1, 7000.0.0a1
Votes
0
Found in
2023.3.0f1
6000.0.0f1
Issue ID
UUM-72651
Regression
No
[RayTracing] Several pragma require directives are ignored in .raytrace files.
Using #pragma require in .raytrace files doesn't work. All pragma require directives are ignored.
Steps to reproduce:
1. Clone the project from [https://github.com/INedelcu/PathTracingDemo] and open Assets/Shaders/RayGenerator.raytrace
2. Use one of the pragma require in a .raytrace file for example #pragma require int64bufferatomics or #pragma require int64 and save the file.
3. The shader fails to compile and generates the following error:
{quote}opcode '64-bit atomic operations' should only be used in 'Shader Model 6.6+'.{quote}
Actual results: No shader compilation errors are generated when using #pragma require directives.
Expected results: Shader fails to compile.
Reproducible with versions: 6000.0.2f1
Not reproducible with versions: N/A
Tested on (OS): Windows 11.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 6000.0.5f1):
Fix verified in:
Unity 6 Preview
6000.0.5f1.6358
Revision: trunk 17028576122a
Built: Wed, 29 May 2024 00:17:24 GMT