since this game uses the Q3 engine I assumed it would be w/o any problem on my voodoo5

but I'm getting 4 or 5 fps (I can count them  ::)), at any resolution/detail

worse : the game doesn't launch with WickedGL, and I don't know to open the console (tried to put the opengl32.dll in the game's folder : I get the "press C to continue" screen but he kicks me out to windoze)

it runs like a charm on geforce2 MX  :P
unless I use the high textures settings ; then I fall back to 4 fps

so I guess the voodoo5 runs short of video memory and/or the lack of AGP texturing hurts it
(the geforce2MX has "only" 32MB though  :-/) . No means to know if textures are compressed or not, texture compression could solve the problem, but, the games is lacking in options (no way to lowen geometry detail either..)


the developers said the engine is heavily modified but it don't really look that different from medal of honor ;D
http://www.callofduty.org/pages/sp/engine_editing.shtml

also, the games officialy supports only radeon 7200 to 9800 , and geforce 1 to geforce FX

any idea or solution?
thx

Sounds like the CPU. If the Video is lacking T&L, the CPU becomes crucial, and one above 1.4 Ghz is needed.

sorry

I didn't mention I have a duron 700  :D
but UT2003 is more or less playable on that piece of ****


BTW, I thought opengl doesn't care about hardware TnL, whether you run quake1 or this game !?

if you have TnL then it's used in all opengl games else it's software TnL all the way?

oops I didn't even thoughtt about the .cfg ;D

I found a way to get a good framerate..  just looking at the floor :D
shame on the CPU, it sucks at doing all the geometry in software
on this PC mohaa is well playable but some places run choppy ..
the demo starts on a place worse (complexity wise) than everything you can see in mohaa ;D


BTW here is an extract of the .cfg (r_ variables only)
(do you mind if I eat some KB on your server? ;))

if you don't want to waste your time, don't bother reading it

if you do.. congratulations, you're a nerd :o


seta r_ati_fsaa_samples "1"
seta r_ati_pntriangles "0"
seta r_ati_truform_normalmode "QUADRATIC"
seta r_ati_truform_pointmode "CUBIC"
seta r_ati_truform_tess "1"
seta r_colorbits "32"
seta r_customaspect "1"
seta r_customheight "1024"
seta r_customwidth "1600"
seta r_depthbits "0"
seta r_detailtextures "1"
seta r_diffuseSunQuality "2"
seta r_diffuseSunSteps "3"
seta r_dlightQuality "0"
seta r_drawSun "1"
seta r_dynamiclight "0"
seta r_entLightCutoff "0.2"
seta r_ext_texture_filter_anisotropic "0"
seta r_fastsky "0"
seta r_finish "0"
seta r_flares "0"
seta r_fullscreen "1"
seta r_gamma "1.4375"
seta r_ignoreGLErrors "1"
seta r_ignorehwgamma "0"
seta r_inGameVideo "1"
seta r_lastValidRenderer "3Dfx/Voodoo5 (tm) SLI/2 TMUs/32 MB SDRAM/3DNow!/ICD
seta r_lodbias "-200"
seta r_lodscale "4"
seta r_maxEntLights "8"
seta r_mem_agp "8"
seta r_mem_backend "0.5"
seta r_mem_manual "0"
seta r_mem_video "2"
seta r_minEntLightIntensity "0.02"
seta r_mode "3"
seta r_nv_fog_dist "0"
seta r_nv_fogdist_mode "GL_EYE_RADIAL_NV"
seta r_overBrightBits "1"
seta r_picmip "2"
seta r_picmip2 "3"
seta r_portalbevels "0.7"
seta r_primitives "0"
seta r_railCoreWidth "1"
seta r_railSegmentLength "32"
seta r_railWidth "16"
seta r_simpleMipMaps "1"
seta r_stencilbits "8"
seta r_swapDelay "0"
seta r_swapInterval "0"
seta r_texturebits "16"
seta r_texturemode "GL_LINEAR_MIPMAP_NEAREST"
seta r_vbo_interleave "0"
seta r_vbo_manual "0"
seta r_vbo_smc_static_draw "1"
seta r_vbo_stream_draw "1"


this is the demo's cfg with all detail turned down in the demo
I set cg_drawfps to 1 and tweaked it a bit (fastsky 1 , LOD bias 0, detailed textured 0..)
doesn't change much : I'm getting 4 fps in the beginning,  2 fps during the airstrike, and 10 to 20 fps in some places where there's not much on the screen    (up to 30fps, looking at the ground :D).  (FSAA 2X enabled ; no better if I disable it)

I feel like I'm playing doom3's leaked alpha :o
it looks nice anyway

wrote on 03.09.03 at 22:56:09:

oops I didn't even thoughtt about the .cfg ;D I found a way to get a good framerate..  just looking at the floor :D shame on the CPU, it sucks at doing all the geometry in software on this PC mohaa is well playable but some places run choppy .. the demo starts on a place worse (complexity wise) than everything you can see in mohaa ;D BTW here is an extract of the .cfg (r_ variables only) (do you mind if I eat some KB on your server? ;)) if you don't want to waste your time, don't bother reading it if you do.. congratulations, you're a nerd :o seta r_ati_fsaa_samples "1" seta r_ati_pntriangles "0" seta r_ati_truform_normalmode "QUADRATIC" seta r_ati_truform_pointmode "CUBIC" seta r_ati_truform_tess "1" seta r_colorbits "32" seta r_customaspect "1" seta r_customheight "1024" seta r_customwidth "1600" seta r_depthbits "0" seta r_detailtextures "1" seta r_diffuseSunQuality "2" seta r_diffuseSunSteps "3" seta r_dlightQuality "0" seta r_drawSun "1" seta r_dynamiclight "0" seta r_entLightCutoff "0.2" seta r_ext_texture_filter_anisotropic "0" seta r_fastsky "0" seta r_finish "0" seta r_flares "0" seta r_fullscreen "1" seta r_gamma "1.4375" seta r_ignoreGLErrors "1" seta r_ignorehwgamma "0" seta r_inGameVideo "1" seta r_lastValidRenderer "3Dfx/Voodoo5 (tm) SLI/2 TMUs/32 MB SDRAM/3DNow!/ICD seta r_lodbias "-200" seta r_lodscale "4" seta r_maxEntLights "8" seta r_mem_agp "8" seta r_mem_backend "0.5" seta r_mem_manual "0" seta r_mem_video "2" seta r_minEntLightIntensity "0.02" seta r_mode "3" seta r_nv_fog_dist "0" seta r_nv_fogdist_mode "GL_EYE_RADIAL_NV" seta r_overBrightBits "1" seta r_picmip "2" seta r_picmip2 "3" seta r_portalbevels "0.7" seta r_primitives "0" seta r_railCoreWidth "1" seta r_railSegmentLength "32" seta r_railWidth "16" seta r_simpleMipMaps "1" seta r_stencilbits "8" seta r_swapDelay "0" seta r_swapInterval "0" seta r_texturebits "16" seta r_texturemode "GL_LINEAR_MIPMAP_NEAREST" seta r_vbo_interleave "0" seta r_vbo_manual "0" seta r_vbo_smc_static_draw "1" seta r_vbo_stream_draw "1" this is the demo's cfg with all detail turned down in the demo I set cg_drawfps to 1 and tweaked it a bit (fastsky 1 , LOD bias 0, detailed textured 0..) doesn't change much : I'm getting 4 fps in the beginning,  2 fps during the airstrike, and 10 to 20 fps in some places where there's not much on the screen    (up to 30fps, looking at the ground :D).  (FSAA 2X enabled ; no better if I disable it) I feel like I'm playing doom3's leaked alpha :o it looks nice anyway

As it seems, if you haved a Athlon XP 2000, you could run at near 30 fps (especially if you turn res to 800x600 because now the video is slower than the CPU). This brings back memories of a "Star Trek", I believe, game which was OpenGl, Quake 3 engine based:
Low detail 6fps, highest detail 4fps... CPU P2 300 (Savage4 16Mb), or K6-2 450 (4fps more because of 3DNow! and Banshee).

Conclusion: CPU is certainly the main cause in every game, if low or high detail didn't help much the performance...Check and buy an Athlon XP 2200+ if you can.

Well I just tried to run it on my old p3-500 with voodoo 3 2000 and it doesnt seem to work. I realize that all my parts are below min. system requirements. Downloaded amigamerlin and the mesa5.1. No luck. Here is the message.
Client Initialization Complete -----
----- R_Init -----
Initializing OpenGL subsystem
...initializing QGL
...calling LoadLibrary( 'C:\WINDOWS\SYSTEM\opengl32.dll' ): succeeded
...setting mode 3: 640 480 FS
...using colorbits of 32
...calling CDS: ok
...registered window class
...created window@0,0 (640x480)
Initializing OpenGL driver
...getting DC: succeeded
...GLW_ChoosePFD( 32, 24, 8 )
...5 PFDs found
...hardware acceleration found
...PIXELFORMAT 6 selected
...creating GL context: failed
...failed hard
...restoring display settings
...WARNING: could not set the given mode (3)
...shutting down QGL
...unloading OpenGL DLL
----- CL_Shutdown -----
RE_Shutdown( 1 )
-----------------------
Hunk_Clear: reset the hunk ok
Could not load OpenGL.  Make sure that you have the latest drivers for your video card from the manufacturer's web site.

...setting mode 3: 640 480 FS
...using colorbits of 32

Since you have a Voodoo3, you'll need to edit the config to run in 16bit, it otherwise must fail due to the 32bit setting...

Did you try the latest Mesa 0.51c Release from yesterday ?

i keep on getting the open gl notice when i try to play the game.  i downloaded the mezafx 0.51 driver..followed the directions..it still doesn't work.  is there anything i can do??
thanks

Hey wipeout, plz supply some info on your pc specs so we can assist u more.   ;)
eg:  video card, OS etc

I have windows xp..i think an invidia video card..not too sure on that...i thought it was 32 mb...but might be only 16.
thanks

wrote on 31.12.03 at 06:36:20:

I have windows xp..i think an invidia video card..not too sure on that...i thought it was 32 mb...but might be only 16. thanks

then you may have a tnt1/2...you won't need mesafx with this card man, it's just for 3dfx cards! do you have a voodoo1/2 as secondary card? both aren't supported by mesa.. :'(

--adding--
oh well, if you really have a tnt1/2, you might have better chances running call o' duty when installing new detonator drivers.. ;)
if you've 32mb video ram, it could also be a geforce1/2, then it wouldn't be a problem to run the game with actual detonators due to hardware t&l support on geforce series.

Which file do I need to modify? A config for COD? I have the full version. Thinking about biting the bullet and buying a new card for the old computer. Any recommendations for a card that will work with the 2x agp and support dx9.

Oh I forgot yes I have the 5.1c version of mesa. :D

tw56 wrote on 02.01.04 at 06:49:04:

* tw56 users) Copying file named openGL32 in game folder

bet you have a voodoo.. ::)

dunno any card supporting agp2x and dx9..  ???

>>adding<<
found some...
http://www.sparkle.com.tw/frame/list/f_fx.htm
the whole sparkle geforcefx series supports both   ;)

...setting mode 3: 640 480 FS  
...using colorbits of 32

Since you have a Voodoo3, you'll need to edit the config to run in 16bit, it otherwise must fail due to the 32bit setting...

Did you try the latest Mesa 0.51c Release from yesterday ? ""
yes voodoo3 2000

>>editing<<
ah, found the entry you quoted...  ;)

got it running?
there should be a.cfg file somewhere in the gamefolder..edit this line.
seta r_texturebits "32"
--> set to 16

I am trying to get the demo working, I have found the .cfg file in the file .pk3, I have changed to 16bit and mesafx but it doesn´t work now, it seems an incompatibility with this extension:
WGL_ARB_extensions_string

Yes, this is the entire message:

CoD Beta build win-x86 Sep  3 2003
----- FS_Startup -----
Current language: english
Current search path:
C:\Archivos de programa\Call of Duty Dawnville Demo\main\pak0.pk3 (3208 files)
C:\Archivos de programa\Call of Duty Dawnville Demo/main
C:\Archivos de programa\Call of Duty Dawnville Demo\main\localized_english_pak0.pk3 (790 files)
   localized assets pak file for english

File Handles:
----------------------
3998 files in pk3 files
execing default.cfg
couldn't exec language.cfg
couldn't exec config.cfg
execing autoexec.cfg
Unknown command "cg_fov"
========= autoconfigure
configure.csv: using configuration 1200 cpu MHz 512 sys MB 32 vid MB
Hunk_Clear: reset the hunk ok
logfile opened on Sat Jan 03 02:43:52 2004

...detecting CPU, found AMD w/ 3DNow!
Measured CPU speed is 1.64 GHz
System memory is 512 MB (capped at 1 GB)
Video card memory is 16 MB
Streaming SIMD Extensions (SSE) supported

----- Client Initialization -----
----- Initializing Renderer ----
-------------------------------
----- Client Initialization Complete -----
----- R_Init -----
Initializing OpenGL subsystem
...initializing QGL
...calling LoadLibrary( 'C:\WINDOWS\SYSTEM\opengl32.dll' ): succeeded
...setting mode 3: 640 480 FS
...using colorsbits of 16
...calling CDS: ok
...registered window class
...created window@0,0 (640x480)
Initializing OpenGL driver
...getting DC: succeeded
...GLW_ChoosePFD( 16, 16, 0 )
...5 PFDs found
...hardware acceleration found
...PIXELFORMAT 2 selected
...creating GL context: succeeded
...making context current: succeeded
Initializing OpenGL extensions

GL_VENDOR: Brian Paul
GL_RENDERER: Mesa Glide v0.51 Voodoo3 (tm) 1MB FB, 12MB TM, 2 TMU, NOSLI
GL_VERSION: 1.2 Mesa 5.1
GL_EXTENSIONS: GL_ARB_multitexture GL_ARB_point_parameters GL_ARB_texture_compression GL_ARB_texture_env_add GL_ARB_texture_mirrored_repeat GL_ARB_transpose_matrix GL_ARB_window_pos GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_func_separate GL_EXT_clip_volume_hint GL_EXT_compiled_vertex_array GL_EXT_copy_texture GL_EXT_draw_range_elements GL_EXT_packed_pixels GL_EXT_paletted_texture GL_EXT_point_parameters GL_EXT_polygon_offset GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shared_texture_palette GL_EXT_subtexture GL_EXT_texture GL_EXT_texture3D GL_EXT_texture_edge_clamp GL_EXT_texture_env_add GL_EXT_texture_lod_bias GL_EXT_texture_object GL_EXT_vertex_array GL_APPLE_packed_pixels GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_INGR_blend_func_separate GL_MESA_window_pos GL_NV_light_max_exponent GL_NV_texgen_reflection GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod WGL_3DFX_gamma_control WGL_EXT_swap_control WGL_EXT_extensions_string WGL_ARB_extensions_string
----- CL_Shutdown -----
RE_Shutdown( 1 )
Shutting down OpenGL subsystem
...wglMakeCurrent( NULL, NULL ): success
...deleting GL context: success
...releasing DC: success
...destroying window
...resetting display
...shutting down QGL
...unloading OpenGL DLL
-----------------------
Hunk_Clear: reset the hunk ok
Your video card appears to be missing one or more features required to run Call of Duty.

You should install the latest drivers for your video card, being sure to uninstall the old drivers first.  If you already have the latest drivers, you should completely uninstall the drivers and then reinstall them.  This fixes most problems.  If the game still doesn't work, it may be that your video card does not have the minimum features required.  Please check the readme for more information, including a list of supported video cards.

But it seems that that message is from the game and not from the demo which I am using :-/

In 32bit I got the same message in the demo so possibly if I get the game, I´ll get it running ;)

Well I have the full game and I wanted to play so I said goodbye to my old 3dfx card. Bought the Asylum geforce fx 5700 ultra 128mb agp. I was able to get the game working and it is running fine on p3 500mhz. But I have 2 identical computers so I am still interested if anyone has success getting the voodoo3 working with this game. Now my video card is worth more than the computer.

From the read me with full version.
""""""""
3. 16-bit color
 Call of duty does not support 16 bit color depth and does not provide this option in the menu system. Forcing  the game to run in 16-bit color through other mean may result in graphic corruption and other issues.

4. 16 bit textures
 Call of duty is optimized for 32 bit (high resolution) color textures. Since most of the textures and art in the game contain a 32 bit color palette, playing the game using the 16 bit texture quality selection only displays half the color information, thus causing some loss in visual quality.
"""
Sounds like it can run in 16 texture mode

Yes, it can but the demo doesn´t run so I am going to get the game and then I´ll try different settings

hehehe...that's again the color depth problem, isn't it?
since cod only supports 32bit color depth and the voodoo3 only supports 16bit color depth (in 3d apis) you'll get this error message.
we tried to handle that problem but we had no luck, 'cause there aren't even 16bit textures delivered with the game...dunno about the other forums but i don't think anybody had luck to run your combination up to now, sorry  :-[