Search Issue Tracker

Won't Fix

Won't Fix in 6000.6.X

Votes

0

Found in

6000.0.65f1

6000.3.4f1

6000.4.0b3

6000.5.0a4

6000.6.0a1

Issue ID

UUM-131785

Regression

No

Entering large values in keyframe “Value” causes Curve to disappear and spams Mesh Bounds errors in the Console window

Mecanim Animation

-

Steps to reproduce:
1. Create a new Unity project
2. In the Hierarchy, create any GameObject
3. Open the Animation window (Window -> Animation -> Animation)
4. With the GameObject selected, click "Create" in the Animation window
5. Click "Add Property" and add “Cube : Position” Property
6. Select “Curve” tab
7. Right-click on red Curve Key and select “Edit Key”
8. Add “22222222222222222222222222” in “value” field
9. Press Enter
10. Observe Curve and Console window 

Actual results: Adding a bigger value causes Curve to disappear, unable to re-add it in the Curves window, errors are thrown in the Console window
Expected results: Value field should be limited how big of a value can be added, should not break the Curves, no errors thrown in the Console window

Reproducible with versions: 6000.0.65f1, 6000.3.4f1, 6000.4.0b3, 6000.5.0a4

Tested on (OS): macOS Silicon Tahoe 26.2

Errors:
{code:java}
Mesh 'ControlPointRendererMesh': abnormal mesh bounds - most likely it has some invalid vertices (+/-inifinity or NANs) due to errors exporting.
Mesh bounds min=(33.00, -155555563602465356559417344.00, 0.00), max=(49.00, -155555563602465356559417344.00, 0.00). Please make sure the mesh is exported without any errors.
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
{code}

  1. 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.

  2. Resolution Note (6000.6.X):

    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.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.