It's not actually that odd when you know how the loader3d works internally.
The thing is that loader3d uses the asset library internally by default. This means that even if you start two loading operations on different loaders, they internally use the same library instance for the load and the way its currently designed will get the same events. You can avoid the problem by configuring loader3d to use the asset loader instead of the library, by setting the first constructor parameter to false. I will fix this tomorrow, so that even if the loader3d uses the asset library internally for loading, a loader3d instance will only care about those loads that were initiated through it's own interface. After then your code will work as expected exactly the way it looks now. Cheers /R On May 16, 12:23 am, John Brookes <[email protected]> wrote: > ok thanks. > > was ging to post this so shall :) > > ... > More bizarre > > cabLoader = new Loader3D; > cabLoader.load(new URLRequest('../models/DAFCab/DAFCab.awd'), new > AWD1Parser()); > cabLoader.addEventListener(LoaderEvent.RESOURCE_COMPLETE, > onLoadCabComplete); > > trailerLoader = new Loader3D; > trailerLoader.load(new URLRequest('../models/TRAILERC/TRAILERC.awd'), new > AWD1Parser()); > trailerLoader.addEventListener(LoaderEvent.RESOURCE_COMPLETE, > onLoadTrailerComplete); > > private function onLoadCabComplete(e:LoaderEvent):void > { > trace("onLoadCabComplete "+ e.url) > //traces onLoadCabComplete ../models/TRAILERC/TRAILERC.awd <--wrong > ... > > } > > private function onLoadTrailerComplete(e:LoaderEvent):void > { > trace("onLoadTrailerComplete "+e.url) > //traces onLoadCabComplete ../models/TRAILERC/TRAILERC.awd > ... > > } > > erm how? > Traces same url.
