Search Issue Tracker
Fixed in 2020.1.X
Votes
1
Found in
2017.1
2017.2
2017.3
2017.4
2018.1
2018.2
2018.3
2018.4
2019.1
2019.2
2019.3
2020.1
Issue ID
1059722
Regression
No
Static Batching Corrupts Scene View Modes on Play
Repro
=====
1. Download, unzip and open the attached project StaticBatching_LightingUVIssue2.zip
2. Open AdditiveLighting_00_Master scene.
3. Ensure the lighting is correctly baked by clicking "Generate Lighting" from Unity's Lighting Settings tab.
4. Ensure "Static Batching" is disabled from the Player Settings window (Edit > Project Settings > Player).
5. Switch the Scene View Mode to "Baked Lightmap" in order to better observe changes to the lightmaps.
6. Enter Play Mode.
7. Observe the lightmaps remain mapped as intended.
8. Now enable "Static Batching" from the Player Settings.
9. Enter Play Mode once again.
Observe
=======
The lightmaps will get hella goosed in the Scene View and dirty the bed sheets. You can't work like this. Like, seriously, what the hell is even going on anymore? I don't know. It's like a metaphor or something. The world is on fire and so are your lightmaps. Sad.
Note that the lightmaps are still rendered correctly in the Game view, only the Baked Lightmas scene view is corrupted.
Expected
========
Lightmap coordinates in scene view should remain consistent regardless of whether Static batching is enabled or otherwise.
Notes
=====
Scene modes affected (Baked GI):
- Albedo
- Texel Validity
- UV Overlap
- Baked Lightmap Culling
- The issue also present in Lightmap Preview window
- Occurs when either Auto Generate is enabled or disabled
- Tested with single and multi-scene setups
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment