Search Issue Tracker
By Design
By Design in 5.4.X, 5.5.X, 5.6.X
Votes
1
Found in
5.4.1p3
Issue ID
887625
Regression
No
[MSE] Scene with no baked lightmaps is treated as Directional
BY DESIGN:
The current behavior is expected, as the user is trying to merge two scenes with incompatible settings. The warning is there for a reason.
The reason why we cannot change the behavior to what the user suggested is the following: Suppose scene1 has non-directional mode, scene 2 has directional mode. If a multi-scene setup loads these two incompatible scenes and the scene1, which has no lightmaps, changes its mode to accommodate to scene2, it might break its own compatibility with a third scene3 added later (you can add any number of scenes together). If we change the behavior to what the user suggested, we are changing the default which other users may rely on.
In any way, MSE or additive scene loading should always be done with compatible scene settings. It is a mistake to add these two setups into one, and we will change the warning to a stronger expression (Error).
Reproduction steps:
1. Open the attached project (OpenSceneAdditiveLM.zip).
2. Open the Scene2.
3. Go to Window -> Lighting.
4. Make sure that Directional Mode is set to Non-Directional.
5. Push the Build button.
6. Open the Scene1.
7. Right-click the Scene2 in the Hierarchy and Select Open Scene Additive.
Actual behavior:
- Scene2 objects turns black
- Warning is thrown: The loaded level has a different lightmaps mode than the current one. Current: Directional. Loaded: Non-Directional. Will use: Directional.
Expected behavior:
- Scene with no baked lightmaps changes to Non-Directional mode.
Workaround:
- Bake the Scene1 with "Non-Directional" mode before combining the scene.
Reproduced with:
5.3.8f1, 5.6.0b11, 2017.1.0a3
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
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
LilGames
Aug 10, 2019 23:14
2018.3.4f1
I have a basic scene with just a canvas in it, and it loads the main scene with all the 3D content. I've matched both scenes' lighting settings and even set the first scene to "non-directional" yet I still get the warning
"The loaded level has a different lightmaps mode than the current one. Current: Directional. Loaded: Non-Directional. Will use: Directional"
Why is it defaulting to Directional if BOTh scenes are set to Non-Directional? This makes no sense.
levykin
Oct 03, 2018 14:25
+1
denis_va
Aug 01, 2018 08:09
I get your point with the "compatible scene settings", but shouldn't there at least be an option to completely disable lighting-related behaviour / checks?
In my case, I do have a Main scene that works as an entry point for the game and holds all central services and managers that are needed in the different contexts. Which is why I keep this scene in the hierarchy throughout the whole running time. So every time I load a 3d scene with baked lighting, I get this warning.
Same thing applies to UI Dialogs and Popups that are capsuled in their own scenes. It's not really practical to just bake empty lightmaps for all these scenes...