Search Issue Tracker
By Design
Votes
1
Found in
2019.4
2019.4.31f1
2020.3
2021.1
2021.2
2022.1
Issue ID
1374474
Regression
No
Rendering probe lit objects in shadowmask mode is causing dark objects
How to reproduce:
1. Open the user attached project (LightProbBug2019.zip)
1a. Switch to linear mode in Player settings
1b. Switch to Shadowmask in Quality settings
1c. Rebake lighting
2. Select the "Main Camera"
3. Observe the color of the mentioned cube
Expected result: the two cube look the same
Actual result: the probelit cube is too dark
Reproducible with: 2019.4.32f1, 2020.3.22f1, 2021.1.28f1, 2021.2.2f1, 2022.1.0a14
Not reproducible with:
Notes:
1. Reproducible on Ubuntu 20.04 and Windows 10
2. The issue is present in the Editor and on a build
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 (2022.1.X):
Turns out this was caused by a couple of probes stuck inside the cube. Moving those out caused the lighting to look correct. The reason that it was changing with the camera movement was that one of the lights was shadowmasked. This means that it uses realtime lighting and shadows when rendered up close, but when rendering from a distance it approximates incident shadows by using occlusion values stored with the probes. So since there were probes inside the object and these were flagged as being in shadow, the cube was rendered as partially shadowed and thus tured out appearing darker than it should.