Does Babylon.js or Three.js perform better with more meshes?

[aFalcon]

@gryff GOLD!!!

@gryff

vertices can pile up more quickly than you think if you don’t think about good UV mapping.

123456789

24 vertex count, with texture UV, on a box - that makes SENSE!

Can it go lower, with BAD UV MAPPING?

Found a way.

But didn’t know about INSPECTOR, OR how to use it to count VERTICES like that.

Cool

Thanx G!

---

Ah…

I just want to say LIKE this THREAD so MUCH!

LIKE - what @jerome says about

• every scene needs to be optimized in different ways. AND,

@Deltakosh - the perf ops of runtime animations - in RELATED thread - is especially helpful.

Animation performance drop by translation/rotation

As I briefly mentioned in another thread my bottleneck in a scene is the animation: [animationperformance] This scene has two instanced animated objects (plus the original mesh) loaded from a gltf file with BABYLON.SceneLoader.LoadAssetContainer and container.instantiateModelsToScene. At first glance I thought this was caused by the bone animation, but it turns out this is not the case. The problem is reproduced here: https://www.babylonjs-playground.com/#4ZVNJJ#3 Moving the meshes (by setti…

For review, and OTHER PERF OPS TIPS, more comment on that thread.