Search Issue Tracker
Fixed
Fixed in 2022.3.51f1, 6000.0.24f1, 6000.1.0a1
Votes
0
Found in
2022.3.11f1
2023.3.0a11
6000.0.0b11
7000.0.0a1
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
Postponing; will batch forward port in the future.