Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2018.1.0b8
Issue ID
1002151
Regression
Yes
Changing project settings and pulling that change breaks lighting and Editor layout color
Reproduction steps:
1. I used this simple project, that's on GitHub https://github.com/UnityCatalina/bug/invitations
2. Open the project on machine 1and leave it running
3. On machine 2, clone it and change a simple Graphics setting (e.g. change the Lighing from Linear to Gamma)
4. Push that change
5. Back on machine 1, pull that change while the project is still running
6. Notice the shadows going all black and the lighiting is yellow (see attached screenshot).
7. Try to re-bake lighting, and notice it doesn't improve it. Also, in Unity 2018.1 0b8, the colors of the framework change (see attached screenshot).
8. Reloading the whole project fixes back the lighting
Same steps yields a correct lighting result in Unity 2017.3 0f3
Please check the attached screenshots to see the lighting difference.
While the example project is very simple, I have encountered this issue during Scenario Test Week with a scene that had the Post Processing Stack on it. All the effect of the PP are turned off when this issue occurs. It DID occur really often especially at the start of the project, when a lot of us were changing project settings.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment