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
- ScrollView speed is slower when entering Play mode
- UI Builder elements disappear and "Semantic - Unknown template name" error appears when changes to "Template" parameter are saved
- Renderers outside Light Probe hull use incorrect Ambient Probe values when "Renderer Light Probe Selection" is set to "Use Ambient Probe" and "Light Probes" on Mesh is set to "Blend Probes"
- ArgumentNullException error occurs when selecting a Camera in the Hierarchy with the Scene view open
- Clicking 'Open Editor Log' through the Console fails to open redirected Logs when relative Log files exist outside of the Project root
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.