I can’t find anything online for the havok wasm build; I suppose part of that is by design for this release.
But for the mean time I’m guessing the API glue babylon.js uses with Havok is more than enough. I’m just used to regularly needing to make raw physics calls when working with ammo.js. Man oh man, so much to learn! Love it!
So the expected workflow here is just using bjs api calls and there’s never going to be a need/usecase where we want to make “native calls” as we did with ammo.js right?
It’s so strange… a huge chunk of my work in my old project was dedicated towards getting the most use out of ammo.js. I even used it for faster raycasting. In fact I ended up using it to generate more detailed hieghtmaps 1000x faster than when using vanilla bjs 5.0 raycasting. And now I’ll probably never need any of that stuff again. I mean I’ll still need the functionality, but it’ll all be done via bjs api calls.