Webgpu init issues

Questions
1

I’m testing WebGPU with Babylon on Electron and running into these issues:

image
image807×239 11.1 KB

after some browsing the warnings could be due to mime type not being registered in webpackdevserver, but I’m not sure what the file server could have to do with rendering wasm…

Another thing: when I try to test it in regular Chrome (stable or beta) with the chrome://flags/#enable-unsafe-webgpu enabled Babylon still says ‘WebGPU is not supported by your browser’. Am I missing something?

2

This is not a webgpu issue but an issue within your build where BABYLON namespace was not found (eg it is not referenced from your code somehow)

3

I thought the error might be solved if the warnings were solved.

this is the only diff between it working and not working

image
image1461×425 27.6 KB

4

well this is super weird because the system error is about a missing ref to BABYLON

5

I just resolved my second question: I should have used Chrome Canary and not Chrome Beta.
Now at least I got the playground working in Chrome and it gives the same warnings, so those are not the problem.

image
image859×578 38.8 KB

1 Like
6

this is where the error is (while calling engine.initAsync())
(I’m using the latest alpha, and nowhere do I reference BABYLON. directly)

image
image502×757 38.7 KB

7

let me add @syntheticmagus

8

Are you using ES6? We need BABYLON to exist in the global namespace because of some initialization code for the TintWASM module. So, in ES6, you have to do something like:

import * as BABYLON from "@babylon/core";
(window as any).BABYLON = BABYLON;

We will need to get rid of that, but for the time being it’s required.

1 Like
9

we need to make sure we track the need to get rid of it to not forget :wink:

10

ah, that is a simple solution. For now that probably means the bundle will contain all of Babylon, but that is manageable.

Not getting any errors anymore, but not seeing any meshes either. Only an all white screen (which is not the clear color) so I have some work to do :slight_smile:.
Thanks for now.

11

Is there an issue number for this? I’d like to track this one if possible :slightly_smiling_face:

12

I have created an issue:

1 Like
13

Probably related. The window babylon was fixed but still seeing the “wrong mime type” error, is this something fixable in the cdn ? or should we host the glslang and twgsl ? is there a package containing those files ? so probably I’ll need a predeploy copy command

Screenshot 2024-06-12 172409
Screenshot 2024-06-12 1724091313×132 14.1 KB

Thanks

14

I have the same error in the console with :

wasm streaming compile failed: TypeError: Failed to execute ‘compile’ on ‘WebAssembly’: Incorrect response MIME type. Expected ‘application/wasm’.

It’s a recent error that I’ve had for maybe 2 or 3 weeks, I don’t really know.

However, I load the physics engine normally :

async loadPhysic(scene) {
        const gravity = new BABYLON.Vector3(0, -12, 0);
        const havokEngine = await HavokPhysics();
        const babylonPhysicPlugin = new BABYLON.HavokPlugin(true, havokEngine);
        scene.enablePhysics(gravity, babylonPhysicPlugin);
    }

in htaccess :

AddType application/wasm .wasm

15

cc @RaananW
Do we have a server side issue?

16

Looking into that

17

Problem was resolved. Also fixed deployment so next nightly will work correctly as well.

3 Likes
18

haha I love that :smiley: Problem? Yes sir, here is the solution!

1 Like