• Join Us |
  • |
  • Sign in with:

New 3dfx & Matrox Drivers

by Steve Gibson, Nov 30, 1999 9:09pm PST
Related Topics – 3dfx

Couple of quick driver updates to round out the evening, 3dfx has some new Voodoo3 drivers, and Matrox has some new G400 drivers. The 3dfx drivers have another update to their OpenGL ICD (dunno how performance is) and supposedly the Matrox guys did something strange with their GL driver as well.




Comments

47 Threads | 46 Comments















  • Just installed the drivers and there was zero change in Q2 timedemos for me. Q3 runs like shit on this system anyway (I won\'t post my specs for fear of being laughed at!), so I didn\'t even bother doing timedemos with it.

    I typically ignore the nVidia vs. 3dfx BS that is so rampant on here these days, but why release drivers that don\'t address any of the *real* problems that people are reporting, esp. knowing that A) JohnC just criticized your drivers in a public forum and B) the full version of Q3 will be out in a week anyway (prob. meaning you\'ll have to release yet more drivers then)? Why not just wait those extra few days and then lie to us all when you release these drivers?




  • I play at the \"normal\" graphics settings, sometimes \"fast\" when I\'m online. Yes, that is 640x480x16. The V3\'s image quality seems a bit blurry at 800x600 and certainly doesn\'t give enough FPS for online play, but turning the texture detail to highest looks excellent. Framerate takes a massive hit (as low as 17 FPS for me in some cases) IF you\'ve turned gibs on. Do cg_gibs 0 and you\'ll take a much softer hit. I also turned off cg_drawattacker and some other crap I\'m sure I\'ve forgotten. Maybe I\'ll post my \"kickass\" config. heh. =) The weird thing about these drivers from 3dfx, they\'re still dated November 11 or something. I\'ll probably go with nVidia next time around--not because I don\'t like 3dfx, but because I think onboard T&L/high poly counts are neat ideas (15 million polys, anyone?) The T-Buffer seems disappointing.. Who the hell would WANT \"motion-blur\"? I for one, wouldn\'t. And the V5 5000 is PCI only? What the hell? Some sick marketing ploy? Ugh, I\'ve ranted enough.

  • I agree #24
    earlier versions of the test had different demos for timedemo purposes so of course results between the two will be different with the demotest in terms of fps numbers, but there is definitely some big slowdown in certain situations now that didn\'t exist in earlie versions of the 3dfx v3 drivers
    put your nose right up against a wall and fire the ssg
    i drop from 100+ fps to 8-15
    also, when firing either the plasma or the rl at a target while running towards the point of impact causes me to take a 50% drop in framerate when other models are onscreen.
    I have a p3-550, 128mb v3-3000 system
    I dont think its my cpu or ram
    this latest batch of drivers dropped me anoher 4 fps in timedemo demo001.
    the wickedgl helps alleviate some of these problems, especially \'stuttering\' and MAJOR rl trail and blood slowdowns, at the cost of some image quality and portals, but it\'s still present when it counts most: in a large battle. that the card is being held back due to a shit-brain infested driver development team at 3dfx is a real fuckin shame, and regretably I can now say that 3dfx has let me down for the 1st time.
    v1 and v2 were kings in their time, but no matter the fill-rate, a card with shit drivers is worth very, very fucking little to someone who cares about high performance.



  • #20 A friend has a TNT2 and when IÂ’ve played Q3 on his computer I havenÂ’t experienced any slow downs like with the V3. I also remember that the original Q3 compatible drivers ran lightmap without any sort of lagging/slow down effect. This only appeared with the release of later drivers, so I can only conclude itÂ’s an issue with the Voodoo 3 drivers. The 3 shader issue shouldnÂ’t cause the effects it does when you use vertex lighting on the V3 (33fps running demo001 with the default q3config only with vertex lighting on a PIII-550 160MB RAM, V3 3000).

    IÂ’m went for the V3 over the TNT2 because all IÂ’m interested in is fps, but when the V3 canÂ’t supply either looks or fps something is very wrong. It would seem that drivers are more important than fill rate, and in this area nvidea is far better than 3dfx.

    IÂ’ve totally lost confidence in 3dfx and I wonÂ’t be buying another one of their cards for some time to come.

    I just canÂ’t wait for the Prophet 3D DDR to come out. If theyÂ’re not out in America, we probably wonÂ’t see them in the UK until way after Christmas :( IÂ’m tempted to buy the SDR version.





  • #18 The framerate is fairly good, but thereÂ’s a bizarre effect when there are a few rockets on screen or when you get in most fights or when you enter a new room, particularly the lightening gun room. ItÂ’s like a lagging effect (not itÂ’s not my connection, it happens when I create a game on my PC). The mouse movement lags behind your movement, and the general action slows down. ItÂ’s not my processor cos I have a PIII-550 and my brother has an Athlon 600 and we both get the same problem.

    In previous versions of Q3 test the problem could be solved by changing to vertex lighting, but in the demo test the problem is amplified to a shocking level when you change to vertex. Try vertex out and tell me if you get the action lagging behind the mouse effect.

    This effect isnÂ’t just with Q3, I also noticed it in the Messiah demo.

    3dfx canÂ’t produce drivers, so the fill rate on the Voodoo 5 will count for nothing when they supply their crap drivers with it.