Using the SpriteRenderSession instead of BitmapRenderSession seems to fix this, and there isn't a noticeable difference in performance so I guess I'll just use it instead. I don't think that the issue is directly because of moving the view3D, but rather an issue with the stage. The current app I am working on is a swf that is being loaded into a container swf which we have no control over (or are even given access to in order to test), so I think that it has something to do with findHit referencing the stage of the container and thus offsetting the _hitPointX and _hitPointY values. If anyone knows of a proper fix, please let me know.
Thanks, Eric On Jul 27, 7:23 pm, Eric Decker <[email protected]> wrote: > I ran into a little problem today. Once I create my View3D, I am > moving it to the center of the stage. Everything there is fine, > however, once I add any interactivity, anything past the center (both > horizontally and vertically) doesn't work. So basically, it acts as if > only the top-left quadrant of the view is mouse enabled. Is there some > sort of interactive rectangle or bounds I need to set if I move the > view3D? > > Thanks, > Eric
