Search Issue Tracker
Fixed
Fixed in 2022.2.15f1, 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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment