If it is Away3.6 so render sessions are better solutions in term of performance . Correct Z order is CPU intensive .
Sent from my iPhone On May 19, 2011, at 12:08 PM, ringodotnl <[email protected]> wrote: > For Away3.6 I assume ? > > Not sure about render sessions suggestion but that sounds to me like > layer rendering, so it will draw table first then the balls which will > not solve the issues when a ball is near a corner. > Correct me if I am wrong. > > What you could try is: > view.renderer = Renderer.CORRECT_Z_ORDER; > > The downside of this will be the performance. Let me know how it goes. > > Cheers, > Ringo. > > > > > On May 19, 10:19 am, Michael Iv <[email protected]> wrote: >> Use render sessions . Distribute different parts to separate sessions. That >> always works >> >> Sent from my iPhone >> >> On May 19, 2011, at 10:42 AM, Novora <[email protected]> wrote: >> >> >> >> >> >> >> >>> I've been struggling with this problem with a week or so, and I'm >>> really, really irritated... >> >>> Alright, we're making is a pool game, where there will be balls, on a >>> pool table. >> >>> Main problem, the balls have this great tendency to... how to say, >>> appear above or below the rails? At some areas it will be rendered >>> above the rails, at some areas below. >> >>> The 6 main parts are, the 4 rails, the "floor" of the pool table (that >>> green area) along with the legs, and the balls, all in the same >>> container. >> >>> And no matter what I've been trying, ownSession.screenZ or >>> ScreenZOffset, I can never figure out that exact number to put to >>> ensure the balls will always be rendered correctly! >> >>> So... Main questions. >> >>> 1) Is there any better way of doing this? Ensuring that the balls and >>> the rails will be rendered correctly. >> >>> 2) Is there a way to access what the current screenZ of the object is, >>> if its not OwnCanvas? In order to correctly determine the rendering >>> order, you could say... >> >>> 3) How does screenZ and ScreenZOffset work exactly?!? It seems to >>> randomly work here and there... >> >>> 4) Is there any other ways of modifying the depth sorting? >> >>> Please help, I'm pulling my hair out! >> >>> Thanks!
