syuilo
July 28, 2026, 11:56am
1
I updated from 9.15.0 to 9.18.0, but now this error occurs every time I destroy the Engine.
I’m using WebGPU and a pure import.
I am not using the “Custom Loading Screens” feature.
I’m sorry, but I haven’t been able to set up a reproducible playground yet.
Thank you for this great lib!
The problem with no repro is that we have nothing to check and I cannot repro either
syuilo
July 29, 2026, 1:30am
3
I apologize for not being able to provide clear reproduction steps.
After investigating, I found that calling RegisterAbstractEngineLoadingScreen resolves the error.
Is this intentional? As mentioned earlier, my project does not use a custom loading screen, nor has Babylon ever displayed any “Loading UI”.
Therefore, requiring this import feels unintuitive.
I will check if the side effects removal missed this extra call. Loading screen was always a side effect, but if we are missing the function registration in the side effects it’s a mistake on my side and it will be fixed.
Just wanted to update - this was fixed and merged yesterday
syuilo
July 30, 2026, 1:09pm
6
Thank you for the quick fix!