Search Issue Tracker
In Progress
Under Consideration for 6000.2.X, 6000.3.X
Fix In Review for 6000.4.X
Votes
0
Found in
6000.2.4f1
6000.3.0b2
6000.4.0a1
Issue ID
UUM-117463
Regression
Yes
TerrainLitDepthNormalsPass is using uint4 instead of uint for outRenderingLayers
Reproduction steps:
1. Create a new URP project
2. From the Project window, search for “TerrainLitDepthNormalsPass.hlsl” and open it (Package\com.unity.render-pipelines.universal\Shaders\Terrain)
3. Search for “outRenderingLayers” in the file
4. Observe the data type next to it
Expected result: outRenderingLayers uses “uint”
Actual result: outRenderingLayers uses “uint4”
Reproducible with: 6000.2.0b1, 6000.2.4f1, 6000.3.0b2
Not reproducible with: 6000.0.58f1, 6000.2.0a10
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Note:
- In the “Not reproducible with” versions, the actual result was a “float4” type, which was then later changed to an incorrect one (uint4), which should be “uint”
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Add comment