Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
8
Found in
2020.3.5f1
2021.1.0a7
Issue ID
1325858
Regression
Yes
Objects are tinted cyan when Environment Lighting Intensity Multiplier is 1.0
How to reproduce:
1. Open the repro project
2. Use ADBV1 (click "no" on the dialog)
3. Accept upgrade (click continue)
4. Open Assets/_CompletedDemos/ToonOutlinePostprocessCompleted/ToonOutlinePost.unity
5. In Scene View, observe blue glow on characters
6. Click Window > Rendering > Lighting Settings
7. Uncheck "Auto-generate lighting"
8. Change Environment Lighting > Intensity multiplier to 0.99 or 1.01
9. Click "Generate Lighting"
10. Observe cyan tint disappears
11. Change Environment Lighting > Intensity multiplier to 1.0
12. Click "Generate Lighting"
Expected: No cyan tint
Actual: Lighting bake contains a blue/cyan tint when the intensity multiplier is 1.0
Reproducible with: 2019.4.23f1 (7.3.1), 2019.4.24f1 (7.6.0), 2020.3.5f1 (10.5.0)
Not reproducible with: 2020.3.4f1
Notes:
1. Tested on MacOS
2. Reproducible in built player
3. The Lightmap (seen in Lighting Settings > Baked Lightmap tab) does not become tinted in step 8 vs. 11
-
Alf-Dee
Sep 23, 2021 09:13
Happened to me on windows too on 2020.3.16f1
-
equalsequals
Aug 05, 2021 12:43
This is reproducible in the 2020.x stream as well.
It is temporarily resolved by clearing the GI Cache.
-
TylerBlust
Jun 01, 2021 17:20
This is also reproducible in 2019.4.22f1
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2022.1.X):
Investigation showed that the root cause for this issue was a problem with the underlying shading/material compilation system: https://issuetracker.unity3d.com/product/unity/issues/guid/1368213/
This problem has now been diagnosed and a fix has been implemented. The fix is backported to 2019.4, 2020.3, and 2021.2. This fix should be part of one of the coming minor version updates.
We will be postponing this case as a part of a larger area refactor which we are planning on conducting at a future date.