Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.67f1
6000.0.58f1
6000.2.6f1
6000.3.0b3
Issue ID
UUM-119892
Regression
No
“Assertion failed on expression: 'IsFinite(distanceForSort)’” is spammed in the Console when changing Trail GameObject position to a very high number
*Steps to reproduce:*
# Create a new Unity project using the Universal 3D template
# Create a new Trail GameObject (GameObject > Effects > Trail)
# Select the newly created Trail GameObject in the Hierarchy window
# Change the X position to a very large number in the Inspector window
# Observe the Console window
*Actual results:* “Assertion failed on expression: 'IsFinite(distanceForSort)’” is spammed in the Console window
*Expected results:* "Invalid worldAABB. Object is too large or too far away from the origin." error is thrown which is descriptive and tells the user the exact issue
*Reproducible with versions:* 2022.3.67f1, 6000.0.58f1, 6000.2.6f1, 6000.3.0b3, 6000.4.0a1
*Tested on (OS):* Ubuntu 24.04, macOS Silicon Sequoia 15.6.1
*Notes:*
* On any other GameObject, the "Invalid worldAABB. Object is too large or too far away from the origin." error is thrown
* The errors are being thrown even if the position is changed back from the very large number to a small number
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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
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.