Search Issue Tracker
Fixed in 2022.3.51f1
Fixed in 2022.3.X, 6000.0.X, 6000.1.0a1, future release
Votes
0
Found in
2022.3.11f1
2023.3.0a11
6000.0.0b11
Issue ID
UUM-49399
Regression
Yes
Shader Graph is reverted to its primary state when entering Play Mode without saving changes
How to reproduce:
1. Open the attached “graphs.zip” project
2. Open “New Shader Graph” Shader Graph
3. Add any Node
4. Enter play Mode
5. Exit Play Mode and observe the Shader Graph
Expected result: The added Node is in the Shader Graph
Actual result: The added Node is not in the Shader Graph
Reproducible with: 2022.2.2f1, 2022.2.21f1, 2022.3.10f1, 2023.1.14f1, 2023.2.0b10, 2023.3.0a6
Not reproducible with: 2021.3.30f1, 2022.2.1f1
Reproduced on: macOS 13.5.2 (Intel)
Not reproducible on: No other environment tested
Note: if saving Shader Graph before entering Play Mode, then the issue is not reproducible
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
- Console Warning -- KeyboardIconAtlas sprite Input Outline goes beyond the boundary of the Sprite rect.
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
Resolution Note:
Postponing; will batch forward port in the future.