Search Issue Tracker
Won't Fix
Votes
0
Found in
2023.2.0b13
2023.3.0a9
Issue ID
UUM-52424
Regression
No
Only one from three possible ways allow user to open FVX templates window
How to reproduce:
# Open HUB;
# Create 3D(HDRP) project;
# Create a visual effect graph in the "Project" window (Create->Visual Effects-> Visual Effect Graph-> Minimal System -> Create);
# Double-click on it to open it;
# Verify, that "+" (to add template) is active and user can use it;
# Delete the graph from the project window;
# Verify, that the graph becomes deleted;
# Observe the next points: "Create new Visual Effects Graph", "+" and "Window -> Visual Effects ->Visual Effects Graph".
Expected result: All three options should be active to create a new graph.
Actual result: Only the "Create new Visual Effects Graph" buttons work and the user can select a needed template. The other two options do not help. One is disabled, the other not, but still does not open the template window. Added video in the "Attachments" section.
Reproducible with: 2023.2.0b13, 2023.3.0a9
Not reproducible with: 2022.3.10f1 and 2023.1.16f1 as this one has no "+" functionality.
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
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
- [Mobile] The Material is not visible when using the Decal Renderer Feature
- Uncaught TypeError: Cannot read properties of undefined is thrown when the tab is inactive for several minutes
- Crash on mono_array_length when building a project
- "StackOverflowException" error when changing spline curve type from "Bezier" to "Auto" in the "Element Inspector"
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.