Any way to save all variables?
Any way to save all variables?
Is there anyway to save all the commands when you do writeconfig cfgname.cfg ?
I don't think it saves all of them, for example I changed pb_sleep to 500 and I cannot find pb_sleep in the cfg I did writeconfig to and it's being reset every time I start so I have to put it in my autoexec.cfg. There must be a way to make it save all the commands in a cfg file.
I have another question I have a pretty bad connection, due to bad wiring in this old condo.
Download at about 100 kb/s
Upload at about 12kb/s
I experience quite a bit of lag during gameplay in Q3A, however games like CS:S don't lag at all and I have a ping of 60-90. I also notice that lower com_maxfps seems to give me less lag. I was wondering what would be the best values for these commands?
set cl_maxpackets
set cl_packetdup
set rate
set snaps
set com_maxfps
Any other connection commands? Thanks.
I have another question I have a pretty bad connection, due to bad wiring in this old condo.
Download at about 100 kb/s
Upload at about 12kb/s
I experience quite a bit of lag during gameplay in Q3A, however games like CS:S don't lag at all and I have a ping of 60-90. I also notice that lower com_maxfps seems to give me less lag. I was wondering what would be the best values for these commands?
set cl_maxpackets
set cl_packetdup
set rate
set snaps
set com_maxfps
Any other connection commands? Thanks.
Your connection is, at a guess, 1Meg down 128k up
Try:
\rate 12000
\snaps 40
\cl_maxpackets 60
\cl_packetdup 1
\com_maxfps 125
I think PB commands are an exception to the config rule, as punkbuster's integration with Q3 is pretty, uh, hacked, if you like. There may be a config file in the \pb\ folder where you can manually add the command (with notepad).
Try:
\rate 12000
\snaps 40
\cl_maxpackets 60
\cl_packetdup 1
\com_maxfps 125
I think PB commands are an exception to the config rule, as punkbuster's integration with Q3 is pretty, uh, hacked, if you like. There may be a config file in the \pb\ folder where you can manually add the command (with notepad).
"Maybe you have some bird ideas. Maybe that’s the best you can do."
― Terry A. Davis
― Terry A. Davis
Thanks I will give that a try. 1 more question, for some reason when I connect to 69.41.173.132:27960 , as soon as I enter the game I see about 2 seconds of the gameplay then I see connection interupted and punkbuster throws me back to the main menu with this message.
"Server disconnected - you have been kicked via punkbuster (for 0 minutes) ... PB GUID AUTH: UNKN"
I am able to connect to other servers with pb, but not this one. Any ideas?
"Server disconnected - you have been kicked via punkbuster (for 0 minutes) ... PB GUID AUTH: UNKN"
I am able to connect to other servers with pb, but not this one. Any ideas?
It might be a problem with the server if noone else can stay on it, either.
If other people are on it and you're the only one who can't connect, that's trickier. The server could be using some non-standard port to communicate PB info, I really dont know.
If other people are on it and you're the only one who can't connect, that's trickier. The server could be using some non-standard port to communicate PB info, I really dont know.
"Maybe you have some bird ideas. Maybe that’s the best you can do."
― Terry A. Davis
― Terry A. Davis
For saving pb commands, make a pbcl.cfg in your pb dir and put this in it:
;Auto Generated by PunkBuster Client
pb_msgprefix "^2PunkBusted Client" //[PB Message Prefix (default=5)]
pb_sleep 500 //[# of Milliseconds (default=250)]
pb_security 0 //[0=No, 1=Yes (default=0)]
pb_system 0 //[0=No, 1=Yes (default=0)]
pb_logtofile 0 //[0=No, 1=Yes (default=0)]
pb_sslog 0 //[0=No, 1=Yes (default=1)]
pb_sssave 0 //[0=No, 1=Yes (default=0)]
pb_ssoptions 640 480 50 50 1 //Set local PB screenshot options
pb_load pbcllog.cfg //load remote logging settings
Edit to your liking, and after saving make the file read-only. This will prevent pb from dicking with these settings (it resets pb_security unless it's read-only for instance).
EDIT: Try pb_logtofile 1 After you get kicked, go to the pb dir and see if there is a new txt file which might contain the error message.
Also make a pbsys.cfg in the pb dir and put this:
pb_system 0
Match it to whatever pb_system preference you have in the previous file. Make it read-only also.
Getting dropped from the game, you might be getting an 'invalid pk3 files referenced' error. This is osp right? Well anyway you won't know if that's the error you get, other players should be able to notice what the error is when they are in-game.
Check your osp and baseq3 dir for any odd pk3s in there (the type that are several kbs in size, might be a custom weapon model or something). osp sometimes downloads these. In folder views go to 'detail' mode and filter by date, it will tell you if any 'weird' pk3 file was added recently with or without your consent.
;Auto Generated by PunkBuster Client
pb_msgprefix "^2PunkBusted Client" //[PB Message Prefix (default=5)]
pb_sleep 500 //[# of Milliseconds (default=250)]
pb_security 0 //[0=No, 1=Yes (default=0)]
pb_system 0 //[0=No, 1=Yes (default=0)]
pb_logtofile 0 //[0=No, 1=Yes (default=0)]
pb_sslog 0 //[0=No, 1=Yes (default=1)]
pb_sssave 0 //[0=No, 1=Yes (default=0)]
pb_ssoptions 640 480 50 50 1 //Set local PB screenshot options
pb_load pbcllog.cfg //load remote logging settings
Edit to your liking, and after saving make the file read-only. This will prevent pb from dicking with these settings (it resets pb_security unless it's read-only for instance).
EDIT: Try pb_logtofile 1 After you get kicked, go to the pb dir and see if there is a new txt file which might contain the error message.
Also make a pbsys.cfg in the pb dir and put this:
pb_system 0
Match it to whatever pb_system preference you have in the previous file. Make it read-only also.
Getting dropped from the game, you might be getting an 'invalid pk3 files referenced' error. This is osp right? Well anyway you won't know if that's the error you get, other players should be able to notice what the error is when they are in-game.
Check your osp and baseq3 dir for any odd pk3s in there (the type that are several kbs in size, might be a custom weapon model or something). osp sometimes downloads these. In folder views go to 'detail' mode and filter by date, it will tell you if any 'weird' pk3 file was added recently with or without your consent.