Collision events are not reliably fired

I’ve forked the Jenga game and I’m trying to detect collisions between the table and the blocks, I’ve forked the game, and then added the following:

table.addEventListener('collision', function( other_object ) {  
    console.log('table collision', other_object); 
});

Dragging blocks off the tower, and letting them fall onto the table, I expect to see a collision event fired, but I usually don’t. I notice that the blocks towards the bottom of the stack behave differently than the ones towards the top, but still not really what I expected: drop a block onto the table, get a collision event.

https://timdix.github.io/Physijs/examples/jenga.html

I’m very new to both Three.js and Physijs, any suggestions are greatly welcome.

[chrisnyc]

Ok, so after finding the “disable caching” checkbox in the Chrome developer window settings… I figured out the issue is with ammo.js. The latest version of ammo.js silently breaks collision detection. Reverting to the version of ammo.js included with the example http://chandlerprall.github.io/Physijs/examples/collisions.html solves the issue. I am continuing to dig into this because I think the newer version of ammo.js is faster and I’d like to use it…

[chrisnyc]

Ok, so after a bit more investigation, it seems like changing the hostname is just a way of forcing a cache miss of some sort. The real problem seems to be with a newer version of three.js or physi.js. I’m looking at this hard and I hope to figure it out soon.