chrome is about to release a new upgrade - 146. it’s already available in the chrome 3 dots / help / about.
after installing this upgrade, my web site that use babylon 8 AWS works fine with glb that has no images but if glb contains images for material albedo, there is no rendering.
this issue is not reproduced on playground.
trying to load images from my disk using the inspector also not working.
AI failed to fix it…
2 Likes
after treating err.errorCode==3000 properly the scene rendering is working but still, no images
We need a repro as it seems all ok on main/dev/canari for me on win and for @Deltakosh on mac.
Can you share a way for us to repro so that we address the issue ASAP ?
2 Likes
I have the same problem. Please address this properly, officials.Upgrading the Chrome browser causes texture corruption.
1 Like
To help us resolve the issue quickly, would you have a repro we could look at?
We have not been able to reproduce it ourselves.
Thank you in advance!
Are you using ktx twxtures ? Cc @RaananW to double check the loading path as it seems to be ok in the pg ?
yep, all seems to be fine, but i will be happy to see a reproduction. we might have missed something that i didn’t enticipate.
all types seem ok here https://playground.babylonjs.com/#E4VDDW#28
It appears that there are anomalies in parsing Base64 data, particularly for JPEG-formatted Base64 strings,Base64-encoded PNG images also have the same issue.
I encountered the same problem.
The following is a model using glTF Base64 embedded data.
It displayed correctly in Edge 145, but it seems to fail to load the Base64 data in Edge 146.
https://cx20.github.io/gltf-test/examples/babylonjs/index.html?model=Duck&scale=1&type=glTF-Embedded
(https://cx20.github.io/gltf-test/sampleModels/Duck/glTF-Embedded/Duck.gltf)
Edge 145
Edge 146
Thanks for the reproduction!
Here’s the fix:
2 Likes
I directly loading a serialized model using the API: BABYLON.SceneLoader.ImportMeshAsync("", url, sceneFileName, this.scene, null, extension), and passing a JSON string directly to load it, but this still results in an error. What should i do?
The PR must be merged before the fix is enabled. It should be done today, so the Playground will have the fix tomorrow.
Thanks for the fix.
I assume that tomorrow we will have a new version and we will be able to upgrade our babylon version.
Am I right?
Meanwhile, I am trying to create a patch.
Can you help me by specifying the file names that should be patched?
AI says i should use
babylon-build\packages\public\umd\babylonjs-loaders\babylon.glTFFileLoader.js
babylon-build\packages\public\umd\babylonjs-loaders\babylon.glTFFileLoader.min.js
is it correct?
You can find the changes here:
But it may be difficult to find the original code in the mininified package, because it may be different because of the minification…
A new npm has been deployed a few min ago
2 Likes
I just tried version 8.55.3 and there are still issues. Has this version been updated yet? Or does it only fix the import of models like glTF, while other import methods—such as importing serialized strings to generate models—have not been fixed yet?
The Playground has been updated:
- 8.55.2 (doesn’t work): Babylon.js Playground
- latest (works): Babylon.js Playground
The Sandbox is also updated.
What doesn’t work for you? Are you able to setup a repro?
I use the code let str = BABYLON.SceneSerializer.SerializeMesh(this.rootNode, false, true) to save model files (in JSON format) that contain embedded base64 images, then load the saved files via BABYLON.SceneLoader.ImportMeshAsync("", "", "data:"+JSON.stringify(str), this.scene, null, ".babylon"). This is causing issues for us now, though everything worked perfectly fine before the browser was updated.
Can you please share a repro in the playground ? We will fix it as soon as we have it.