[ODE] dWoldStep slowdown
jmiles at pop.net
Sun Jun 11 22:16:45 MST 2006
It could be worthwhile to implement a denormal/NaN/Inf check on geom/body
positions every frame. Any object with bogus floating-point values would be
reported to the app via a callback, where it could be flagged for
correction, debugging, or deletion.
Maybe dGeomSetInvalidPositionCallback() or something like that...
> -----Original Message-----
> From: ode-bounces at q12.org [mailto:ode-bounces at q12.org]On Behalf Of Jon
> Watte (ODE)
> Sent: Sunday, June 11, 2006 9:04 PM
> To: LR
> Cc: ode at q12.org
> Subject: Re: [ODE] dWoldStep slowdown
> LR wrote:
> > Do you think it's a float problem ? Double should resolve it ?
> When i look a
> > my first body position (after the first dWoldStep slow down)
> x=y=z=nand ....
> That's your problem right there. Figure out why that's happening, and
> cure it. Add a bunch of asserts in lots of places, and figure out why
> something goes NaN.
> Anything that's not a regular float (say, a NaN, Inf or denormal) will
> slow down the FPU significantly, as it's an "exceptional case."
> / h+
> ODE mailing list
> ODE at q12.org
More information about the ODE