Trying to get es6 Havok working, odd error

Questions
21

Hey everyone! I’m facing the same issue trying to import Havok to my Vite/ReactTs project. Did you manage to solve it?
image

1 Like
22

No, I never did but am looking at doing a havok deployment here soon and will need to figure this out as well!

1 Like
23

Same issue, using Vite

24

I believe adding this section to vite.config.ts fixed it for me:

export default defineConfig({
…
optimizeDeps: {
exclude: [“@babylonjs/havok”],
},
…
})

see: babylonjs-vite-es6/vite.config.ts at f8cd66e0e2cd84c5f392994bfe76af922bedd355 · knutsoned/babylonjs-vite-es6 · GitHub

1 Like
25

This did not work for me unfortunately. Went back to using the bun bundler and copied over HavokPhysics.wasm to my build directory manually, and that worked.

26

Isn’t this the same issue?

27

cc @RaananW FYI

28

This is becoming a major blocker for me, I really need to figure out how to get this working with webpack 5.

We were able to get it to work with Mac and Linux, but when its a PC trying to load it this magic word problem just keeps happening no matter what we have tried.

1 Like
29

Can you share the method you are using to load havok using webpack? I have added a Havok sample to the template which also works under windows. there shouldn’t be any OS-related issues TBH.

The magic-word thing usually happens when the server returns an HTML or a 404 instead of the right content. are you sure the request goes through correctly?

30

Yes because it’s working on the Mac with the same setup. On that it’s returning a ~2 mb wasm file in the net report. On the PC it’s returning two ~6 mb wasm files that appear to be array buffers instead. Im importing it just how it’s been demonstrated to work, it’s really tripping me out that the exact same code is working for a different OS.

I’ll post the code and the relevant webpack stuff here in a couple of hours when I get to work.

1 Like
31

Here is how I’m importing it.
image

and here is how I’m initializing it.
image

Originally we had our webpack config looking like this:
image

But that was making the same error pop up even for Mac and Linux. So we changed it to this:
image

And it started working for those two platforms, but remains being a problem for windows.

Is it a pathing thing with windows and the exclude possibly?

32

I am not sure why you would need the wasm loader in this case. Webpack will take care of the wasm file just like any other asset and will let havok load it correctly. At least this is my experience with webpack and havok. What happens if you remove the webassembly-loader? does it not initialize?

33

The same results, I tired that yesterday as well.

I did not check if when that is removed if it works for Mac or Linux though, ill check that when I can get a change to rotate back to this topic. Unfortunately on other bugs right now so it might take a second.

34

can you share the project? or a reproduction?

35

Its for Frame, so it would be extremely hard to share. I can possibly recreate though. Let me check about nerfing that wasm loader if it still works for Mac and Linux. Then ill see about making a simplified recreation.

1 Like
36

does the webpack template on my repo work, or does it fail the same way?

37

Ill clone that and check.

1 Like
38

Ok, this is gonna sound dumb af… buuuuuut.

I deleted my node_modules folder, deleted my dist and package lock. Got rid of the wasm loader in the webpack config annnnnd it started working.

Smh… I waisted so much time on this.

1 Like
39

Getting rid of that broke the way we load other wasm stuff, but I was able to change the rule to:

 {
        test: /vendor\/.*\.wasm$/,  
        use: [
          {
            loader: "webassembly-loader",
            options: {
              export: "buffer",
            },
          },
        ],
      },

and now we are off to the races!

3 Likes
40

This worked for me, thank you

1 Like