Loader3D.load & AssetLibrary.getInstance bug about away3d-core-fp11 HOT 4 CLOSED

Thanks for reporting and explaining the issue in such detail. This is definitely a bug, and I will fix it straight away!

from away3d-core-fp11.

thanks for your hurry.
and one more thing...

even if I assign library key,
AssetLibrary.getAsset('someID', 'building') seems to refer AssetLibrary.getAsset('someID', null).

from away3d-core-fp11.

I have fixed the original issue.

In your last comment you are using getAsset() incorrectly. The second parameter is a namespace, which is not the same as a library key. Namespaces are used to separate a single library into groups of assets. This lets you load assets with the same name, provided that you load them into separate namespaces. This is not the same as loading them into separate libraries. Most applications will only need a single library.

So, to load something into the "myns" namespace, and then retrieve an asset from this namespace, do this:

AssetLibrary.load(request, null, null, "myns"); // Load
AssetLibrary.getAsset('myasset', 'myns'); // Get

If you want to use a separate library, this is what you would do:

AssetLibrary.getInstance('otherlib').load(request);
AssetLibrary.getInstance('otherlib').getAsset('myasset');

Closing this issue, as the originally reported bug has been fixed. If you have any other questions regarding the AssetLibrary, please post them to the forum on away3d.com.

Thanks!

from away3d-core-fp11.

Thanks for quick fix.

from away3d-core-fp11.