mirror of
https://git.code.sf.net/p/quake/quakeforge
synced 2025-01-29 20:20:43 +00:00
Fixups for my glspeed configs, which were uh, out of sync with cvs >P
cl_max_particles got changed to r_particles_max, also I added in cl_maxnetfps at 30 and edited cl_maxfps to 72 since that should work nicely with maxnetfps now :) Tim McGrath (Misty-chan)
This commit is contained in:
parent
e782153743
commit
9dc5cf6591
2 changed files with 12 additions and 12 deletions
|
@ -58,14 +58,14 @@ gl_fb_models "0"
|
|||
|
||||
// Rocket trails, smoke etc. Turn off to gain a LOT of fps in battles, as well
|
||||
// as make it a hell of a lot easier to see your enemy.
|
||||
// NOTE: Heck of a lot easier to use cl_max_particles to reduce
|
||||
// NOTE: Heck of a lot easier to use r_particles_max to reduce
|
||||
// how many you see instead of just shutting this off now :)
|
||||
r_particles "1"
|
||||
|
||||
// How many particles can be seen in your vision? Default is 2048. 60 is just
|
||||
// enough to see what is going on without slowing down at *all* on my
|
||||
// old voodoo 1, so other systems likely can handle far more than this
|
||||
cl_max_particles "60"
|
||||
r_particles_max "60"
|
||||
|
||||
// Toggles lavaball and rocket fireballs, - 0 gives a bit of a speed up.
|
||||
gl_fires "0"
|
||||
|
@ -113,10 +113,10 @@ cl_cshift_damage "0"
|
|||
cl_cshift_content "1"
|
||||
|
||||
// client's maximum fps allowed. 72 is the highest it can be set to
|
||||
// However, and this is important, setting it higher currently
|
||||
// causes more packets to need to be sent. This is bad, so mine is set to
|
||||
// 30 for the moment
|
||||
cl_maxfps "30"
|
||||
cl_maxfps "72"
|
||||
|
||||
//Set to how many frames per second worth of *data* is sent to client
|
||||
cl_maxnetfps "30"
|
||||
|
||||
// Set to 0 to go faster, 1 is older mode and slower
|
||||
// Or not. Some people say 0 is slower and 1 is faster.
|
||||
|
|
|
@ -59,14 +59,14 @@ gl_fb_models "0"
|
|||
|
||||
// Rocket trails, smoke etc. Turn off to gain a LOT of fps in battles, as well
|
||||
// as make it a hell of a lot easier to see your enemy.
|
||||
// NOTE: Heck of a lot easier to use cl_max_particles to reduce
|
||||
// NOTE: Heck of a lot easier to use r_particles_max to reduce
|
||||
// how many you see instead of just shutting this off now :)
|
||||
r_particles "1"
|
||||
|
||||
// How many particles can be seen in your vision? Default is 2048. 60 is just
|
||||
// enough to see what is going on without slowing down at *all* on my
|
||||
// old voodoo 1, so other systems likely can handle far more than this
|
||||
cl_max_particles "256"
|
||||
r_particles_max "256"
|
||||
|
||||
// Toggles lavaball and rocket fireballs, - 0 gives a bit of a speed up.
|
||||
gl_fires "0"
|
||||
|
@ -114,10 +114,10 @@ cl_cshift_damage "0"
|
|||
cl_cshift_content "1"
|
||||
|
||||
// client's maximum fps allowed. 72 is the highest it can be set to
|
||||
// However, and this is important, setting it higher currently
|
||||
// causes more packets to need to be sent. This is bad, so mine is set to
|
||||
// 30 for the moment
|
||||
cl_maxfps "30"
|
||||
cl_maxfps "72"
|
||||
|
||||
//Set to how many frames per second worth of *data* is sent to client
|
||||
cl_maxnetfps "30"
|
||||
|
||||
// Set to 0 to go faster, 1 is older mode and slower
|
||||
// Or not. Some people say 0 is slower and 1 is faster.
|
||||
|
|
Loading…
Reference in a new issue