Hi John, What exactly is the issue that you're having? Is one of the loaders not showing up in the scene? If there is a bug I definitely want to solve it, but why don't you just add the loaders to the scene right after starting the load. The entire reason for the Loader3D is so that you don't have to wait for an event, but can add the loader straight to the scene and know that the loaded contents will be added as they come in.
Cheers /R On May 15, 11:41 pm, John Brookes <[email protected]> wrote: > Just testing some models I've been doing and I'm getting issues with awd1 > and loading two separate files. > > cabLoader = new Loader3D; > cabLoader.load(new URLRequest('../models/DAFCab/DAFCab.awd'), new > AWD1Parser()); > cabLoader.addEventListener(LoaderEvent.RESOURCE_COMPLETE, onLoadComplete); > > trailerLoader = new Loader3D; > trailerLoader.load(new URLRequest('../models/TRAILERC/TRAILERC.awd'), new > AWD1Parser()); > trailerLoader.addEventListener(LoaderEvent.RESOURCE_COMPLETE, > onLoadComplete); > > private function onLoadComplete(e:LoaderEvent):void > { > if (e.url == '../models/DAFCab/DAFCab.awd') > { > view.scene.addChild(cabLoader); > } > if (e.url == '../models/TRAILERC/TRAILERC.awd') > { > trace(trailerLoader.getChildAt(0).getChildAt(0).name) //traces stuff > from cabloader > trace(trailerLoader.getChildAt(0).getChildAt(1).name) > > view.scene.addChild(trailerLoader); > > } > > I know awd had the issues with getting only top container. Don't know if > this is same issue.
