Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.10f1
2022.2.0b8
2023.1.0a9
2023.2.0a1
Issue ID
UUM-14060
Regression
No
Mesh in preview does not have lightning when "Rendering Layer Mask" is set to anything but 0
Reproduction steps:
1. Open the user's attached project
2. Select "ExampleAssets/Sphere"
3. In the Inspector, make sure that the "Rendering Layer Mask" is set to 1 (Or it seems like any layer other than 0)
4. Observe the preview image at the bottom of the Inspector
Expected result: The preview sphere is lit up
Actual result: The preview sphere is completely black
Reproducible with: 2021.3.10f1, 2022.2.0b8, 2023.1.0a9
Could not test with: 2020.3.38f1 (Donwgrading issues)
Reproducible on: macOS 12.5.1 (Intel)
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:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (2023.2.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.