Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2020.3.41f1
2021.3.12f1
2022.1.21f1
2022.2.0b12
2023.1.0a16
2023.2.0a1
Issue ID
UUM-17497
Regression
No
VFX asset window displays old VFX title after its renaming
How to reproduce:
- Open HUB;
- Create 3D(HDRP) project;
- Create visual effect graph in the "Project" window (Create->Visual Effects-> Visual Effect Graph);
- Drag it to the "Scene" window;
- Select newly created graph in the "Project" window and go to "Inspector" window;
- Click "Open" button;
- In the opened graph window turn on "Blackboard";
- If VFX asset window is docked to the Unity editor, undock it;
- Go to "Project" window and select VFX asset;
- Rename selected VFX asset.
- Verify VFX window, but don't touch it.
Expected result: VFX asset title should update in three places: VFX window, VFX window tab and blackboard.
Actual result: VFX asset title changes only in 2 places - VFX window tab and blackboard, but VFX window stays with the old title.
Reproducible with: 10.10.0 (2020.3.41f1), 12.1.7 (2021.3.12f1), 13.1.8 (2022.1.21f1), 14.0.3 (2022.2.0b12), 15.0.1 (2023.1.0a16).
Note: reproducible with macOS only, windows OS does not seem to have name for windows
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.