hmm of course i`m not sure ;-) but when i leave the objects untextured i see the triangles right? and when i enable the awayprojectstats there are the elements shown and when i change the view and the triangles are multiplied the elements in the stats rise up too. so maybe it is temporary but in the moment when they are shown it falls back to the performance or not? when i try nearfieldclipping instead its the same. Why does away change the trianglecount? is this neccassary?
On 17 Aug., 15:10, Michael Iv <[email protected]> wrote: > Are you sure about it ? May be you mean frustum clipping ? But that > subdivision is temporary , just to remove screen edge artifacts . > > Sent from my iPhone > > On Aug 17, 2010, at 3:52 PM, le_unam <[email protected]> wrote: > > > Hey guys, when i was analyzing the clipping/rendering of my scene then > > i saw that often more triangulates are shown as they are created. So > > what i want to say is that i create an easy plane in cinema4d for > > example with only two triangles. When i import this plane into away3d > > first i see this two triangles, but when i move my camera and the view > > changes, away makes the trianglescount riseup. Is there a chance to > > stop this procedure? Is it a clipping-thing? Or a rendering-thing? i`m > > searching for things to make my swf speed up. So any helpful things > > about the speedness?
