Search Issue Tracker
Fixed in 6000.1.0a7
Fixed in 6000.0.X, 6000.0.30f1, 6000.1.X, future release
Votes
0
Found in
6000.0.20f1
Issue ID
UUM-83852
Regression
No
[VFX Graph] Operators Size isn't consistent
Steps to reproduce:
1. Open a VFX
2. Create a bunch of operators (Vector3, Sample Noise Operator etc..)
3. Collapse some of them, Super collapse some of them
4.Close the VFX Graph
5.Re-open the VFX Graph
6.Un-Collapse some Operators.
7.Re-collapse.
8.Observe
Actual results: The size of the Operators in their different States are changing. Sporadically they're small, when sometimes they seems to be very wide in Collapse mode.
Expected results:
The collapse/Super-Collapse/
!image-2024-10-08-11-50-42-583.png!
Tested on (OS):
Notes:
- I'm unsure which version of the Operator is the Correct one. But to me, the Smallest one looks better, and takes less place. The Random Vector3 or Float are good examples of Operators that sometimes appear far too wide. Same for the Noise etc... For some operators, it appears to be relative to the display of the Input Labels. The shorter version don't display any input label when collapse and for me it's fine and takes way less space.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment