Hi,
I'm running a simulation of a few thousand RBDs (small shards – exploding windshield), and I realized that at the end of the sim almost half of my RBDs are “gone”. Upon further examination it turned out that the geometry point coordinates of the disappearing pieces became NaNs – this coming from the DOP network where these pieces' sim attributes became NaNs as well.
(The event that triggers this seems to be a collision, as on the same frame it becomes NaN-ned, an Impacts data also appears on the object)
I'm currently experimenting with various solver settings and whatnot that perhaps would get rid of this problem.
Anyone seen such a thing before?
cheers,
imre
DOP RBD NaN problem
4608 3 0-
- riviera
- Member
- 1721 posts
- Joined: March 2020
- Offline
Imre Tuske
FX Supervisor | Senior FXTD @ Weta FX
qLib -- Houdini asset library
http://qlab.github.io/qLib/ [qlab.github.io]
https://www.facebook.com/qLibHoudini [www.facebook.com]
FX Supervisor | Senior FXTD @ Weta FX
qLib -- Houdini asset library
http://qlab.github.io/qLib/ [qlab.github.io]
https://www.facebook.com/qLibHoudini [www.facebook.com]
-
- berniebernie
- Member
- 5 posts
- Joined: Jan. 2016
- Offline
Bumping this thread from spacetime but no one has really answered this on the forums.
Is there any ways to debug NaNs?
I'm in a somewhat similar situation, i'm pretty sure my collision objects which are growing and changing shapes are affecting the sim and blowing up forces (division by 0?), but I can't find a way to debug the scene(s).
Is there any ways to debug NaNs?
I'm in a somewhat similar situation, i'm pretty sure my collision objects which are growing and changing shapes are affecting the sim and blowing up forces (division by 0?), but I can't find a way to debug the scene(s).
-
- tamte
- Member
- 9384 posts
- Joined: July 2007
- Offline
-
- mkarlowski
- Member
- 1 posts
- Joined: Feb. 2020
- Offline
-
- Quick Links


