Search Issue Tracker
Fixed in 10.0.0
Fixed in 7.7.1
Votes
0
Found in [Package]
7.0.1 - 10.0.0-preview.9
Issue ID
1262044
Regression
Yes
Closing the Editor while there are unsaved Shader Graph changes does not throw a warning prompt and results in a data loss
How to reproduce:
1. Create a new URP/HDRP template project
2. Create a new shader graph file
3. Open the graph and make some changes
4. Close the Editor
Expected result: Editor throws a prompt about unsaved changes in the graph before closing
Actual result: Editor does not throw a prompt about unsaved changes resulting in a data loss
Reproducible with: 2019.3.0b1(7.0.1), 2019.4(7.4.1), 2020.1.0b16(8.1.0, 9.0.0-preview.34), 2020.2.0a18(10.0.0-preview.9)
Not reproducible with: 2018.4.25f1(4.10.0), 2019.3.0a11(7.0.0)
Notes:
1. 2019.3.0b2 would consistently crash when trying to close the Editor with unsaved changes resulting in a data loss as well.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash with multiple stack traces when playing video on a render texture with low-end graphics devices
- Circle handle of the Game view scale slider bar disappears when the scale is set to 1x
- Asset Bundles non-deterministic behavior with CRCs and hash when a video has Transcoding enabled and Sprite Atlas has an override option enabled
- [Quality Hackweek] Errors "InvalidOperationException: EnsureRunningOnMainThread can only be called from the main thread" and "NullReferenceException" shown when switching build platforms with Muse Texture package installed
- "Importer(DefaultImporter) generated inconsistent result for asset" warnings are thrown when reimporting the "URP" texture
Resolution Note (fix version 7.7.1):
Fixed in Unity 2019.4.28f1 and ShaderGraph 7.7.1