version 2.3.3
There is a problem with the collision detection of 3D object in the cannon.js library when you use a maxSubStep bigger then 1.
When for exemple you set “maxSubStep=2” the interalStep code will run twice for every word step update and if the collision happen during the first internal step, the second one will wipe the ‘contacts’ list (contacts.length = 0) and therefore the step code that run once per frame will only see the contact list from the second pass of the internalStep.
I’ve compared the modified code of the cocos/cannonjs library from the old original cannonjs version 0.6.2 and discovered that the "World_step_oldContacts"code that run inside the internalstep was moved elsewhere on the cocos version so that might be why we have this issue.