Search Issue Tracker
Fixed in 2017.2.0f3
Fixed in 5.6.X
Votes
0
Found in
5.6.0f3
Issue ID
919234
Regression
No
[Auto] Creating a new scene in project window affects the lighting settings of other scenes
Creating a new scene using Project window (instead of File -> New Scene) changes Auto mode toggle button and affects the lighting setting of previous scene.
Steps for reproduction:
1) Create a New Project
2) Create a new scene through File -> New Scene or `Ctrl + N`
3) Save the scene (e.g. name it `Scene1`)
4) Disable Auto mode and manually generate the lighting
5) Right click in Project window, go to Create -> Scene
6) Press enter two times, this creates a scene called `New Scene` in Project window.
7) Open previous scene (`Scene1`)
9) Observe that Auto mode is magically enabled and triggers a re-bake of the scene.
Notes:
- Not a regression, reproduced in 5.4.5p2, 5.5.4f1, 5.6.0f3, 5.6.1p2, 2017.1.0b9, 2017.2.0a3
- Workaround is to create a new scene through (File -> New Scene)
- Creating a new scene in Project window shouldn't affect the lighting settings of another scene in the project
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] FPS does not match the targeted FPS when it is set with Application.targetFrameRate
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
Add comment