System Specs for ETQW

[kamikazee]

Indeed, you could enable SMP support by means of the r_smp CVar in the later patches for Q3.

[mortis]

Does anyone know if that cvar works in Wolfy?

[SCDS_reyalP]

Does anyone know if that cvar works in Wolfy?

AFAIK it does not.

[Sauron_EFG]

"From the feedback we got after the 1.32 release, the SMP support as designed in the Quake III Arena technology isn’t so much relevant anymore. It was designed for much lower CPU frequencies and lower AGP throughputs. Modern systems won’t benefit from SMP. Since it didn’t make much sense to remove the SMP binary, we have both now. "

I’d assume the same would be true for RtCW/ET if r_smp did work.

[mortis]

From an old post found here.

Game Clients That Currently Support SMP:
Total Club Manager 2003 - Supported
Quake 3 Arena - Works OKAY
Return to Castle Wolfenstein - Works OKAY
Jedi Knight II - Works OKAY
StarTrek Elite Force - Works OKAY
Alice - Rumored (uses Q3A engine)
IL-2 Sturmovik - Not Very Efficient
Falcon 4 - Not Very Efficient
Starsiege - Works
Mig Alley - Rumored
Battle of Britain - Rumored

Game Clients That Will Support SMP:
Doom ]|[
Quake 4

Dedicated Servers That Support SMP:
Return to Castle Wolfenstein - Supported
Jedi Knight II - Supported
Quake 3 Arena - Supported
Half-Life (with mods) - Supported
Star Fleet Command II - Supported
Orion Pirate - Supported

And from here

The following commands are some of the common ones that expert players may be familiar with from other games - but do NOT work in Wolfenstein: Enemy Territory:

\g_synchronousclients (removed)
\r_stencilbits (crashes game)
\r_texturebits (defaults to 0 after crash, visual artifacts)
\sv_reconnectlimit (not functional)
\r_smp (set to 1 is not supported)
\g_drawammowarning (not functional)
\r_debugsort (crashes PC)
\r_showimages (not supported)

[me666]

The following commands are some of the common ones that expert players may be familiar with from other games - but do NOT work in Wolfenstein: Enemy Territory:

\g_synchronousclients (removed)
\r_stencilbits (crashes game)
\r_texturebits (defaults to 0 after crash, visual artifacts)
\sv_reconnectlimit (not functional)
\r_smp (set to 1 is not supported)
\g_drawammowarning (not functional)
\r_debugsort (crashes PC)
\r_showimages (not supported)

dunno…only r_smp affects how much threads running simultaneous and is supported but write protected. and why should r_stencilbits crash the game? u know for what its stand? try 0 or 8 and u will be fine.

[BR1GAND]

go here:
http://www.systemrequirementslab.com/referrer/srtest
test your rig for Doom 3

Great site… I tested one of my older rigs that had a ATI 9500 and it failed the Q4 Minimum requirements (due to the vid card) but made it into the Recommended Doom 3 requirements. I’d recommend testing at the Q4 setting.

[M8DNanite]

Quake3 had dualcore (SMP) support also but ET dont have it.

RtCW and ET dont support it. r_smp is set to 0 and is read only cvar.
There wouldnt be any benefits from this anyway like Sauron|EFG posted.

But keep your ET in one processor and most windows threads and TS/Vent on another processor if you really want to start to tweak to the rim to get the extra 0.1% boost.

You can set the cpu from task manager (affinity) or automatically with command line tool like this:
http://www.stefan-kuhr.de/procaff/main.php3
http://www.softtreetech.com/24x7/archive/42.htm

Helps if you have AMD X2 and old games that have the rubberbanding issue or dont start at all.
Google for: amd x2 rubber banding