In angular the SceneLoader.ImportMeshAsync have not any response

Bugs
1

My enviroement is angular8， and the babylonjs is ok ,and it can create sphere and run ok.
But when I use the SceneLoader.ImportMeshAsync to import mesh of localhost, it is not work. I debug the progress is finished， however, the promise have not any response.

131635484-03fee461-0bb0-4bb0-a575-22a1f0e404ff
131635484-03fee461-0bb0-4bb0-a575-22a1f0e404ff1456×708 90.4 KB

And the code is on below:

 ngOnInit() {
var canvas: any = document.getElementById("renderCanvas");
var engine: Engine = new Engine(canvas, true);

var scene: Scene = createScene(engine, canvas); 
var camera: ArcRotateCamera = createCamera(scene, canvas); 
var building = createBuilding(scene); // the buiding is sphere

SceneLoader.ImportMeshAsync(null, "./assets/mesh/", "2f.gltf", scene, (progress) => {console.log(progress)}).then((result) => {
  console.log('hello');
}, (error) => {
  console.log('world');
  console.log(error);
});

engine.runRenderLoop(() => {
    scene.render();
});
}

so, I test the code in javascript environment, and it is work.
I think maybe the npm package has bug.

At last, I find the problem. On the line 143259 of node_modules/babylonjs/babylon.max.js. The if condition is false.

I modify as below:

// if (request.readyState === (XMLHttpRequest.DONE || 4)) {
 if (request.readyState === XMLHttpRequest.DONE || request.readyState === 4) { // [debug]

I hope offical to modify it. Now, I just load the babylon.max.js in angular.json, but can not import the babylonjs in the .ts file.

2

What browser are you using?

It feels like XMLHttpRequest.DONE in your browser is, for some reason, wrong? (i.e. not 4)

This line, though a bit cryptic, should work the same, if you have XMLHttpRequest.DONE defined correctly or not at all

1 Like
3

My browser is chrome. And I print the XMLHttpRequest.DONE，it is a function!
Should I declare the type anywhere?

4

This should not be a function. No idea what defines it, but this is incorrect. This is the standard value:

image

Check a different browser tab and see if it is still a function.

1 Like
5

O, I find the problem. Because the zone patch the XMLHttpRequest, and all the attribute has been changed.

I think this is the problem of zone in angular.

So I submit a issue to the zone in github.

Thanks.

1 Like
6

They should never change system variables. I wonder what is the reasoning behind this…

Glad you could find the issue!