Hello, I hope everyone is well! I’m reporting this bug because I believe other people may experience it. I don’t think the problem is with Babylon, but rather with Chrome’s WebGL implementation. But I also write hoping that someone has some clue as to what it could be. Since yesterday, some users …

Seems to be related to chrome having a bug with UBOs… You can use scene.getEngine().disableUniformBuffers = true; to disable them on your experience. I will add a way to auto disable them in 120+ chrome mobile versions… and ping the chrome/edge teams as well

Are you sure it’s not fixed by reverting Babylon? I’m not at my dev place right now. Also: I think you can install older Chrome versions to see if it’s Chrome. I will try that tomorrow.

@mise I’m using Babylon v5.50.1 (I didn’t upgrade to 6.x yet), and yes, downgrading Chrome solves the problem (so I’m pretty sure the issue is with the latest Chrome upgrade). Thanks for your help

I have this issues as well: Chrome 120.0.6099.43 Android 14; Pixel 8 Pro Getting started Chapter 2 texture: https://playground.babylonjs.com/#KBS9I5#71 Initial load shows this: [image] Refreshing shows this: [image] Refreshing shows only the box, sometimes if shows the roof, but not the bo…

Passing disableWebGL2Support: true in to the engine fixes the issues (using webgl1) It seems that if you disable the first mesh wait a few seconds and then the other meshes appear. Then enable the first mesh.

Thanks for your effort! Can we get some more eyes on to this? is a workaround possible in WebGL2? if this is truly a bug in Chromium, does the Babylon crowd have a more direct link to the Chromium team?

[image] mise: if this is truly a bug in Chromium, does the Babylon crowd have a more direct link to the Chromium team? Don’t know. Anything Yours can do to accelerate the process since definetely looks like a bug from latest chrome update for mobile? cc @RaananW

Hello, I hope everyone is well… I would be very grateful if those who had the problem could comment on the Bug Report I opened about this problem: https://bugs.chromium.org/p/chromium/issues/detail?id=1510149 @Matthew1 @mise

I once had an issue where loading textures was unsuccessful, and the debugger found that the network completed after the request, but the then function was not called normally. The then function is triggered only after any operation is performed on the scene. This issue does not resolve by refreshi…

The workaround will be added to the next Babylon version Disable UBOs in Chrome mobile... by sebavan · Pull Request #14603 · BabylonJS/Babylon.js · GitHub

I added to the chrome issue the right list of ppl to fix it :slight_smile:

Problems on Chrome Mobile since December 7th, 2023

Bugs

mawa December 14, 2023, 12:52pm 23

more reports coming in:

Topic		Replies	Views
Mobile chrome fun Questions	1	358	December 14, 2023
Babylonjs takes longer to render the first frame on mobile compared to Threejs Questions material , performance	7	1425	May 30, 2023
WebGL Performance Regression in Chrome? Older Demos Run Significantly Better on Firefox Questions	29	982	January 5, 2026
Disappearing meshes on mobile device Questions	5	765	October 11, 2019
`engine.disableUniformBuffers` is set to false in mobile mode, and cause a bad performance Bugs material , performance	3	566	May 30, 2023

Problems on Chrome Mobile since December 7th, 2023

Related topics