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
- [Hub] Editor is shown in the "Installing" state indefinitely when the installation fails due to INVALID_DESTINATION error
- Searching packages on an ill-configured scoped registry targeting Google Unity API registry throws an error
- Not possible to deduce the source of 'Shader properties can't be added to this global property sheet.' error
- [MacOS] Mouse input gets interrupted when changing values in inspector by dragging mouse
- Adding/removing components expands collapsed components view in the Inspector window
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 :-) )