The reason I developed those faster code-paths was my laptop with 945 graphics... ;)
(And the GM45 graphics in the laptop I use now).
Although.. regarding TRIANGLE_ARRAY_SIZE, what particular problem were you seeing which caused you to bump its size?
Did you hit
fprintf (stderr, "Not enough space in vertex buffer\n"); fprintf (stderr, "Requested %i vertices, %i available\n", count, 3 * TRIANGLE_ARRAY_SIZE);
I'd be really curious to see the polygon (or other geometry) which triggered that - it might be a bug somewhere.
Normally the code should just flush the triangles out and start again with a clear buffer.
The reason I developed those faster code-paths was my laptop with 945 graphics... ;)
(And the GM45 graphics in the laptop I use now).
Although.. regarding TRIANGLE_ ARRAY_SIZE, what particular problem were you seeing which caused you to bump its size?
Did you hit
fprintf (stderr, "Not enough space in vertex buffer\n");
count, 3 * TRIANGLE_ ARRAY_SIZE) ;
fprintf (stderr, "Requested %i vertices, %i available\n",
I'd be really curious to see the polygon (or other geometry) which triggered that - it might be a bug somewhere.
Normally the code should just flush the triangles out and start again with a clear buffer.