Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2020.2
2020.2.0a11
Issue ID
1259645
Regression
No
Warning for nonmatching lightmaps mode is not taking into account the change of the active scene
How to reproduce:
1. Open user-submitted project (LightmodeWarning.zip)
2. Open the DirectionalBaked scene
3. Enter Play Mode
4. Note that the NondirectionalBaked scene was loaded additively and set as the active scene; non-directional mode is used
5. See the Console window warning
Expected result: "The loaded level has a different lightmaps mode than the current one. Current: Directional. Loaded: Non-Directional. Will use: Non-Directional."
Actual result: "The loaded level has a different lightmaps mode than the current one. Current: Directional. Loaded: Non-Directional. Will use: Directional."
Reproducible with: 2018.4.24f1, 2019.4.2f1, 2020.1.0b14, 2020.2.0a16
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
- [Mobile] Player Crash on scripting_invoke_profiler_begin when the built Player Scene has an empty UIDocument and is built on IL2CPP
- Unnecessary Warnings are logged when running Player with -batchmode -nographics
- [Android] [iOS] Application silently crashes when creating and setting up Textures2D in large amounts
- Some VFX Window Panels close on entering Play mode
- VFX Graph using Redo action for Move and Connect node results in an unknown input value
Resolution Note:
Warnings about mismatches in LightmapSettings of additively loaded scenes are only issued at load time. If the user - after the load like in the sample - switches the active scene from one to another, the mismatch is still there, but there will be no more warnings issued.
The old warning of course stays in the console until it is cleared.