Packs you will need from original rtcw game are following:
- pak0.pk3 (main folder) (300mb pack)
- mp_pak0.pk3 (main folder) (60mb pack )
================
Installation:================
Installation procedure is simple but stick to it and read "What not to do" at
bellow this instructions.
Mandatory:
1st: Extract/Install the game to any location you want.
2nd: Copy ONLY pak0.pk3 and mp_pak0.pk inside your extracted wolfX\MAIN folder.
Next steps are optional:
3rd: You can obtain soundpack for (spree, deaths..) on forum as well as a HD
textures pack by registering on forum ->
http://rtcwx.com and grab it in
downloads section along with other stuff (source code, configs..).
4th: If you want to play on streaming servers, you will need to obtain a GUID.
To generate your GUID all you need to do is register on forum and create it
under "Game Account" tab.
5th: Read WHAT NOT TO DO bellow!
LINUX USERS:
You will have to install libsqlclient if you already don't have it due SQL
support that's implemented in engine. Also you'll have to have your drivers
sorted which is something any native linux user will already have sorted..
================
WHAT NOT TO DO!
================
Some common sense warnings...if you follow this guide lines you should be safe..
if not, then repeat whole installation process or risk getting crashes.
- Do not copy your whole rtcw folder with all the packs, maps, configs in wolfX.
- Do not copy your config file inside it unless if it contains key binds only.
- Do not go into any kinda of configs/tweaks because you're risking to break stuff.
- Do not bother with copying maps because wolfX uses HTTP to download maps at
full speed so it's useless and as side result, your map checksum may fail and
can cause infinate download loop bug in certain occasions.
================
Advanced users:
================
Some cvars behavior was altered and as result, dumping config from rtcw may cause
your game to crash. Key binds and mouse related settings are not a problem but
graphical stuff is/may be.
R_mode behaviour was changed, most, well all typical resolutions
are now supported and as result r_mode values where shifted..so don't use rtcw
values from your config and rather do it ingame in system setting and then grab
from console while in game by doing /r_mode to get value or from generated config
values and THEN you can add it in your config when you're sure it's correct one.
Most of cvars still exist and work as expected but some have limited behaviour,
following cvars are removed, or locked between certain values (abusing cvars):
- r_mode values have been shifted due support for new (standard) resolutions
- cl_timenudge is removed
- rate min value has been set to 8000 instead of 3000
- cl_maxpackets is locked between 40 and 100
- centerview key does was removed and whole it's behavior was removed
- m_pitch is locked between .015 and .022 (+/-)
- com_maxFPS is now locked to max 125
- r_intensity is locked between 0 and 2
- r_mapOverBrightBits is locked between 0 and 2
- cg_shadows are locked between 0 and 1
Rest of cvars should work as expected. As you see most of stuff is the same
but some people tend to drop config from rtcw then experience "OPEN_GL subsystem"
crashes due using old r_mode which is set at value their display doesn't support,
as such it's advised to avoid dumping stuff.
New ingame client cvars can be set from OPTIONS/HUD menu & for crosshairs in
OPTIONS/VIEW menu. That's the safest bet to get all the stuff working the way
you want as some settings act the same as in etc OSP but it's cvar name is
different thus your OSP config may not work as you expected.