Search Issue Tracker
Directionality artifacts in multi-scene lighting setups
Steps to reproduce:
1. Download attached project 'New Unity Project78.zip'
2. Unzip and load project
3. Open 'test' scene
4. Additively load 'test2' scene
Expected results: 'test' scenes lighting look the same
Actual results: objects have NaNs created via the additional 'unity_black' texture
Reproduced with: 2019.3.0a6
Not reproducible with: 2019.2.0b7
Regression introduced in: 2019.3.0a1
- Reproducible just in 2019.3
- Reproduces in all render pipelines
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- [Android] QosService.Instance.GetSortedMultiplayQosResultsAsync crashes Player when it's built
- [Linux][IL2CPP] Player is not killed when using xkill command
- Decal is not drawn when using Deferred Rendering, a Rendering Layer, and Screen Space Ambient Occlusion
- "unity-radio-button-group__container" element is not referenced when calling RadioButtonGroup.contentContainer
- Unclear documentation about when ScriptableObject.Awake() is called
Resolution Note (2019.3.X):
We never supported mixing scenes with different directionality settings.
We also cannot correct for "wrong" settings, as the user might have an empty scene with some lights in it which has directionality disabled, being loaded additively onto a scene that has geometry with directionality. If we'd switch to non-directional just because some other scene is non-directional, the lighting would suddenly change in the main scene.
I'm therefore closing this by design. The LightmapSettingsManager will warn if such a scenario is being attempted.