Search Issue Tracker
Fixed in 2017.2.X
Votes
1
Found in
5.3.4f1
Issue ID
799477
Regression
No
Unity does not start if scene and its built lighting are named as library
Steps to reproduce:
- Open attached project and scene named "library" which can be found under Assets/Scenes
- On the top menu select Window > Lighting
- Press "Build" which is placed on newly opened "Lighting" window's bottom
- Notice that built lighting folder named "library" (name depends on the scene's name) was created and placed in the Scenes folder
- Close Unity and re-open the same project
- Notice error which complains about newly created folder named "library" (see attached image)
Expected behavior:
There should be no error no matter what is the name of the built lighting folder
Actual behavior:
Unity gives an error about multiple folders and does not let open the project
Note:
The error does not occur if the "library" folder is empty
Workaround:
Change scene's name to anything but "library" and then do the build of lighting
Reproduced with:
5.4.0b19, 5.4.0b1, 5.3.5f1, 5.3.4f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Add comment