Search Issue Tracker
In Progress
Under Consideration for 2022.3.X
Fix In Review for 6000.0.X
Votes
0
Found in
2022.2.2f1
2022.3.40f1
6000.0.13f1
7000.0.0a1
Issue ID
UUM-77183
Regression
Yes
Docked Shader Graph window loses unsaved changes when resetting all layouts
*Steps to reproduce:*
# Open a URP Unity project
# Create a new Shader Graph asset in your assets via Create > Shader Graph > URP > Lit Shader Graph
# Open your new Shader Graph asset by double clicking on it
# Make sure the Shader Graph window is docked in the Editor and not floating
# Make some visible changes in the asset without saving (e.g. add a new float property or create a new node)
# In the top right of the editor, press the layout drop-down and click 'Reset All Layouts'
# Press 'Continue' on the pop-up
*Actual results:* The layout of the editor is reset and all unsaved changes for the Shader Graph Asset are lost.
*Expected results:* One of two results is expected:
* An 'Unsaved Changes Detected' pop-up is given to the user before the layout is reset, with the user having the usual option of being able to 'Save' or 'Discard'. This is how it was for Shader Graph before the FAV.
* The layout is reset, however the user can re-open the Shader Graph Asset and all their unsaved changes will have been persisted. This is how it works in VFX Graph and UI Toolkit.
*Reproducible with versions:*
* 6000.0.13f1
* 2022.3.40f1
* 2022.2.2f1
*Not reproducible with versions:*
* 2022.2.1f1
* 2021.3.40f1
*Can’t test with versions:* -
*Tested on (OS):* Windows 10/11
*Notes:* -
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- Mouse and Pointer Events are called incorrectly in ScrollView with XRUIInputModule
- Memory leak occurs when repeatedly minimizing and maximizing the UI Builder window
Add comment