   Test program for vbo
  first: this is fillrate limited and using a 3d texture out of laziness isnt helping. point is: in config.cfg you will find the option VBOShort, switching it on will use short instead of float for vertex coords. for some reason, that seems to completely kill speed on my machine when using vbo.so i need testers (card should support fragment_programs).http://festini.device-zero.de/VBODemo.zip (300kb)contains all sources and the binary (windows, linux and others should work once the timer in timer.cpp is replaced, everything else should in theory be independent).^ (or whatever you got in the top left corner next to 1) should open/close the console. try running it with and without VBOShort and if shorts also slow down on nvidia cards (im using a radeon9800, probs showed in cat 4.1 and 4.2) let me know.random keys: cursor for movement, page up/down to scroll in console or move up/down, mouselook, middle button frees cursor, esc quits. rest should be obvious via console. map can be reloaded with loadmap test.map 128  with patchsize a power of 2 between 1 and 128. if automatic word completion is annoying you: autotype (you can still complete words by pressing space).if you dont care about vbo but want to play around with it, let me know how usable the console is and if the typing limitations are helpful or distracting.theres also a large point/square making some noise. pressing ''a'' will rotate a plane and do some collision. if openal works fine for you, you should be getting 3d sound when its flying past you. 
Cool demo man, profiler is slick.On my Radeon 8500/ Athlond XP 2.3Ghz I getVBOShort 0: 300fps at top looking down at entire modelVBOShort 1: 20fps at top looking down at entire modelBig difference there. ;  damn.. still hoping for someone with an nvidia and without the slowdown, so i could at least be sure it's atis fault ,-)oh, and its not really a demo. i called the file demo because it was meant to demonstrate the strange vbo behaviour.just too bad the 3d texture has to go. cant seem to get mipmapping working without using half the depth too for every level (makes me wonder: if i HAVE to half all dimensions, why even bother specifying the new dimensions *confused*). but the 3d lookup seems to take longer than 2 2d lookups and interpolating them anyway.the profiler is still missing some kind of hierarchy, to indent nested ones and optionaly subtracting their value from the "parent". at least it will resize if necessary and fit about 96 halfway readable profiler windows on screen (though i hope nobody will ever need them all)   [edited by - Trienco on February 14, 2004 3:48:44 AM];  Yeah, if I set myself in the same position each time(so I can see the full map), one time I get 180fps, without shorts, and with I get 30fps Radeon 9700pro Catalyst 4.2   [edited by - m_e_my_self on February 14, 2004 7:45:10 AM];  Couldn''t really read the fps because it''s hidden behind the console border.  Is there a way to hide the console?  Didn''t look like there way a major drop in framerate between the two modes.  I''m using a GeForce Fx5900.  The demo didn''t shutdown properly.  Pressing escape closed the main window, but the console window remained.  Closing that left the process running in the background.Enigma ;  console should be the ~ or ^-key (or whats to the left of the number 1 key.. i added that key to the config file).just noticed the config file already had an unused entry for console. changed that and actually use it now ,-).. so if the default isnt working, you can change it here (stick with letters and numbers for now or the ins,home,etc. block for now)shutdown: ouch.. i just noticed i made too many changes to just bail out with exit(0).uploaded a new version, hopefully fixing the shutdown issue too, but it still sounds a bit strange. anyone else had the same problem? if it only happens with nvidia cards debugging it will become a bit difficult (no matter which card you have, its always the wrong one) ;  Shutdown worked fine that time.  You seem to have removed the VBOShort entry from the config file though.  I tried adding it back in and got exactly the same framerate, so either I set it wrongly or there''s no difference between floats and shorts on nvidia hardware.  Framerate was 100fps while looking down on the terrain btw.Enigma ;  i think i need a version control system.. entries are case sensitive, with VBOShort 1 it should work.. but im uploading the corrected version right now. ;  vsync disabled, got on both cases ~525 fps with the full patch in frustum(upside-down view).specs:athlon xp 2000+nvidia geforce 4 ti4200;  hm, i tried it on a fx quadro something (pretty slow but has all the features). no difference and both had about 66fps.so i guess we can officially say the problem only appears with ati and the question is: are non-float types in vbo supposed to screw things up or did ati miss some kind of obvious bug? especially since trying around had another weird result: a simple quad in a vbo was working well with floats and short, but as byte it wouldnt even show up. while the terrain works with all kinds of types, but anything but float will crawl. 