Update the PG of the Documentation DEMOS for Sceneloader ImportMesh, Append

[ryantrem]

@Dad72

Then compare on this PG. You will see that a light is added with BABYLON.LoadAssetContainerAsync

If you look at the inspector, we see that a ‘lamp’ was added.

Yes, this is exactly the expected behavior. The .babylon file you are loading has Lights in it. When you use ImportMeshAsync, you are import meshes only. Everything else in the file is ignored. When you use LoadAssetContainerAsync, you are bringing in everything from the file, and if you call addToScene with no arguments, you are adding everything to the scene (including lights). If you added only meshes (e.g. result2.addToScene(entity => entity instanceof BABYLON.AbstractMesh)) then the behavior is exactly the same as ImportMeshAsync. This is why we felt like LoadAssetContainerAsync is probably a superset of the functionality of ImportMeshAsync.

@Dad72

@ryantrem For the error, I think I understood what is happening.
Logically the path of my model is in this form:

…/GameClient/Data/Meshes/Props/barel.babylon

But using LoadAssetContainerAsync This removes all capital letters:

…/gameclient/data/meshes/props/barel.babylon

I think you are saying the error is because your code converts the url to lower case, but if I’m misunderstanding and you think there is a Babylon bug, let me know!