Search Issue Tracker
In Progress
Won't Fix in 2023.2.X
Under Consideration for 2022.3.X
Votes
7
Found in
2022.3.22f1
2023.2.16f1
6000.0.0b13
Issue ID
UUM-67560
Regression
Yes
"undeclared identifier '_FOVEATED_RENDERING_NON_UNIFORM_RASTER" error is thrown when the "FoveatedRenderingKeywords.hlsl" file is not included in a custom shader and the Rendering Path is set to Forward+
Reproduction steps:
1. Open the attached "Test20233URP" project
2. Open the "New Scene" scene
3. Observe the Console logs
Expected results: No "undeclared identifier '_FOVEATED_RENDERING_NON_UNIFORM_RASTER" errors are thrown and the shader compiles
Actual results: "undeclared identifier '_FOVEATED_RENDERING_NON_UNIFORM_RASTER" errors are thrown and the shader does not compile
Reproducible with: 2022.3.22f1, 2023.2.16f1, 2023.3.0b3, 6000.0.0b13
Not reproducible with: 2023.3.0b2
Could not test with: 2021.3.36f1 (Forward+ does not exist)
Reproducible on: macOS 12.6.7
Not reproducible on: Windows 11 Pro
Notes:
- When the Rendering Path is set to "Forward" or "Deffered", the error is not thrown and the shader compiles properly
- The compilation errors of scripts in 2022.3 and 2023.2 can be ignored as the issue with the shader throwing the error is still apparent in the Scene view
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
- "Objects are trying to be loaded during a domain backup." errors on entering Playmode
- Transform Node does not have outputs when it is created
- Changing the Default Icon does not change the executable's icon when re-building the project
- Texture is stored upside down when using Blit
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
Resolution Note (2023.2.X):
Closing as Won't fix due to 2023.2 reaching it's EOL.