problem: AmmoPhysics is not a constructor ?

[pigLoveRabbit520]

enable3d is installed by npm.

here is my code:

import { Project, Scene3D, PhysicsLoader, AmmoPhysics } from 'enable3d';

....
const physics = new AmmoPhysics(this.scene);
physics.debug.enable(true)

and I got error:

Uncaught TypeError: enable3d__WEBPACK_IMPORTED_MODULE_1__.AmmoPhysics is not a constructor

[yandeu]

Do you want to use enable3d as a physics extension for three.js? Then you don't need to install enable3d. You need the package @enable3d/ammo-physics.

[yandeu]

I will write a better documentation about the different npm packages.

[pigLoveRabbit520]

@yandeu thks a lot.

[pigLoveRabbit520]

@yandeu

import { AmmoPhysics } from '@enable3d/ammo-physics';
...
const physics = new AmmoPhysics(this.scene);

I got another error:

Uncaught ReferenceError: Ammo is not defined

😭😭

[yandeu]

Don't worry. I will create a small example repo later this day.

[pigLoveRabbit520]

@yandeu ok

[yandeu]

Voila: https://github.com/enable3d/threejs-ammojs-webpack-example

But there is an issue with the colors. Just create all your objects using THREE.something and it should be fine :)
Will fix it in the next version.

[pigLoveRabbit520]

@yandeu It seems I should add ammo.js to my src folder? I think it's redundant because @enable3d/ammo-physics has included it.

[yandeu]

Ammo provides a wasm version that can't be bundled. The PhysicsLoader detects if the browser supports wasm and loads the correct file.

Yes, it is included in the bundle. But I guess I can remove it from there.

[pigLoveRabbit520]

@yandeu I have to update ammo.js manually? 🤣🤣

[yandeu]

ammo.js does nearly never get updated.

[yandeu]

Also there are different ammo builds. Depending on what functions you need, you have to add a different build.

[pigLoveRabbit520]

@yandeu thanks a lot. And there are some lines around the mesh in your demo, can I hide them?