Quote:Original post by Headkaze
Another optimization I've been considering is changing from GL_TRIANGLES to GL_TRIANGLES_STRIP. Is it relatively easy to convert the data over to this format?

Art tools can do it, but it is probably not recommended.

First off, you would be much better off with indexed triangles rather than drawing individual triangles. That way you only transmit the points once and reuse them. If you are transmitting raw triangles every frame you are probably sending 3X the necessary data.

I'm not sure about the iPhone's various GPU editions, but most modern cards perform better with "triangle soup" rather than triangle strips. The parallel processing in the card means that each sub-processor can be more efficient if you let it do its own optimization rather than telling it a specific order to draw the strips.

Quote:I'm not sure moving it will help either, that part of the forum seems quite dead.

It is very active but low volume.

Many people watch it. Few professionals post questions to it because of the console maker's NDA terms They will post to the official private groups.

When questions are asked, however, there are relatively more industry professionals lurking on the forum. The answers are generally more useful and targeted directly to the hardware's need.

I know you've "solved it" but you could optimise this simple loop by removing all the aliasing. I would code the loop something like this:

while(vertexCount--){    fp32 fCx = pCurrent->x;    fp32 fCy = pCurrent->y;    fp32 fCz = pCurrent->z;    fp32 fNx = pNext->x;    fp32 fNy = pNext->y;    fp32 fNz = pNext->z;    pDest->x = fCx + (fNx - fCx) * fAlpha;    pDest->y = fCy + (fNy - fCy) * fAlpha;    pDest->z = fCz + (fNz - fCz) * fAlpha;    ++pCurrent;    ++pNext;    ++pDest;}

I hope this helps?