by mark (killzat) » Jan 21, 2002 @ 8:52pm
Ok my changes worked and now you can actually get some half-reasonable speed out of Q2.
Firstly edit the config.cfg file (copy it out of baseq2) and change the following lines to a value of 70 (most are 80 and you don't need that much given Q2's current state):
set fov
set viewsize
Then add the following to the last line:
exec autoexec.cfg
Now make a blank autoexec.cfg file and copy and paste these (they won't work if you just put them in the config.cfg file):
set cl_gun "0"
set cl_particles "0"
set cd_nocd "1"
set cl_footsteps "0"
set intensity "2.75"
set cl_lights "0"
set vid_gamma ".85"
set s_initsound "0"
disconnect
Then upload your edited config and new autoexec file to the baseq2 dir (overwriting old config) and give it a go. Note that the last two lines (s_initsound and disconnect) don't stop the sound system from starting and demo loading, however that may be because they only work in the config.cfg file - will try that next.
If you want to see the gun then you can remove the 'set cl_gun "0"' line, just remember that there's a lot of extra polygons to calculate then, it'll still be faster, but not close to what it is without it.
I hope this helps, I'm still trying to work out why it is Q2 can sometimes run with 17mb free and others it requires 20.28/07mb or more. At least if you have got it started then you'll now actually be able to see some smoother motion, which is quite pleasing =).
Note, I did re-bind all the keys in my own CFG so it works with the buttons on my Maestro, I won't release this since you'll all have your own setups. Just press the keys when in the console to see how they're bound.