Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.12f1
2023.1.19f1
2023.2.0a15
2023.3.0a11
Issue ID
UUM-54682
Regression
No
VFX Asset Settings do not update in Inspector when focusing different VFX Assets in the VFX Window Blackboard
How to reproduce:
1. Open any project with the Visual Effect Graph installed
2. Open and create two VFX Graph Assets (They should open 2 different windows)
3. Try selecting the two Assets and observe that the Inspector updates
4. Select a Node in one of the Assets and click on the Blackboard where there are no other Nodes and observe that the Inspector changes to VFX Asset Settings
5. Open the other Asset by switching windows and not opening the Asset itself and click anywhere on the Blackboard without selecting a Node first and observe the Inspector
Actual result: Clicking anywhere on the Blackboard if no Node was previously selected does not show the VFX Asset Settings, but does show it if a Node was previously selected
Expected result: Clicking anywhere on the Blackboard dead space could show the VFX Asset Settings, like it does when a Node is selected and then unfocused when clicking in the Blackboard
Reproducible with: 2022.3.12f1, 2023.1.19f1, 2023.2.0a15, 2023.3.0a11
Not reproducible: 2021.3.31f1 (VFX Assets open only in one window)
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.