Asset Manager Singular?

Reading through the code for Application it appears that only one AssetManager should be instantiated per application. Does this mean you cannot create multiple instances of AssetManager s running on separate threads filling up hidden Nodes with game assets that are to be attached to the root node latter in the game?

No, you can do that, no problem. 8)

You can use one asset manager from many threads (it is thread safe). This will also share the asset cache, which as you can guess is a very good thing.



Just make sure to attach any models you load by using a Callable running on the render thread.

By no means can you modify a live rendering scene graph from any thread except the rendering thread.

A) If it is thread safe then does itself spawn threads to perform tasks requested of it thereby making itself available to other requests?

B) Presumably the assetManager does not place a wait upon requesting threads while sequentially ensuring the completion of each request.

C) If this is so then there is no advantage to be gained generating threads to call the assetManager because the assetManager will be creating the threads required. Is this right?

A) No, but you can use one assetmanager from multiple threads.

B) Correct

C) No, you have to create the threads

ste3e said:
A) If it is thread safe then does itself spawn threads to perform tasks requested of it thereby making itself available to other requests?

That's not what thread-safety means, you can read about thread-safety here:
http://en.wikipedia.org/wiki/Thread_safety

Thanks for that. Either Re-entrancy or atomic operations then… deduced from the article and Normen’s response.