Search Issue Tracker
Fixed in 5.6.0
Votes
1
Found in
5.3.5p7
Issue ID
812486
Regression
Yes
[MSE] Built lightmaps are not applied due to positioning in hierarchy
Steps to reproduce:
1. open users attached project
2. open SceneB
3. add SceneA to hierarchy
4. build lightmap
Result: Builds lightmap but does not apply it to the scene
5. open SceneA first
6. add SceneB to hierarchy
4. build lightmap
Result: Expected behaviour scene is light by red light
Notes:
- Reproduced on: 2017.1.0a3, 5.6.0f1
- Regression introduced with: 5.6.0b6
- Doesn't occur in 5.6.0b3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment