Search Issue Tracker
By Design
Votes
1
Found in
6000.0.56f1
6000.2.4f1
6000.3.0b1
6000.4.0a1
Issue ID
UUM-119191
Regression
No
Branch node outputs a random value instead of a constant on the false conditon
Steps to reproduce:
- Open the attached package
- Open VFX and observe Update context setup of both systems
- [Optional]In the "Expected behavior" system, connect the Branch node, with values (0, 0, 0) on the false condition, to a Set Offset block
Actual results: Branch node's false condition outputs a random value
Expected results: Branch node's false value outputs a constant value
Reproducible with versions: 6.0, 6.2, 6.3, 6.4
Not reproducible with versions:
Can’t test with versions:
Tested on (OS): macOS
Notes:
- When disconnecting Angle.XYZ or Vector2 for Barycentric coords in Sample Mesh operator, issues becomes not reproducible
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:
The behavior of any random block in an output context relies on its non-constant randomness. If the particle seed is modified in the Update context, the output will vary on every frame.
If you encounter this situation, one possible workaround is to use a Random Operator and disable the Constant option for any calculation connected to the output context.