Search Issue Tracker
Fixed in 2022.2.15f1
Fixed in 2022.2.X, 2023.1.X, 2023.1.0a26
Votes
0
Found in
2022.2.0b13
2023.1.0a1
Issue ID
UUM-564
Regression
No
[VFX Graph] Errors are thrown to the Console when shape nodes contain parameters with large numbers
How to reproduce:
1. Create a new VFX graph or open the existing one
2. Create 'Cone' node
3. Switch node to World Space
4. Enter '1e+20' to 'Radius 0' input field (or any other high value)
Actual result: Errors are thrown to the Console
Expected result: No errors are thrown to the Console, or informative errors that makes users aware of limitations are thrown to the Console
Reproducible with: 2021.2.0a18 master
Note: reproducible with other shapes too, for example: AABox, Circle, Sphere, etc.
Error messages:
Assertion failed on expression: 'CompareApproximately(det, 1.0F, .005f)'
Assertion failed on expression: 'fRoot >= Vector3f::epsilon'
Quaternion To Matrix conversion failed because input Quaternion is invalid \{-nan(ind), -nan(ind), -nan(ind), -nan(ind)} l=-nan(ind)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Add comment