Hi Rob,Thanks for your help. From what I can tell, this still doesn't work, but I've already written around this in my framework. Instead of attaching accessories to the parent DisplayObject3D instance, I keep track of attached accessories and move them whenever the parent is moved or rotated. This system is probably more flexible, particularly if I ever need to use a different render layer.
For practical purposes this issue is resolved on my end. If I need to do this again or can recreate a test scenario that's not under NDA, I'll let you know. Thanks for the great work!
On Thu, 09 Sep 2010 16:39:17 -0700, Rob Bateman <[email protected]> wrote:
Hey Joshuasome of the internal listeners for re-parenting were updated in the latesttrunk version of the fp10 engine 3.5.2would it be possible for you to check this problem against the latest trunkcode, and see if you are still experiencing the issue? cheers Rob On Sun, Sep 5, 2010 at 1:12 AM, Joshua Granick <[email protected]>wrote:I can try. Here's some more information about it: SETUP:I use the Collada loader to create two objects. Each is named then placedinside of a new ObjectContainer3D. THIS WORKS:I remove one of the objects from it's ObjectContainer3D parent, and add itinside the other object THIS DOESNT WORK:I remove one of the objects from it's ObjectContainer3D parent, and add itto the other object's parent ObjectContainer3D Now that I think of it, I think both objects are given the same name. Itcould be that there are problems with having two objects with the same namein the same ObjectContainer3D, or it could be how many levels deep theobjects were. For example, I noticed that properties like minX and maxX workcorrectly when checking a mesh, but as its embedded within multiple ObjectContainer3D instances, these get inaccurate. Not sure if this is similar? On Sat, 04 Sep 2010 17:04:28 -0700, Rob Bateman <[email protected]> wrote: Hey Joshuathis is odd behavior indeed. The original version you describe is correctfor Away3D, but i am at a loss to explain why this no longer works for you. Would you be able to isolate the problem in a simple test class? Rob On Mon, Aug 30, 2010 at 5:51 AM, Stephen Hopkins <[email protected] >wrote: Hm you sure that object3d's don't move with the container? I remembertesting the container with a offset cube and rotating the the container rotated the cube about the container's origin. I didn't try moving the container though. On Aug 27, 2:38 am, "Joshua Granick" <[email protected]> wrote: > Whelp, I thought I was stuck, but then I realized I have enough framework> around Away3D that I was able to update the attached object myself, soit > all sticks together. > > It would still be nice to know, though, for the future, if there's a way > to have child ObjectContainer3D objects move with their parent, like> Sprites do. I'm guessing this is probably a performance thing, though?> > On Fri, 27 Aug 2010 01:35:51 -0700, Joshua Granick > > > > > > <[email protected]> wrote: > > > Hey guys, > > > Here's the scenario: > > > A) I have an ObjectContainer3D, which holds a mesh or primitive inside > > > B) I have another ObjectContainer3D, which also holds a mesh or > > primitive >> > C) I drag the second mesh to the first one, and I want to add the> > second ObjectContainer3D as a child of the first > > > In the last major release, I was able to do this fine. The second would> > attach itself to the first. If you clicked to drag the first object,> > both would move together. If you clicked the second one to drag, I could > > detach it again and let you move it elsewhere. >> > With Away3D 3.5, this is no longer possible. If I add the second as a > > child of the first, it doesn't act like its a child. It doesn't move> > when the first is moved. This is critically vital for my whole project > > that I'm upgrading. > > > Thank you for your help!! > > -- > Joshua Granick > Owner / Lead Developer > [ eclecticdesignstudio ] > P: (916) 889-7306-- Joshua Granick Owner / Lead Developer [ eclecticdesignstudio ] P: (916) 889-7306
