Some breaking changes to expect

Hey team!!

As we are walking towards having a more modern internal architecture for Babylon (see Babylon 10. The first blog I wrote to announce… | by Babylon.js | Medium), I would like to take some time to set some expectations for the upcoming weeks :slight_smile:

We are working on porting most of our main shaders to WebGPU in order to have WebGPU as a first class citizen to be future proof.

While doing that we are trying to optimize the size of our package by delay loading shaders (you do not want to load webgpu shaders in webgl and vice and versa).

This should be almost transparent as everything shader related is already asynchronous by nature.

THAT BEING SAID, we will obviously find problems along the way and I would like to ask for everyone patience and understanding.

We are trying to capture all the breaking changes right here: Babylon.js Breaking Changes | Babylon.js Documentation (babylonjs.com). If we miss some, if you find an issue not documented, please speak up (or even better help us fix it ;)).

This is the first step in a long series (more to come later with Render Graph integration :)).

I love this community like a family and I know these changes are painful. But they are necessary and we are working super hard to make them as subtle as possible from the user standpoint.

Thanks again for your comprehension!

46 Likes

We love you too bro! :heart_eyes_cat: All of you :wink:

6 Likes

It makes sense that babylon.js won’t always be able to be 100% backwards-compatible while still making advancements. It would be a pity to prevent improvements for ever, trying to always keep full compatibility. So I’m looking forward to seeing what improvements / optimizations come out of these architecture modernisations!

3 Likes

We’re patiently supporting the team! Please do not worry about breaking changes, every 10 years is fine :wink:

5 Likes

We are cheering for you and the team - in Kosh we trust💪

image

Let us know if there is anything we can help with :smiley:

2 Likes

Yes. I can agree with this. At some point, there’s no other choice. You just have to move on (or you are out of the game :sweat_smile:). Just mind to keep with the pillars, vision and DNA…do what you have to do, and it’s gonna be just fine :smile: :relieved:

4 Likes

Looking forward to next big version of Babylonjs!
Thanks for your great working!

2 Likes

Thank you for pushing forward with WebGPU!

Does this also include WebXR?

I found this repo: immersive-web/WebXR-WebGPU-Binding (github.com) which had a commit 5 days ago, so it seems up to date at first glance. I really hope it’s something that can be used to improve WebXR performance.

1 Like

Question for @RaananW but I don’t think webXR is yet compatible with WebGPU (I can be totally wrong though)

not yet, no. Would be great though :slight_smile: