Search Issue Tracker
By Design
Votes
1
Found in
2020.3.35f1
2022.2.0b1
2023.1.0a1
Issue ID
UUM-1356
Regression
No
GameObjects are overexposed when Scene is additively loaded along with the Scene which uses HDRI Sky Environment
How to reproduce:
1. Open the attached "1319940_Repro" project
2. Open the "A" Scene
3. Drag the "B" Scene into the Hierarchy to load it additively
Expected results: The Cube in Scene "B" is black/doesn't emit light
Actual results: The Cube in Scene "B" is overexposed/emits light
Reproducible with: 7.5.3 (2019.4.23f1), 10.3.1 (2020.3.2f1), 11.0.0 (2021.1.0f1), 12.0.0 (2021.2.0a7)
Could not test with: 2018.4.33f1 because High Definition RP was not yet available
Notes:
- The issue is still reproducible if the Scene is loaded/unloaded using LightProbes.Tetrahedralize
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
- Memory Leak when using InstantiateAsnyc to instantiate a large Prefab
- There are checkboxes to enable and disable Volume Profile effects in the Graphics Settings
- “ArgumentException: Trying to use an invalid resource (pass Motion Blur)” errors are infinitely thrown when Motion Blur is used
- Inspector is not using the result of the last CreatePropertyGUI call when calling it for several times for one property
- Crash when attempting to initialize XR SDK while entering Play Mode
Resolution Note:
The scenes have different skies applied. Scene A uses a HDRI sky and scene B uses no sky. Thus the probes in scene A are lit by this sky and this lighting is applied (as is expected) onto the objects in scene B that are rendering from probes.
If probes are stored in a separate scene then the lighting treatment needs to match between the probe scene and the additively loaded scenes.