No soup for you!!
Well I decided it was time to move from 32bit IBO to a 16bit IBO for my terrain rendering. I been putting this off as it was going to take a bit of work to switch over to it. I was hoping to see a FPS increase, but no.... Reason is I am texture/shader bound which increasing my vertex processing wouldn't help, but the positive is the memory requirement for the terrain will be a lot less. I have one 16bit IBO of 32x32 size vs. whatever the terrain mesh size is e.g. 513x513x4bytes vs. 32x32*2 nice savings! So I am going to keep it this way.
I am determining that I am having slow downs based on my FBO auto mipmapping. I am using 2048x2048 texture sizes which are expensive but man it kills FPS... Not sure what one can do for that... IIRC I don't see any difference in IQ with the mipmapped FBO vs. non mipmapped. So I may turn them off for now.
Once I run through my list of things to check or update, I will add in physics. I am looking at newton for the SDK. What I have seen so far it looks easy enough to use. I hope.
Anyone here use laptops? If so which one are you using? I love my desktop very powerful, but if I go somewhere I would like to keep coding. e.g. Xmas is here and driving a few hundred miles to the relatives sucks, but if I could code while I was there if I stayed the night now its becomes a nice tool to have.