Search Issue Tracker
Fixed
Fixed in 6000.2.7f1, 6000.3.0b4, 6000.4.0a2
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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Add comment