Search Issue Tracker
By Design
Votes
0
Found in
2020.3.38f1
2021.3.7f1
2022.1.11f1
2022.2.0b3
2023.1.0a4
Issue ID
UUM-12795
Regression
No
Scene's ambient color turns black when scenes are switched using SceneManager.LoadScene
To reproduce:
1. Open the project “BugHunt2 Built-in”
2. Enter Play mode
3. Notice that in the Console the “Second” Scene’s Ambient color is black
4. Exit Play mode
5. Open the “Second” scene
6. Enter Play mode
7. Notice that the “Second” Scene's Ambient color is not black
Expected result: The colors in the 4th and 8th steps are the same
Actual result: The Ambient color of the “Second” scene becomes black
Reproducible with: 2020.3.38f1, 2021.3.7f1, 2022.1.11f1, 2022.2.0b3, 2023.1.0a4
Reproduced on: macOS Monterey 12.4 (Intel)
Note:
- If the direction light is oriented the same in both scenes the issue does not appear
User’s note:
- The effect can be observed by adding some additional objects or with RenderSettings.ambientProbe.Evaluate which should report some non-black values
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
This is a known design flaw of the SkyManager, which bakes environment lighting temporarily for scenes that have none.
The workaround is to simply manually generate lighting for each scene where environment lighting is desired.