<SOLVED>Collisions not coliding

[jcmeyer5]

[slembcke]

[jcmeyer5]

[jcmeyer5]

Eureka!! I found it. My "begin" callback needed to be a BOOL return and not a void return. Once I fixed that, I started getting impact values and the circles bounced off properly.

[jcmeyer5]

I was able to migrate the collision code back to my original classes without incident. Sweetness!

[slembcke]

Also, cpArbiterTotalImpulse() (and other functions that deal with impact values) must be called from a post-solve callback. Otherwise the values you are asking for haven't been calculated yet.

[jcmeyer5]

Just figured that out too, as I was getting intermittent values. Moving it to the postSolve gives the results I am looking for. Thanks for the help. I am going to do a search to see if I can find more details on the differences in collision callbacks.

[jcmeyer5]

[slembcke]

Aha! I think that is the same as a bug that I just fixed. It's... a little complicated to explain why it happens though. It has to do with separate callbacks that can be triggered immediately when removing objects, and scheduling post-step callbacks within them. Try updating to the latest code out of Git and see if your problem goes away.

[jcmeyer5]

I will try the code Monday. I did find a work around with switching the callbacks. I put rock removal as postSolve and damage as separate. Not sure if that switch has ramifications that I have not yet considered, but it appears to be working well.