Search Issue Tracker
Fixed
Fixed in 6000.5.0a5
Under Consideration for 6000.0.X, 6000.3.X, 6000.4.X
Votes
0
Found in
6000.0.65f1
6000.3.3f1
6000.4.0b5
6000.5.0a4
Issue ID
UUM-130886
Regression
Yes
“Shader warning in 'TraceTransparentRays’…” warning is thrown after adding Graphics API
Reproduction steps:
1. Create a new project
2. Edit > Project Settings… > Player > Other Settings
3. Disable Auto Graphics API
4. Press “+” in Graphics API section and add one of the Graphics APIs
5. Observe the Console
Actual result: “Shader warning in 'TraceTransparentRays': ambiguous type for bit shift; use a type suffix on literal values, like 'L' or 'U', or a cast [-Wambig-lit-shift] at Packages/com.unity.render-pipelines.core/Tests/Editor/UnifiedRayTracing/TraceTransparentRays.urtshader(21) (on d3d11)” warning is thrown
Expected result: No errors or warnings are thrown
Reproducible with: 6000.3.3f1, 6000.4.0b3, 6000.5.0a4
Not reproducible with: 6000.0.65f1, 6000.3.2f1
Reproduced on: Windows 10, Windows 11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment