Search Issue Tracker
Fixed in 5.4.0
Votes
2
Found in
5.3.0f2
Issue ID
749008
Regression
Yes
When loading scenes additively async, GI is corruped and appearing from other scenes
To reproduce:
1. Open attached project
2. Play "Scene1" scene
3. Move around with Mouse & WASD buttons
4. Press Z to load next scene in background and X to activate next scene and unload previous scene
5. Repeat 3-4 steps for a few times
Expected behavior: correct GI, only from loaded scene (see screenshot)
Actual behavior: GI corrupted, some parts from other scenes (see screenshot)
Reproducible with: 5.3.0f1, 5.3.0f2, 5.3.0f4 (5.3.0f4 only in build)
Not reproducible with: 5.1.4p1, 5.2.3p2, 5.4.0a5
Comments (4)
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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
3dHomer
Jan 29, 2016 11:31
I have a similar problem in 5.3.2p1 and previous releases. If I remember right, the bug was introduced in 5.1 or 5.2. Realtime GI doesn't work correctly in the build if I load the main scene via LoadScene or LoadSceneAsync. Everything works fine in the editor. Also, everything works fine in a single-scene build.
Auto-baking is off. GI cache was cleared and lightmaps were rebuilt many times.
The problem doesn't seem to be related to differences in scenes because the same problem appears when I load an identical scene (duplicate) too. I tried many different ideas but I'm not able to find any solution.
Bendik Stang
Jan 11, 2016 12:16
Partly solved.
Directional and Non-Directional lightmaps are not compatible, so if one scene is directional and the other non-directional, then one of the scenes will have broken lightmaps when loaded addititively.
Bendik Stang
Jan 11, 2016 12:15
If one scene is baked with directional maps, and the other isn't, then this problems occurs.
Obviously directional and non-direcitonal lightmaps are not compatible.
Bendik Stang
Jan 11, 2016 11:35
Reproduce:
1. Have two baked scenes.
2. Press play in the editor in one scene, load the other additively.
The second scene is visually completely broken.
Tried to bake on PC and Mac with same results.