Jump to content

  • Log In with Google      Sign In   
  • Create Account

Banner advertising on our site currently available from just $5!

1. Learn about the promo. 2. Sign up for GDNet+. 3. Set up your advert!


Member Since 28 Mar 2013
Offline Last Active Mar 28 2013 10:55 AM

Posts I've Made

In Topic: Strange Video Memory Increase

28 March 2013 - 10:59 AM

Thanks, I'll check out the GL_EXT_compiled _vertex_array. I get the same problem when I have varied colours

at the vertex and just change the values to say RGB ->RBG. Basically, any change to the colour array causes

the problem.


I appreciate all your comments gentlemen.

In Topic: Strange Video Memory Increase

28 March 2013 - 09:52 AM

Its all in C baby. I am not using anything like GLEW or SDL. Its pretty basic stuff.


Do you think it is a driver issue which is out of my control ??

In Topic: Strange Video Memory Increase

28 March 2013 - 09:39 AM

Yes, sorry I forgot to add in the glDisableClientState commands. These are all deleted after the tris are drawn each time.


I added in VBOs and got the same effect even when deleting the VBO. Even simply using glBegin/End for the rendering (shock horror !!) causes the same effect.


It is kind of driving me crazy..................

In Topic: Strange Video Memory Increase

28 March 2013 - 08:51 AM

OK, the render code is basically as follows:
















So, I am just using arrays, not VBOs. All I do is update the values in the color array that glColorPointer points to before I come into this routine.


The problem is, on a 1GB graphics card, if I am using 600MB and then change the color, it swamps the card and

the system starts badly lagging because it is trying to double the memory usage.

In Topic: Strange Video Memory Increase

28 March 2013 - 07:52 AM



I am using the latest linux driver from Nvidia. The card is pretty old. Its an FX3800, but we see the same issue on an FX4000.

The same routines are used for both types of shading. I'm simply changing the values in the color array. Nothing else.


We get the same "doubling" of memory usage on smaller models too. Its like when the color array is updated, the memory

is not re-allocated on the card properly.