physicsImpostor.unregisterOnPhysicsCollide doesn’t seem to work Babylon.js Playground
Pinging el maestro ! @Cedric
Of course it does, when unregistering the right function
What you did was trying to remove a new function that is similar to the original one, but not the same. so it didnt find it.
#RaananW But why is console.log() not printing anything?
because you unregister the collider, so the collider doesnt run. you register it, then unregister it, so it never triggers.
That makes sense. Thanks
(Wingy hugs Arte). We had no code bug, but there was an Arte brain bug, eh? I’ve had hundreds of them. MANY of my bug reports changed from “Hey, I think this is a bug”… into “Oops, I think I had a misconception.”
I think maybe it is the word “register”. “register” is a term used for event “triggering” and event handlers. When the physicsEngine “registers” an onCollide event, then there MUST be a time when that event is un-registered… and this is where Arte takes a beautiful swan dive into Lake Misunderstandin.
Had we used “bind” and “unbind” instead of “register” and “unregister”… hmm. Events are registered, handlers are bound. hmm. Just thinkin’… 'bout words.
@RaananW… geez, good catch on the not-identical functions being registered/unreg. Holy crap, i would have NEVER seen that. Miracle catch! (bow, bow) U been well? Hope so. You too, Arte, and everyone else.