Rob, I have most everything work as desired using the ObjectContainer3D. I'm running into one last issue.
Objects directly a child of view.scene the event.sceneX,Y,Z works perfectly. Objects nested inside my ObjectContainer3D are offset. For an object that is nested inside the ObjectContainer3D I want to move it to the event.sceneX,Y,Z. What translation or action do you recommend is the best practice? Tony On Oct 27, 10:41 am, mogg <[EMAIL PROTECTED]> wrote: > Rob, > > Thank you again. I will go the "ObjectContainer3D" route. That will > provide better rotation anway by using two "ObjectContainer3D"s. > > Tony > > On Oct 27, 8:18 am, "Rob Bateman" <[EMAIL PROTECTED]> wrote: > > > > > Hey Tony > > > screenX Y and Z will have perspective applied to the X and Y coords, to get > > absolute X Y positions in space you need to de-perspective those values - > > you can use the deperspective() method in a ScreenVertex object to do that, > > or lift the code out of there and create your own method > > > if your still having trouble then i would suggest not rotating the scene at > > all - if you need a global rotation value for X, Y and Z, create an > > ObjectContainer3D inside the scene and rotate that instead. That way your > > sceneX Y Z values will be correct for your purposes. > > > atb > > > Rob > > > On Mon, Oct 27, 2008 at 12:29 PM, mogg <[EMAIL PROTECTED]> wrote: > > > > Rob, > > > > Should not "event.sceneX,Y,Z" reflect the "scene.rotationX,Y,Z" ? To > > > say "screen" seems backwards. > > > > Either way, from my testing, neither "event.scene" or "event.screen" > > > reflect "view.scene.rotation". > > > > Tony > > > > On Oct 26, 5:19 pm, "Rob Bateman" <[EMAIL PROTECTED]> wrote: > > > > Hey Mogg > > > > > this is true, however, i would say this is the expected behaviour of > > > > properties with names like sceneX, sceneY and sceneZ. They represent the > > > > position within a scene. If you need to take account of camera position > > > > (including the rotation of the scene), you can always use the sceenX, > > > > screenY and screenZ properties. Rotating a scene is like performing a > > > global > > > > transformation on all the views that use it. > > > > > Rob > > > > > On Sat, Oct 25, 2008 at 10:25 PM, mogg <[EMAIL PROTECTED]> wrote: > > > > > > Dear Away3D team, > > > > > > MouseEvent3D event properties event.sceneX, event.sceneY, and > > > > > event.sceneZ do not take in account for scene rotation translations > > > > > like: > > > > > > view.scene.rotationX > > > > > view.scene.rotationY > > > > > or > > > > > view.scene.rotationZ > > > > > > The MouseEvent3D event always returns assuming that the scene has > > > > > never been rotated. > > > > > > Tony > > > > > -- > > > > Rob Bateman > > > > Flash Development & Consultancy > > > > > [EMAIL PROTECTED] > > > quoted text - > > > > > - Show quoted text - > > > -- > > Rob Bateman > > Flash Development & Consultancy > > > [EMAIL PROTECTED] quoted text - > > > - Show quoted text -- Hide quoted text - > > - Show quoted text -
