G.T.A.2 Map Editor

[hwnd]

Whats the proper way to draw objects with vertex arrays?
Is it better to do this before every single object drawn:

    glEnableClientState(GL_VERTEX_ARRAY);
    glEnableClientState(GL_TEXTURE_COORD_ARRAY);
// draw my single object here
// gldrawarrays

   glDisableClientState(GL_VERTEX_ARRAY);
    glDisableClientState(GL_TEXTURE_COORD_ARRAY);

Or just do once this at the beginning of drawing every object (all objects)?

    

glEnableClientState(GL_VERTEX_ARRAY);
    glEnableClientState(GL_TEXTURE_COORD_ARRAY);
for i:=0 to num_objects do begin
// draw all my objects
// gldrawarrays
end;

   glDisableClientState(GL_VERTEX_ARRAY);
    glDisableClientState(GL_TEXTURE_COORD_ARRAY);

Whats the better (in performance) to do this?

Im currently using vertex arrays and not drawing that much of objects but still i get 25% CPU usage.
I dont know what causes this CPU usage.

I will try to pinpoint this of course in the meantime, but maybe the vertex array "order" is important.
Thats why i asked


EDIT: one thing i noticed, sometimes CPU usage is 25% sometimes 0.
In the same place of map.

I dont have any antivirus or something. But i do have enabled debug info and stuff.
I decreased visible range by 1, will see if that reduced the CPU usage.

[User137]

You should change the states just once in that code. All called gl commands slow program down if only a nanosecond, but if constantly repeated they can build up larger lag. But that doesn't seem to be reason for your fps issue, as i assume you already tried both ways?

[hwnd]

I actually tried "once" method. This seems faster i guess because i call these only once. I also dont see the point enabling/disabling them for every block.

But now i discovered that my vertex array version of DrawBlock eats up my RAM. And it gets very slow.
I will restore the DrawBlock from backup and will test if that removes the "memory eating". If yes, then i did something wrong (with sleepy head).

I thought its the map saving procedures that writes invalid map and when loaded damages memory somewhere etc. But the maps are binary equal to original editor maps.
Commented out "DrawBlock" and bug went away. So it is somewhere inside it.