ODE spamming "vector has zero size"
Google turns up a lot of results but no definitive explanation for what causes it or what to do about it. Also of note that I'm using the tao C# wrapper so I can't use a lot of the low level hacks suggested in some of the google results. Can anyone else shed some more light on this?
a normalisation gone wrong? Spamming the debugger output should only occur in debug builds though.
If you have a mesh, look for degenerate triangles (area of triangle roughly 0). If you do a cross product of two edges, get the length (squared) and the result is around 0, you have a degenerate triangle.
If you have a mesh, look for degenerate triangles (area of triangle roughly 0). If you do a cross product of two edges, get the length (squared) and the result is around 0, you have a degenerate triangle.
Currently I'm not using trimeshes, dBodyAddTorque seems to be involved but I don't know if its the root cause or just triggers it. Usually its just console spam but after a while it will completely break the simulation.
EDIT:
just a update it seems like setting a mass or density lower than .01 can get interpreted as 0 mass or 0 rotational inertia
[Edited by - Kaze on August 19, 2008 5:32:54 PM]
EDIT:
just a update it seems like setting a mass or density lower than .01 can get interpreted as 0 mass or 0 rotational inertia
[Edited by - Kaze on August 19, 2008 5:32:54 PM]
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement