Archived

This topic is now archived and is closed to further replies.

performance of glVertexPointer

This topic is 5655 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi there, i''m working on a tile based outdoor game. Because not all tiles are loaded at once in memory, every tile has it own vertex, normal vector and texture coordinate list. So is it advisable to have vertex arrays and call glxxxPointer for every tile to be drawn? Or is it faster to call glVertex3fv in an inner loop? Ok, i could test it for myself, but if anyone has already some experience with it would be nice to hear what you think. eloso

Share this post


Link to post
Share on other sites

Probably the latter is quicker (immediate mode), try it and see. I think that you should do a `collection'' pass into a single buffer so you can render them all at once. Having said that, if each tile is different, you''ll have to change state inbetween - so maybe immediate mode is best. Whatever!

Share this post


Link to post
Share on other sites
I''ve never had a situation where immediate mode is faster... It all depends really, I have managed to make it faster, but only by making the VA''s do far more work. VA''s are generally the way to go...

Death of one is a tragedy, death of a million is just a statistic.

Share this post


Link to post
Share on other sites