THREE.Matrix4.getInverse() is removed in the version of THREE.js that is used in A-Frame master & will be used in A-Frame 1.4.0.
This PR patches three-to-ammo to no longer use getInverse()
I had planned to upgrade to three-to-ammo 1.0.1, which also includes this fix, but that's not straightforward...
1 - three-to-ammo uses ES6-style imports, which aren't compatible with browserify. Requires setting up babel or (my preference) moving from browserify to webpack.
2 - three-to-ammo API has changed significantly from 0.1.0 to 1.0.1 requiring a rework of the integration in this repo.
I've done the work for 1 (moving to webpack), which I'll file as a separate PR. I didn't want to take on the complexity & risk of 2 just now - hence this PR to at least get aframe-physics-system ready for A-Frame 1.4.0.
THREE.Matrix4.getInverse()is removed in the version of THREE.js that is used in A-Frame master & will be used in A-Frame 1.4.0.This PR patches three-to-ammo to no longer use
getInverse()I had planned to upgrade to three-to-ammo 1.0.1, which also includes this fix, but that's not straightforward... 1 - three-to-ammo uses ES6-style imports, which aren't compatible with browserify. Requires setting up babel or (my preference) moving from browserify to webpack. 2 - three-to-ammo API has changed significantly from 0.1.0 to 1.0.1 requiring a rework of the integration in this repo.
I've done the work for 1 (moving to webpack), which I'll file as a separate PR. I didn't want to take on the complexity & risk of 2 just now - hence this PR to at least get aframe-physics-system ready for A-Frame 1.4.0.