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.
Comments (1)
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
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
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?