Search Issue Tracker
Won't Fix
Votes
0
Found in
4.3.3f1
Issue ID
613308
Regression
No
Setting Time.timescale to zero and back to a non-zero value causes Interactive Cloth component to spew out errors
Steps to reproduce:
1. Create a project which makes use of Interactive Cloth
2. Set Time.timescale = 0f;
3. Set Time.timescale = 1f;
4. Errors will be thrown:
IsFinite(outDistanceForSort)
IsFinite(outDistanceAlongView)
IsFinite(outDistanceForSort)
UnityEditor.DockArea:OnGUI()
IsFinite(outDistanceAlongView)
UnityEditor.DockArea:OnGUI()
This can be workaround by setting timescale to a really low number instead of zero. For example 0.00001f;
This is not going to be fixed as Unity 5 will have a new Cloth component.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Michieal
Aug 29, 2014 01:37
This error occurs even without having a cloth component. I have a skinned mesh render (main Player object) and I get this error all the time. Also, I get it on the trees, attached to the terrain. (And even though the error says that it applies to the tree nodes, I only have meshed trees, not noded trees.)
Can you please fix this EVEN though we are getting a new, really cool cloth component? Please?