Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2023.1.0a9
2023.2.0a1
Issue ID
UUM-575
Regression
No
[VFX Graph] Graph changes persist when Creating Graph with the same name as a recently Deleted Unsaved Graph
Reproduction steps:
1. Create a new project
2. Create VFX Graph
3. Select any several blocks and delete them
4. Close VFX Graph window (Don't save graph accidentally)
5. Delete graph from Project Browser
6. Create new VFX Graph
Expected result: A newly created Graph matches the Template
Actual result: Blocks are missing in a newly created VFX Graph
Reproducible with: 7.6.0 (2019.4.29f1), 10.5.0 (2020.3.14f1), 11.0.0 (2021.1.16f1), 12.0.0 (2021.2.0b4, 2022.1.0a4)
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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
Resolution Note:
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (2023.2.X):
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.