As noted in another post, showing a scene inside a component using scalex/scaley at another value than 1.0 do indeed mess up the clippingrectangle logic currently.
Would be great if this was fixed - I don't mind syncing vs the svn to get it asap. ;) On Aug 12, 4:49 am, Ralph B <[email protected]> wrote: > Rob - here is another challenge for you... > > We ran into an issue that seems to have been introduced in a recent > trunk build. If you add an Away3D view to a child movieclip, use > scaleX and scaleY on that movieclip, and then drag the corners of the > window when the SWF is playing, the Away3D scene seems to compute its > rectangle clipping incorrectly. > > For us, this shows up as large chunks of the Away3D object > disappearing when we load a lesson SWF into course player SWF, so it > is a pretty severe problem! > > We were able to work around it by replacing part of Clipping.as in the > trunk with the equivalent fragment of code from tag 2.3.3. I have > created Issue 52 and included there an example .fla and .swf, as well > as the culprit code from Clipping.as. > > Thanks in advance for looking into this! > > Ralph
