SvenFrankson

Indeed it seems like you may not use an image. https://github.com/BabylonJS/Babylon.js/blob/master/gui/src/2D/controls/slider.ts It could be possible to add images as an argument, with a set of 3 pictures "done", "undone", "thumb" to make it more customizable, with "done" and "undone" overlapping accordingly.

In case it help, I did some camera for flying spaceship for this demo Here is the script about the flying camera following the spaceship : https://github.com/SvenFrankson/space-scout/blob/master/scripts/SpaceShipCamera.ts Line 55, there's an update loop for the camera. Main idea is that I keep an empty mesh at a fixed position relatively to the spaceship (it's the vector named _targetPosition), and lerp to it each frame with a smoothness factor. It makes the camera go to a point with some delay, so when spaceship accelerates you feel it a little more because it goes further

Have you tried checking the real value of numBoneInfluencers on your mesh ? For example, add in your loading method, where myAnimatedBinder is your animated mesh. alert(myAnimatedBinder.numBoneInfluencers) (debugging mobile like a boss, but note that alternative and more sophisticated methods involve a properly setup Safari browser and a USB-Iphone cable...) If it says less than 4, some bone influences might be dropped, causing the holes...

Is the binder animated with bones ? If so maybe it's because of limitations about the "bones per vertex" number ? I think it's low for mobiles (documentation says 3 on mobile, 4 on desktop https://doc.babylonjs.com/how_to/how_to_use_bones_and_skeletons )

Hi, You can add a resize after the first frame, it will be ok. this.animate(); setTimeout( () => { this.engine.resize(); }, 100 ); (but it's a fix, I don't really understand why the issue happens in the first place, I also experience it quite often)

If it's only one station you wan't to display, I'd say your problem could come from the fact your meshes are not designed to be used in a real time application. Where did you got them ? Every 3D drawing software has a decimator tool to reduce the amount of triangles in a model, try using it on pieces too detailed. The fact you want to keep the ability to pick meshes make it harder to reduce the mesh count. I'd try something like this : https://www.babylonjs-playground.com/ts.html#IDBWZN#1 The rail sleepers are merged together, so only 1 draw call, but when picking yo

That's really great, thanks a lot !

I think each mesh requires as many draw calls as it has subMaterials, which would explain the huge draw calls count. Any hint about what you are trying to render ? A full city ? A very detailed building ? The easiest way to improve performances would be -> Freeze meshes not moving. If a mesh only move "sometime" (on user input for example), keep it frozen when it's not. There's some true optimization here, if not done already. -> Merge meshes sharing materials together, you will reduce the draw calls count, also some true optimization. It's harder, but you will a

Oups, indeed kurhlaa is right here

Maybe it will work with X = sqrt(3) and Y = sqrt(3) ?

I need something like this too (removing textures from imported material), the way we do it is $.json( { url: "model.babylon", success: (rawData) => { data.id = "newId"; data.mesh.material.id = "newId"; BABYLON.SceneLoader.ImportMesh( "", "data://" + JSON.stringify(rawData); scene, (meshes, particles, skeletons) => { // success callback } ) } } ) (It's pseudocode, the success callback in the first $.json call is likely to be much more complicated...) The idea is you first load the

Mine too, but why would you assume it's a deletion ? It looks like a bug...

Great job ! Is this app made only using your "Interactivity without coding" feature ? Are the handles in the scene (the blue arrow moving the cameras for example) from a ToolBox in your software ?

Are you sure we can ? I don't fully understand how SubMesh are implemented, but it seems copying the array would not set subMesh._mesh or subMesh._renderingMesh,

What about this feature ? https://playground.babylonjs.com/index.html#6FLBU3#2 I often need to extract VertexData from meshes with submeshes, but it ignores the submeshes. Maybe there's already a way to do it without keeping track of the submesh indexes along the VertexData ?