Introducing Babylon Lite

Announcements
21

We will update the doc with the list live :slight_smile:
cc @PirateJC

image
image1332×1218 69.2 KB

image
image1132×1230 64.5 KB

image
image1177×1190 62.5 KB

image
image1167×1147 70.5 KB

image
image1125×1223 67.6 KB

image
image1126×1203 81.7 KB

image
image1212×1212 69.2 KB

6 Likes
22

Thanks :slightly_smiling_face:

Speaking of migration: Vector3 is going to hurt :face_with_crossed_out_eyes:

1 Like
23

I tried Babylon.js Lite.
I was able to port the basic sample, but I’m stuck on the following:

  • I can’t load the Fox glTF model.
  • I can’t display dust particles.
  • The way Skybox is used is different from before.

That’s about it for now.

image
image852×754 146 KB

24

what is the error with fox?
for particles they are not yet supported (but @AlitarSemiramis is on it)

1 Like
25

also you have more than 100 scenes in the repo with their babylon equivalent if you want inspiration

1 Like
26

Wow, it’s crazy. I like it a lot. I’m preparing a version 3 of my editor, when I see this, I tell myself that version 4 should follow. But I admit that I am not reassured. I risk breaking everything if something no longer exists. But it’s worth it I think.

As some say, a list of what no longer exists would be interesting. A list of what remains to be done, documentation to migrate as easily as possible without having to relearn everything.

In any case, congratulations for that. It seems incredible, promising…

Babylon (lite or not) is a great engine.

3 Likes
27

So that’s an apples-to-apples comparison right, both Babylon.js and Babylon Lite using WebGL WebGPU renderer?

28

This! Also device input manager seems to be missing?

Is there any kind of timeline of how the missing features are prioritized, and when to expect some feature parity with the Babylon.js version? Is everyone on the summer holidays already and we/me can assume these come during autumn? :grin:

So eager to port this already, but I think for now, there are so many crucial features missing that it would become a hassle! (For example, null engine, device input manager, particles, audio…)

29

both engine using webgpu actually

1 Like
30

I shared the list earlier and we have A LOT already :slight_smile:

Particles are the big ones missing but they are on the work

1 Like
31

Sorry typo on my part

32

so yes apples to apples ;D

1 Like
33

The only thing that saddens me is that I have the impression that it can’t be used with <script> Because I don’t understand anything about this :

# 1. Install all workspace dependencies (links the babylon-lite package)
pnpm install

# 2. Install Playwright browsers (needed for parity & bundle-size tests)
pnpm exec playwright install

# 3. Start the dev server (builds bundle scenes, then launches Vite on port 5174)
pnpm dev:lab

Can we integrate babylonLite via <script>

I hadn’t paid attention, but there is a small migration guide :

34

Yes because UMD prevents us from treeshacking correctly. BUT you can still import using scripts:

To use modules in an HTML document, you must specify type=“module” in the tag.

35

~3–4× faster is effing incredible. So that’s all down to having a lean, efficient codebase (functions over classes, data over objects etc)?

2 Likes
36

Yes, I can see where to put type=‘module’. Do you have a concrete example of integration?

37

Yeah sorry I didn’t look into that thoroughly… It didn’t mention audio and device manager though, or if it did I need to get my eyes checked! :grin:

There are so many goodies already there! I thought cascaded shadows were not implemented yet but I was wrong!

1 Like
38

correct and thinking the engine for webgpu only instead of having a neutral layer.

1 Like
39

hold my beer, let me create that for you

1 Like
40

webaudio is coming soon from @RaananW

2 Likes