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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment