Search Issue Tracker
Third Party Issue
Third Party Issue in 2022.2.X
Votes
2
Found in
2021.3.4f1
2022.2.0b7
Issue ID
UUM-8027
Regression
No
[M1] Rendering artifacts when disabling and enabling the Light GameObject
Reproduction steps:
1. Open the attached project
2. Open the OutdoorsScene.unity Scene located in the Assets folder of the Project window
3. Enter Play Mode
4. Disable and then Enable the "Sun" GameObject
5. Observe the "Wooden_Support_05" GameObject in the Game view
Expected result: there shouldn't be any graphical artifacts
Actual result: graphical artifacts/glitches are present
Reproducible with: 12.1.7 (2021.3.4f1), 13.1.5 (2022.1.5f1)
Could not test with: 7.7.1 (2019.4.39f1), 10.9.0 (2020.3.36f1) - couldn't downgrade, Apple Silicon Editor is not available, 14.0.3 (2022.2.0a17, 2023.1.0a1) - "Shader error in 'Better Lit/Lit': 'GetDecalSurfaceData': cannot implicitly convert from 'float3' to 'struct FragInputs' at line 18043 (on metal)"
Reproducible on: M1 MacOS 12.4 (21F79)
Notes:
- This issue is reproducible only on Apple Silicon Editors
- The issue doesn't appear in Play Mode
- In order to make the artifacts disappear you have to disable decals in the HDRP frame settings or increase the "Alpha Clip Threshold" parameter on the "Assets/Export/Wood_2" material to anything greater than 0.
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
Resolution Note:
As this is an issue with a third-party shader, we recommend reporting the bug to the shader's author.
Resolution Note (2022.2.X):
As this is an issue with a third-party shader, we recommend reporting the bug to the shader's author.