Stephen - 02 August 2011 09:22 PM
From my experience, correct_z_order runs very slow, when objects are stacked on top of each other in the cameras viewing direction, like so
Camera-> Cube Cube Cube Cube
Unless your objects are like that, not sure what’s wrong. Try using a different renderer
Wow, thanks for the suggestion.
It’s amazing how slow the correct_z renderer is!
I tried the INTERSECTING_OBJECTS renderer and it throws a error:
RangeError: Error #1125: The index 8 is out of range 6.
at away3d.core.render::Renderer/createDrawSegment()
at away3d.core.utils::ViewSourceObject/onepointcut()
at away3d.core.filter::QuadrantRiddleFilter/riddleTS()
at away3d.core.filter::QuadrantRiddleFilter/riddle()
at away3d.core.filter::QuadrantRiddleFilter/filter()
at away3d.core.render::QuadrantRenderer/render()
at away3d.core.session::AbstractSession/render()
at away3d.core.session::AbstractSession/render()
at away3d.containers::View3D/render()
at e_Scene1_fla::MainTimeline/away3dloop()
Not sure what intersecting_objects renderer is, but I’m guessing it’s faster then correct_z, and will be better then basic at z orders. Is that correct?