[ODE] dBodyGetPosition() returning non-numbers after collision

[Jon Watte]

What I've found helpful is to reproduce the case (sounds like you 
have done so), and then set a data watch breakpoint on the specific 
variable that goes NaN. The debugger will then tell you where the 
bad data is coming from, and you can look up the stack at that point 
to figure out what went wrong. You may need to repeat this, or 
couple it with regular break points, to get to the heart of it, but 
a repeatable test case is the first order of the day.

Cheers,

			/ h+


-----Original Message-----
From: ode-bounces at q12.org [mailto:ode-bounces at q12.org]On Behalf Of Geoff
Carlton
Sent: Tuesday, October 12, 2004 9:35 PM
To: ODE mailing list
Subject: Re: [ODE] dBodyGetPosition() returning non-numbers after
collision


Well,
Just glancing through the code, it looks ok.  I set the contact 
parameters after dCollide, but I wouldn't think dCollide would stomp 
them so it shouldn't be any different. 

Can anybody else see any problem here? :-)

Geoff
_______________________________________________
ODE mailing list
ODE at q12.org
http://q12.org/mailman/listinfo/ode