I’ve been trying to figure out how to properly use Cannon or Ammo for physics in BabylonJS but the documentation on this is very sparse. Starting with AmmoJS I’m using the npm package “ammo.js”, there also seems to be one called “ammojs” so I’m not sure which is correct but I believe the former is …

For me, I am using Ammo.js typed package to get the typescript types properly, package.json: "ammojs-typed": "^1.0.6" Then I initialize it in my async function: import Ammo from 'ammojs-typed' const ammo = await Ammo() let physics: AmmoJSPlugin = new AmmoJSPlugin(true, ammo) scene.enablePhysics(n…

Oh wow thanks! It works! :smiley:

I’ve tried both const ammo = await Ammo(); and const ammo = await Ammo.call(this); directly inside an async function that runs my entire BabylonJS app, and I keep getting an Uncaught (in promise) TypeError: this is undefined message in my console. I even tried this as specified in the README for amm…

thats kind of an incomplete example, but arrow functions do not have a “this” context, which you may not be expecting? also await Ammo(Ammo) is wrong. If anything, it’d be await Ammo().then((ammo) => { ammo maybe available here } . Idk if the ammo module returns itself, but either way, you’re prob…

@wavetro a repro could help @RaananW to do his magic a lot

@jeremy-coleman You’re right, I should probably provide more context. @sebavan @RaananW You got it! Here’s a copy of my dev environment: debug/houseDev at main · wavetro/debug · GitHub

@bigrig Legendary timing! Will look into how to apply this same method in Vite UPDATE: This Webpack solution doesn’t seem to be as plug-and-play with Vite. I tried porting that Webpack method into a vite.config.js file like this, even after running npm install on kripken/ammo.js and fs: export def…

change your index.html to: <html lang="en"> <head> <meta charset="UTF-8" /> <title>houseDev</title> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <link rel="stylesheet" href="./style.css"> </head> <body> <script src="https://preview.babylonjs.com…

This is an emscripten issue that I hope they will resolve. Short explanation - when running as es module, you don’t have the global context (when running functions in a module. i.e. - this is undefined). hence - it is not possible to assign anything to the global namespace. but emscripten is still …

It will actually load faster and compile faster by using the script tag. It will load faster because it will be parsed in a different thread by chrome and compile faster because it wont be compiled at all. Doesnt really matter tho i guess.

Using AmmoJS with Babylon

Questions

bigrig January 31, 2023, 5:08am 15

Oh, I just posted a quick code snippet in the tutorial section on this topic. Getting ammo setup with webpack - #3 by bigrig

Topic		Replies	Views
Including Ammo.js with BABYLON using Nodejs Questions	10	4154	April 19, 2020
Cannot set properties of undefined Ammo Bugs documentation , tutorial , ammojs , physics	8	2022	August 20, 2024
Ammo with BabylonJS & Angular Questions	13	1595	September 22, 2021
Ammo.js webpack issues Questions	36	6876	March 7, 2023
CANNON/OIMO/AMMO TypeScript/Webpack example please? Questions	10	2787	April 19, 2020

Using AmmoJS with Babylon

Related topics