Real-Time Physics Simulation Forum

Re: Error Overflow in AABB, object removed from simulation

2022-09-24T12:29:02+00:00

ok I think I tracked it down, the error is not actually a valid report, it may have little or nothing to do with AABBs, but it happened when I tried to apply a faulty force calculation in a boids movment system. the Cohesion factor returned NaN which then got passed on to the physics as a force to apply, and ...it throw the error more often than not.

So it appears to be mainly due to introducing bad numbers to the Rigid body.

Statistics: Posted by Brian Beuken — Sat Sep 24, 2022 12:29 pm

Re: Error Overflow in AABB, object removed from simulation

2022-09-24T12:18:51+00:00

some years later...

I am also getting this message our of the blue, not at all sure what the issue is though, I am going to try to track it down.

Statistics: Posted by Brian Beuken — Sat Sep 24, 2022 12:18 pm

Re: Error Overflow in AABB, object removed from simulation

2017-06-19T07:39:46+00:00

Hi,

Seeing messages in the code makes me think it's important to report how you get the problem at the given email
It's certainly a hard-to-reproduct bug and asking questions with your bug report will be certainly your best chance.

Statistics: Posted by S1L3nCe — Mon Jun 19, 2017 7:39 am

Error Overflow in AABB, object removed from simulation

2017-06-17T07:13:16+00:00

Hi

I am using btGImpact and am running into the following error. When using other collision shapes the error does not occur. Any idea what is causing this and how to fix it

Thank you

Rupert

Code:

static bool reportMe = true;if (reportMe && m_debugDrawer){reportMe = false;m_debugDrawer->reportErrorWarning("Overflow in AABB, object removed from simulation");m_debugDrawer->reportErrorWarning("If you can reproduce this, please email bugs@continuousphysics.com\n");m_debugDrawer->reportErrorWarning("Please include above information, your Platform, version of OS.\n");m_debugDrawer->reportErrorWarning("Thanks.\n");}

Statistics: Posted by jdoriang — Sat Jun 17, 2017 7:13 am