well, say one of the children is an ObjectContainer3D, if you do not addChild()
it, you also do not addChild its children
children are Object3D, this means they can be of type Mesh or
ObjectContainer3D. All depends how you have structured the original file.
if they all are of type Mesh and you keep missing the last one, somehow, I
would think your loop is missing one iteration.
also keep in mind that being addChilded doesn't mean being in viewport.
you can ask your camera to look at the missing one, trace its position...
Fabrice
On Apr 6, 2010, at 5:02 AM, Vic wrote:
> I've been struggling with this for 12 hours and at wits end.
> I just want to know if this rings any bells - maybe this is a bug:
>
> I load my 3ds and while it loads I get 6 models, one
> of them is - (this is what the trace says):
>
> + Build Mesh : MonStand01
>
> Then I go through the loop (derived from frustum room demo):
>
> for each (var child:Object3D in model.children) { ...
>
> and it goes through the objects to place them, etc..
>
> MonStand01, which clearly appears on the stage in the swf
> DOES NOT get found in this loop!
>
> Then, as an experiment, I removed that model from my 3ds scene
> and run the swf and, holy smoke, now there's another model missing,
> even though the + Build Mesh : XXX traces and the model appears
> on the stage. If I remove another 3ds object I loose another object
> that's supposed to be there
>
> It's as if this loop is yielding model.children one less object than
> is on the list of objects that the loader recognizes.
>
> Can anyone tell me what's going on here?
>
> Thanks (exhausted) -
> Vic
>
>
> --
> To unsubscribe, reply using "remove me" as the subject.
