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
- Addressables Report window UI is broken when opening via Build > New Build > Default Build Script
- Addressables Profiles window UI break when creating a new Variable with a long name
- No character limit when renaming Profile in Addressables Profile window, allowing excessively long names
- Blurry, low quality Active Profile icon used in Addressables Profiles window
- Tree Asset Preview window is not updated after assigning a new Material
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.