Search Issue Tracker
Fixed in 2017.1.0f3
Votes
27
Found in
5.0.1f1
Issue ID
688985
Regression
Yes
Baked lighting data lost after rebake in copied scene
To reproduce:
1. Open attached project
2. Open scene, bake lightmaps
3. Make a copy of scene
4. Bake lightmaps in the copy
5. Lightmaps in original scene are removed
Inconsistent with navigation system.
This workflow worked fine in 4.6
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
- Unity drains raw input message queue before Rewired can process each event, making it miss some
- Old input system misses some mouse movement if the new input system is also enabled
- [URP] _ProjectionParams.x with Overlay rendering
- Assertion triggered when using Compile and show code button in Shader inspector
- Wrong elements are selected when holding shift and selecting Game Objects in the Scene Hierarchy
shubhamswaraj2021
Aug 19, 2020 13:21
good one <a href="https://www.lyricsauto.com">lyricsauto</a>
fivekoto
Jul 15, 2017 00:07
I have the same issue in Unity 2017.1 and script cant help any more.
Mirapa
Sep 22, 2015 15:46
I'm afraid this very bug bites us quite hard; we have multiple levels situated in the same location, and of course the scenes are copies of each other; and every time a project is built, every single lightmap is recomputed. This costs quite lot of time (5 hours of building instead of a half an hour with Unity4).
I see there is a note "workaround is possible" - please, can someone describe the workaround? (I sincerely hope the workaround is not "rebuild the second scene from primitives and prefabs", I doubt I would survive telling this to our level designers :-) )