Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
0
Found in
6000.0.69f1
6000.3.10f1
6000.4.0b11
6000.5.0a8
6000.6.0a1
Issue ID
UUM-136170
Regression
No
Undocked VFX Graph window has no limited minimum size
How to reproduce:
1. Create a new Unity project and install the VFX package
2. In the Project window, right-click -> Create -> Visual Effects -> Visual Effect Graph -> Any VFX Graph
3. Undock the VFX Graph window
4. Resize the VFX Graph window to its minimum size
5. Observe the results
Expected results: The window's minimum size is limited so some elements are still accessible
Actual results: The window's minimum size is not limitedÂ
Reproducible with: 6000.0.69f1, 6000.3.10f1, 6000.4.0b11, 6000.5.0a8
Reproducible on: Ubuntu 24, macOS Tahoe 26
Not reproducible on: No other environment tested
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
- Texture generator reference image fails despite valid size
- Agent mode can enter infinite execution loop
- AI Gateway responses contain duplicated sentences
- Texture 2D asset is created when promoting a generated Cubemap to a new asset
- Unable to copy multiple paragraphs from Assistant responses
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.
Resolution Note (6000.6.X):
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.