Contributing to documentation 101

[Guest]

You are right for the scene parameter. This is because we track the meshes for you so you don't need to bother about disposing them if we dispose the scene.

[Dad72]

19 hours ago, Zephos said:

For example, creating a primitive mesh requires a scene object in its constructor, so you can't create a mesh and add it to the scene later... it has to be added immediately.

You can also loaded  it and hide it with setEnabled (false) or isVisible = false

Then display it only when you need it.

[Zephos]

6 minutes ago, Dad72 said:

You can also loaded  it and hide it with setEnabled (false) or isVisible = false

Then display it only when you need it.

I realize that, but there are times when I might want to store a bunch of meshes that may or may not be added, and having to add them to the scene and hide them seems less efficient. Maybe I am wrong though... not sure how much overhead a mesh adds to processing if it is hidden.

[Guest]

Then you can use container

http://doc.babylonjs.com/how_to/how_to_use_assetcontainer

[V!nc3r]

I just see this thing, nice!

[Guest]

Yeah! I'm proud of this one