I just discovered that the problem is affected by the order that I do an addChild(). For example: addChildren(ring, sphere); // Does not render the ring correctly but addChildren(sphere, ring); // Renders the ring almost correctly (but wraps around the back part of the way)
Rob and esteemed AwayMasters: should I submit this as a bug? Or should rendering be affected by the addChild order? Thanks Ralph On Nov 18, 9:15 am, MarkC <[email protected]> wrote: > I have similar problem, drawing a circle around a DOT3 textured > sphere, just a couple of pixels larger, the 'back' of the ring is not > hidden by the renderer. I also have tried various options, and none > seemed to help. > > Mark > > On Nov 17, 10:45 pm, Ralph B <[email protected]> wrote: > > > I am updating a tutorial on latitude and longitude. It has a sphere > > representing the earth with lines of latitude around it. In Away3D > > 3.4.2 the lines would render correctly over the sphere if their radius > > was 1.03X the sphere radius. But in 3.6, they need to be much further > > away: much further even than the size of the triangles; about an > > entire sphere radius away. And the numbers of segments in the lines > > and sphere do not have any effect. > > > Therefore it seems that the BASIC renderer in 3.6 is doing a worse job > > with Z-sorting than in 3.4.2. In fact it seems like the Z-sorting > > algorithm is comparing the line segment in the ring with the entire > > Sphere primitive, not the triangles on the Sphere surface. > > > Could that be true? > > > I tried using CORRECT_Z_ORDER but it is painfully slow. I see the > > same effect wrapping rings around a Cube, and if I make the ring with > > WireCircle or my own array of LineSegments. > > > Forcing the z-sorting using pushfront, pushback etc. is not an easy > > solution because the latitude rings must be seen to wrap around the > > earth. > > > Any suggestions? Thanks! > >
