Jump to content
Compatible Support Forums
Sign in to follow this  
Turbo Grunkamoj

Does the win2k-drivers from 3dfx suck or is it just win2k?

Recommended Posts

Hello.

Im running Windows 2000(build 2195)

I have the latest drivers from 3dfx, released yesterday(v3-w2k-retail-1.00.00.exe)

My System:

P2-400Mhz

128Mb ram

V3-3000agp

17" MAG monitor

yada yada...

The problem is this: When running Quake 3 in 800x600, in win98 before I had about 90fps when using the following:

timedemo 1

demo demo001

Now when I test the same thing I get about 63fps, is this really the performance loss one can expect in win2k?

I have tried the following:

changing color-depth, texture-quality etc, all the things you can change from within the game with a +/- 2-3fps. I put the following line in my config in Q3:

set displayrefresh "85", but no change.

Is there anyone out there who can verify such a performance loss? or who has any help on the matter?

Share this post


Link to post

Personally I don't think you were getting 90 fps what so ever. I have a faster cpu than you and a voodoo3 3000 and I have NEVER seeing it higher than 60-70 range on the lowest res and settings. At 1024 i hit around 40fps. The openGL icd is MUCH better than the one in 98. Not to mention the memory management, disk access and overall better performance of win2k, I would say theres something up with your PC. Did you do a fresh install or an upgrade? How much of your ram is in use? Did you turn off all non essential services? Did you close other apps while doing this or leave them open? Mine tested at 45 fps in 8x6 on timedemo 1 and most settings at default. I have 2 celeron 366's @ 528 and 384mb of ram. My v3 is clocked at 166 as well.

 

------------------

§E£DZÅR

http://www.win2knews.com

Share this post


Link to post

He's right. The Voodoo 3 is slower performing in Windows 2000. I have an AMD Athlon 800 and a dual boot system, and the times in Windows 98 are about 30% faster than the times in Windows 2000. The drivers just aren't there yet.

Share this post


Link to post

You (Seldzar) dont personally think I have about 90 fps on a v3-3000?? Well who can argue with that? I must be wrong or lying...

Well of course my Q3 is tweaked alot, but I dont use singel-colored textures etc..and I havent touched anything in my pak-files either. Still I had about 90 (89.7 to be exact) in 800x600 when running, timedemo 1, demo demo001, in windows 98, thats it and thats that.

Thx Dobbs, for letting me know Im not the only one who got such a performance decrease.

/Sorry if I sounded cranky early in this message, a neighbor of mine is really bugging me....

Share this post


Link to post

Its the drivers. Tests have been performed. The voodoo3 drivers for win2k are slow. Maybe its opengl specific dunno but I defenitely the drivers. I dont have the exact thread and I dont feel like looking it up but there was tests performed on this and on a box with a voodoo3 & win98 was about 10-14 fps faster than the same box with win2k. They replaced it with a tnt or some card I forgot which and it beat out win98. So that means its the drivers. If anyone really wants Ill try and dig up the thread.

Share this post


Link to post

I've found that my voodoo3 is working fine in games. In quake3 i don't believe its running any slower than when it was in win98. i can't be certain becuase i didn't do a benchmark in quake3 when i had win98 but, from just looking at the game its seems to running nice a sliky smooth.

and anyway, if your still getting like 60fps then whats the big deal?? so maybe the drivers aren't quite as fine tuned as the win98 drivers, YET!! or maybe its something else in your system causing your v3 to go abit slower.

Share this post


Link to post

Okay now Im going to say something that is really contradictory:

Im a gamer and I want to use Win2k smile.

If you play Q3, singelplayer and just 1on1 its quite okay with ~60fps, BUT if you play on a server with 8 ppl, and everybody is firing: misiles, grenades, railing, shafting all around you, then I can guarantee that those 20-30 fps makes a difference.

Just my 2-cents to why every fps counts.

I guess we all have to wait until 3dfx gets their head out and releases new drivers.

Share this post


Link to post

Hey, I didn't want it to sound accusing or anything I just didn't think that any voodoo card could push q3 that high, I mean it's q3, 3d card fill rate killer.

 

Care to share you tweaks?

 

------------------

§E£DZÅR

http://www.win2knews.com

Share this post


Link to post

Post them here so we can all see. Please.

Ed

Share this post


Link to post

Okay then here it goes, I have removed every line that isnt really of interest, such as key-bindings etc. Now dont ask me what everything specifically does, I have had a lot of help on this and doesnt acctually have a definite clue myself smile and I have used cut'n paste very much, yada yada smile Here it is:

 

seta cg_drawIcons "1"

seta s_compression "1"

seta com_hunkMegs "48"

seta s_occ_eq "0.75"

seta s_occfactor "0.5"

seta s_bloat "2.0"

seta s_numpolys "400"

seta s_polyreflectsize "10000000"

seta s_polysize "10000000"

seta s_polykeep "1000000000"

seta s_refdelay "2.0"

seta s_refgain "0.45"

seta s_leafnum "0"

seta s_max_distance "1000.0"

seta s_min_distance "3.0"

seta s_distance "100.0"

seta s_doppler "1.0"

seta s_rolloff "0"

seta s_mixPreStep "0.05"

seta s_mixahead "0.1"

seta s_loadas8bit "0"

seta s_khz "22"

seta s_separation "0.5"

seta r_vertexlighting "1"

seta r_lastValidRenderer "3Dfx/Voodoo3 /2 TMUs/16 MB SDRAM/stand-alone (Jan 31 2000)"

seta r_primitives "0"

seta r_railSegmentLength "32"

seta r_railCoreWidth "6"

seta r_railWidth "16"

seta r_facePlaneCull "1"

seta r_gamma "0.9"

seta r_swapInterval "0"

seta r_textureMode "GL_LINEAR_MIPMAP_NEAREST"

seta r_finish "0"

seta r_dlightBacks "1"

seta r_dynamiclight "0"

seta r_drawSun "0"

seta r_fastsky "1"

seta r_ignoreGLErrors "1"

seta r_flares "0"

seta r_lodbias "1"

seta r_lodCurveError "200"

seta r_ignoreFastPath "1"

seta r_smp "0"

seta r_subdivisions "20"

seta r_vertexLight "1"

seta r_simpleMipMaps "1"

seta r_customaspect "1"

seta r_customheight "1024"

seta r_customwidth "1600"

seta r_fullscreen "1"

seta r_mode "4"

seta r_ignorehwgamma "1"

seta r_overBrightBits "1"

seta r_depthbits "24"

seta r_stencilbits "0"

seta r_stereo "0"

seta r_colorbits "32"

seta r_texturebits "32"

seta r_detailtextures "0"

seta r_preloadTextures "0"

seta r_roundImagesDown "0"

seta r_picmip "1"

seta r_ext_texture_env_add "0"

seta r_ext_compiled_vertex_array "1"

seta r_ext_multitexture "1"

seta r_ext_gamma_control "1"

seta r_ext_compress_textures "1"

seta r_allowExtensions "1"

seta r_glDriver "opengl32"

seta r_intensity "1.7"

seta cm_playerCurveClip "1"

seta snaps "20"

seta rate "9000"

seta com_blood "0"

seta com_maxfps "120"

seta cg_deferPlayers "1"

seta cg_forceModel "1"

seta cg_railTrailTime "400"

seta cg_lagometer "1"

seta cg_simpleItems "1"

seta cg_crosshairY "1"

seta cg_crosshairX "0"

seta cg_crosshairHealth "0"

seta cg_crosshairSize "24"

seta cg_drawRewards "0"

seta cg_drawAttacker "0"

seta cg_drawAmmoWarning "0"

seta cg_draw3dIcons "0"

seta cg_drawSnapshot "0"

seta cg_drawFPS "0"

seta cg_drawTimer "1"

seta cg_drawStatus "1"

seta cg_draw2D "1"

seta cg_gibs "0"

seta cg_stereoSeparation "0.4"

seta cg_fov "105"

seta cg_zoomfov "45"

seta cg_drawGun "0"

seta cg_marks "0"

seta cg_drawCrosshairNames "1"

seta cg_drawCrosshair "7"

seta cg_brassTime "0"

seta cg_shadows "0"

seta cg_viewsize "100"

seta cg_predictItems "1"

seta cl_maxpackets "100"

Share this post


Link to post

Turbo? Lemme get this straight. Below is yer posted tweaks..

 

Okay then here it goes, I have removed every line that isnt really of interest, such as key-bindings etc. Now dont ask me what everything specifically does, I have had a lot of help on this and doesnt acctually have a definite clue myself and I have used cut'n paste very much, yada yada Here it is:

seta cg_drawIcons "1"

seta s_compression "1"

seta com_hunkMegs "48"

seta s_occ_eq "0.75"

seta s_occfactor "0.5"

seta s_bloat "2.0"

seta s_numpolys "400"

seta s_polyreflectsize "10000000"

seta s_polysize "10000000"

seta s_polykeep "1000000000"

seta s_refdelay "2.0"

seta s_refgain "0.45"

seta s_leafnum "0"

seta s_max_distance "1000.0"

seta s_min_distance "3.0"

seta s_distance "100.0"

seta s_doppler "1.0"

seta s_rolloff "0"

seta s_mixPreStep "0.05"

seta s_mixahead "0.1"

seta s_loadas8bit "0"

seta s_khz "22"

seta s_separation "0.5"

seta r_vertexlighting "1"

seta r_lastValidRenderer "3Dfx/Voodoo3 /2 TMUs/16 MB SDRAM/stand-alone (Jan 31 2000)"

seta r_primitives "0"

seta r_railSegmentLength "32"

seta r_railCoreWidth "6"

seta r_railWidth "16"

seta r_facePlaneCull "1"

seta r_gamma "0.9"

seta r_swapInterval "0"

seta r_textureMode "GL_LINEAR_MIPMAP_NEAREST"

seta r_finish "0"

seta r_dlightBacks "1"

seta r_dynamiclight "0"

seta r_drawSun "0"

seta r_fastsky "1"

seta r_ignoreGLErrors "1"

seta r_flares "0"

seta r_lodbias "1"

seta r_lodCurveError "200"

seta r_ignoreFastPath "1"

seta r_smp "0"

seta r_subdivisions "20"

seta r_vertexLight "1"

seta r_simpleMipMaps "1"

seta r_customaspect "1"

seta r_customheight "1024"

seta r_customwidth "1600"

seta r_fullscreen "1"

seta r_mode "4"

seta r_ignorehwgamma "1"

seta r_overBrightBits "1"

seta r_depthbits "24"

seta r_stencilbits "0"

seta r_stereo "0"

seta r_colorbits "32"

seta r_texturebits "32"

seta r_detailtextures "0"

seta r_preloadTextures "0"

seta r_roundImagesDown "0"

seta r_picmip "1"

seta r_ext_texture_env_add "0"

seta r_ext_compiled_vertex_array "1"

seta r_ext_multitexture "1"

seta r_ext_gamma_control "1"

seta r_ext_compress_textures "1"

seta r_allowExtensions "1"

seta r_glDriver "opengl32"

seta r_intensity "1.7"

seta cm_playerCurveClip "1"

seta snaps "20"

seta rate "9000"

seta com_blood "0"

seta com_maxfps "120"

seta cg_deferPlayers "1"

seta cg_forceModel "1"

seta cg_railTrailTime "400"

seta cg_lagometer "1"

seta cg_simpleItems "1"

seta cg_crosshairY "1"

seta cg_crosshairX "0"

seta cg_crosshairHealth "0"

seta cg_crosshairSize "24"

seta cg_drawRewards "0"

seta cg_drawAttacker "0"

seta cg_drawAmmoWarning "0"

seta cg_draw3dIcons "0"

seta cg_drawSnapshot "0"

seta cg_drawFPS "0"

seta cg_drawTimer "1"

seta cg_drawStatus "1"

seta cg_draw2D "1"

seta cg_gibs "0"

seta cg_stereoSeparation "0.4"

seta cg_fov "105"

seta cg_zoomfov "45"

seta cg_drawGun "0"

seta cg_marks "0"

seta cg_drawCrosshairNames "1"

seta cg_drawCrosshair "7"

seta cg_brassTime "0"

seta cg_shadows "0"

seta cg_viewsize "100"

seta cg_predictItems "1"

seta cl_maxpackets "100"

 

You cant POSSIBLY be using a voodoo3.. If you are, wtf? depthbits to 24 and texturebits to 32? v3 can only do 16bit..

Share this post


Link to post

Better get those drivers right now smile hehe 3dfx lost 31 or so million last quarter i think. If the v4 and v5 flop (very possible) 3dfx might not be around that long.

 

------------------

***TRUST YOUR TECHNOLUST***

Share this post


Link to post

As a reply for "the Nagual":

Yes Im using voodoo3, and the reason I have Q3 set to 32-bit, is that it will then use its "special-hysch-hysch" 22-bit mumbo yumbo :), and there is NO significant speed decrease. Thats why.

Share this post


Link to post

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×