I’m wondering if there’s any word from the Box2d guys if this is going to actually get fixed properly at some point, or if it’s fixed in the daily builds? This one bug has resulted in almost two days of debugging and work arounds, and I still see it from time to time!
The bug is much less frequent following some of the very handy advice in this thread, but I’m still seeing it. Once I do more cleanup on the code, I may be able to get rid of all remaining instances of it (not my code base, I’m cleaning up/adding features), but for now, it’s just kind of causing some hair tearing. 
in my onCollision event:
self:setLinearVelocity(0,0)
self.angularVelocity = 0
self.isBodyActive = false
and in my onEnterFrame area:
if cleanupFlag == true then
local gameTheme = gameSettings["gameTheme"]
destroyBullet()
cleanupFlag = false
if cleanupIndex == 1 then
enemy:removeSelf()
createOneEnemy(gameTheme, enemy1, 1, -75)
elseif cleanupIndex == 2 then
etc....
end
The “destroyBullet” code is to get rid of the bullet object, and is similar:
bullet:removeSelf()
bullet.doneFiring = false
bullet.isActive = false
Any help or further advice of course is greatly appreciated [import]uid: 37043 topic_id: 6583 reply_id: 40194[/import]