View Full Version : 1.27 and Linux
I am at whits ends with this 1.27 release. I am trying and have been trying for days to get 1.27 and RA3 and OSP to work. Does anyone have a clue how to to get these two mods to work or will I be the only 1.17 server left.
Terrynator
01/13/01, 10:08 pm
If you can list the error you get when you try to start the server, that would be helpful.
Have you tried this?
+set vm_game 2 +set vm_ui 2 +set vm_cgame 2
Stick this in your command line.
------------------
Are You a Hook Monkey?
Q3 GMHook has the best physics period.
It's server side with lots of options
www.terryhell.net (http://www.terryhell.net)
I don't get an error but RA3 comes up as TDM or DM. I got it to kind of load the ra3 cfg file but it still doesn't work. I loaded ra3 1.4 which is suppose to work with 1.27. I did try these commands +set vm_game 2 +set vm_ui 2 +set vm_cgame 2 with 0 1 and 2 but it still does not work. I have one server with slackware 7.0 and on the other with red hat 7.0 and they both produce the same results. I have never had a problem with upgrading the servers until now. I did all the suggestions in the ra3 readme file I deleted q3config from /root/.q3a/arena. Intalled the fix from the ra3 fix file and put it into the config. I brought the server up and did a writeconfig q3config.cfg and right now it don't look like my servers are going to go on 1.27g.
anyBODY|OtH
01/14/01, 03:57 am
When running a mod in linux, add the command "+set vm_game 1" to tell the server to use vm code and not library code. I tshould launch the mod then.
------------------
anyBODY|OtH
High Speed FreezeTag Servers 64.23.60.170:27960 and 27961
All right here is the deal I finally got it to work. First problem went unnoticed until I made a fresh install of quake3. When you unzip and untar the 1.27 point release you have to do it in the parent directory of quake3. Hence this is why my command line kept saying quake3 was a directory. My bad not to act upon that message but everyone else makes their upgrades spawn from the quake3 directory not its parent unless they say so in a readme file. The second problem is some Einstein decided to hard code the new release to use its base directory as /usr/local/games/quake3 which is fine if we were just going to update the current game. This was only noticed when I kept all the defaults from rocket arena and somehow it knew the config of the current server. I changed the current servers name in the config and launched the 1.27 server and long and behold it came up with that new name. So now I have to do a flash cut and pray I can get it to work. I deleted my q3config file from /root/.q3a/arena and started the server and it works. But now I have a new problem I can only have one from each mod since the same Einstein who hard coded the base directory decided that the q3config.cfg would be read after ever map cycle. Unfortunately putting quake in a separate directory does not work since it also uses /root/.q3a/arena for q3config.cfg so I tried putting a line writeconfig q3config at the end of my config file. This seems to work but I just did it so I will keep you posted on it. What happens now it loads my config and writes to q3config so when the next server comes up it does the same thing. I am worried what will happen when the both need it at the same time but I will have to deal with that later. Now I am going to attempt OSP and make sure my stats still work with the 1.27. I wonder if ID Software recently hired some Microsoft programmers because I would expect this from Microsoft not ID software. http://gameadmins.com/ubb/frown.gif
Terrynator
01/14/01, 04:56 pm
Try this in your startup script.
+set fs_basepath `/bin/pwd`
or type in the actual directory structure.
Hopefully this will force Q3 to use the working directory.
------------------
Are You a Hook Monkey?
Q3 GMHook has the best physics period.
It's server side with lots of options
www.terryhell.net (http://www.terryhell.net)
Well you didn't mention your on Linux however it appears that way since you mentioned .q3a as a hardcoded dir (yeah, wonderful id). There is a trick you can use using the power of symlinks to get around all this id crap, here it is:
1. Delete the current .q3a directory.
2. Create a symlinked directory called .q3a that points to your quake3 directory
3. For TA (since id made this mod appear as a non-mod - LoL) create an empty missionpack dir under your current missionpack dir.
4. Create a symlink in this new empty missionpack dir to your q3config.cfg file - call it q3config.cfg (of course).
5. Add "+set fs_basepath ./missionpack" to your startup command line, this will prevent double downloads and allow downloads in non-pure mod also.
TA will use the symlinked q3config.cfg entry for your q3config.cfg file (which points to the one in your main missionpack dir - where you'd expect it to be) and create your games.log in this dir also (we create a logs dir under the main missionpack dir - use a symlink to it in the "phantom" missionpack dir then set the g_log variable to "logs/games.log", this keeps everything where you excpect it to be).
When you don't use the q3config.cfg file for banning players (the addip ... command at the game server console), the easiest way around the q3config.cfg problem is to empty it of all content (make it a blank file) and set it's permissions to read only. Quake3 will whine it can't write to it but no harm to game play. Some more info can be found in this thread: http://www.quake3world.com/ubb/Forum5/HTML/002505.html .
Hope that helps.
Pe@ce and Joy to you - i'm out http://gameadmins.com/ubb/cool.gif
------------------
Jesus Is Lord, Zxel
vBulletin® v3.6.9, Copyright ©2000-2010, Jelsoft Enterprises Ltd.