Search Issue Tracker
Duplicate
Duplicate in 6000.1.X
Votes
0
Found in
2021.3.44f1
2022.3.49f1
6000.0.22f1
6000.1.0a7
Issue ID
UUM-83229
Regression
No
The pixel artifacts appear when there are 33+ lights in the scene using HDRP in macOS
How to reproduce:
1. Open the “ReproLightsProject“
2. Open the “LightPixelRepro“ scene
3. Observe the Game view
Expected result: No pixelation artifact
Actual result: A visible pixelation artifact
Reproducible with: 2021.3.44f1, 2022.3.49f1, 6000.0.22f1
Reproducible on: macOS 14.6.1 (Intel)
Not reproducible on: Windows 10 Pro (22H2)
Notes:
- The 33 lights in the scene start to create the pixel artifact, but they are better visible with around 40, the light limit in HDRP is 63, so the light amount that reproduces the issue is a lot less than the limit
- The pixel artifact position depends on the Scene/Game view cameras position, if you move it around the pixel artifacts change positions
- Reproducible in the Player macOS
- More information in the comments
-
Resolution Note:
null
Duplicate of another internal issue: UUM-74955: [MacOS] Incorrect code generation from HLSLcc vs DXC -
Resolution Note (6000.1.X):
null
Duplicate of another internal issue: UUM-74955: [MacOS] Incorrect code generation from HLSLcc vs DXC
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
This is a duplicate of issue #UUM-73470