• Join Us |
  • |
  • Sign in with:

New Voodoo3 Drivers

by Steve Gibson, Sep 09, 1999 1:22pm PDT
Related Topics – 3dfx

Excitement of the day you ask? New Voodoo3 drivers! YEAH! I AM STOKED! Grab them here. Thanks Rachel (yeah, a female reader!) So are they any faster?




Comments

48 Threads | 48 Comments


  • You have nothing to risk by trying out the mini gl. The little app that the program installs won\'t do anything to any of your games until you run it and tell it which games you want to install the mini gl to. Even then it only installs an opengl32.dll in that games directory. All you have to do to get rid of it in the case of Q2 is delete that dll from your main q3test folder and it\'s history.

    #42: Turn off v-sync and it won\'t be so jerky. It still jerks around a lot on me in q3test2 but none at all on q3test1 with v-sync off. The mini gl doesn\'t do it at all.


  • #38: I\'m not a moron. The game woudn\'t run on my system. I tried all the usal things (including *reboot* [gasp]). It seemed to me that they interfered with the mini gl I had on from WickedGL, because: one I installed the drivers that were about 2 weeks older, I still had the same problem. i had to re-install the miniGL from the WickedGL setup utility.

    By the way: Does any one know what the other Mini GL in Wicked GL is (or how well it works?).. There is a \"Normal GL Drivers\" and then there is a button for \"High Resolution GL Drivers\".. Will these increase my FPS at higher res?



  • All I have to say is that the Wicked GL seems to totally blow on a k6-2. Setting absolutely the same, with the MiniGL, I get two FPS lower, and I get some massive slowdowns (not those second long ones, but in fire fights around 8 fps). On the old reference drivers I get 35 in
    1024*768 with the highest detail textures, r_subdivisions set to 9, and r_lodcurveerror 200.

    At every res, its the same. Sigh, I will say this, and prominent people will back me up, the BSP PVS sucks, and should be absolutely turd dead. It takes more time at runtime than some more accurate systems, and its precalc time blows chunks. And then there is the restrictions, and the fact that it is so damn innaccurate it has more overdraw than the Mona Lisa, which was painted over 3 times.

  • PimpStick: Try this. Turn on v-sync from within the game console (r_swapinterval 1) now try running around a bit and then do a timedemo. Something is screwy with the way the ICD uses v-sync. It\'s fine with it off except for the image tearing which won\'t be obvious unless you have a pretty high frame rate. Some people don\'t even notice it. Others can\'t stand it.

    Also try this. Boot up q3test2 and head down the walkway towards the jump ramp that leads to the railgun platform. Stop right in front of that ramp (almost touching it). Now use the left and right stafe keys and just move back and forth. If it doesn\'t get REAL choppy there, consider yourself lucky. It may be a weird problem that only crops up with certain hardware configs but it seems pretty common. It\'s completely gone with the Metabyte mini gl (and I hear with the Creative mini gl too).

    I haven\'t heard but one or two people having desktop errors. Don\'t know what the hell that\'s all about.



  • The problem with using tweaks in this case is that it somewhat invalidates your benchmarks (as far as anyone else is concerned). It\'s better to stay somewhat at default settings when comparing benchmarks so everybody is on a level field so to speak. You would have to post ALL of your tweaks exactly then we would all have to use ALL of your tweaks exactly to be able to make a fair comparison. :-)

    With tweaks I can get up into the 80\'s on my 450. I get 67 with my normal gameplay config (i have several configs for how much of a speed/looks ratio i want at any given time).










  • The green tint has been improved a bit in the latest mini gl. Still there though. The texture flicking has been all but eliminated. The only time i see any now is when rocket/pad jumping way up past the quad platform in q3test2 now. the pentagram texture will flicker slightly.

    My monitors refresh rate for that resolution is 75Hz. A bit low yes but not low enough to where the timedemo should slow to a crawl like it does in certain places when v-sync is anabled. At least it doesn\'t seem like it should to me. That should just limit my max frame rate to 75fps when v-sync is on. It seems like the 3dfx drivers just aren\'t working correctly with v-sync somehow. The 3dfx mini gl doesn\'t have a problem like that in Q2 and the metabyte mini gl doesn\'t do it in Q3 so it seems like it\'s a problem with their open gl ICD.

    I still think 3dfx should hire some of the poeple working at Metabyte. :-)


  • Just tried it again with v-sync off and now it\'s up to 53fps with the same settings i had before. Porblem is that now there\'s a lot of image tearing.

    Does it seem very odd to anyone else that simply enabling v-sync would cause such massive slow downs? During the timedemo, with v-sync on there are places where it just crawls. You could probably count the frames. With v-sync off it stays much more consistant (however I still feel the mini gl is more consistant).

    The mini gl lets you enable v-sync with only a very minimal loss in frame rate and the image tearing is gone. And even though it\'s a matter of taste, i think the mini gl looks much better (the latest version that is) than the 3dfx drivers. 3dfx gives you a little less banding in the sky but the color is much richer with the mini gl (set the games color depth to 32 bit and the textures to 16 bit if you use the mini gl, big difference).

    If you don\'t mind the image tearing, the new drivers will work fine for you. It drives me crazy though.

    Turn v-sync on and off from the console with this command.

    r_swapinterval 0 (default is 0 which is off)
    r_swapinterval 1 (turns it on and gets rid of the image tearing thats most apparent in the muzzle flash of the machinegun and when going up stairs)




  • Crap. Just like every other driver 3dfx has put out for the V3. If it weren\'t for Metabyte I would have ditched this card by now.

    V3 3000
    Celery 450
    128 PC-100
    Abit BH6
    Quake 3
    960x720
    Mostly default settings
    v-sync on

    Last V3 drivers: 37.2
    New V3 drivers: 37.1
    Metabye Wicked 3D mini gl: 51.2

    Even more important than the dramatic timedemo score is the stability of the mini gl. With the 3dfx drivers the frame rate jumps all over the place including some seriously nasty slow downs. It\'s so bad that it throws of your playing. Like Quaking drunk (seriously, it\'s very similar).

    With Metabytes mini gl the frame rate is VERY consistant. Not any serious frame rate drops to speak of. Silky smooth gameplay.

    If any of you are still trying to play Quake on a V3 (probably V2 or banshees too), do yourself a favor and grab the mini gl. Most of the bugs are worked out of it now except the screen shot problem but thats a small sacrifice for improvement in gameplay.

    - Death2Uall -

    P.S. I\'m sure I could tweak the 3dfx drivers to be faster in the timedemos but theres no way around the jerky ass gameplay that I\'ve found. I spent enough time trying to fix that with their last batch of drivers and doing it again isn\'t worth the effort. I may mess with it later but I\'ll have to be pretty bored to do it.