Performance boosters

(n00ber) #1

Are there any console commands that I could use, like:

/r_fastsky 1
/cg_wolfparticles 0

I’d be glad to have your input.

(DG) #2

roughly in order of how much worth doing (considering fps help vs. ugliness, e.g. probably 0.01 fps extra from no brasstime [bullet casings] but unlikely to really notice it much either):

r_fastsky 1
cg_wolfparticles 0
cg_atmosphericaffects 0
cg_shadows 0
cg_marktime 0
cg_brasstime 0
r_drawSun 0
r_detailtextures 0
r_colorbits 16
r_texturebits 16
r_picmip 1 to 3
cg_showblood 0
r_dynamiclight 0
r_flares 0

(kotkis) #3

r_texturemode “gl_nearest_mipmap_nearest”
r_drawgun “0”
r_lodcurveerror “25”

(WolfWings) #4

Okay, a few terms to sort out first:

Nearest-Neighbor Filtering: GL_NEAREST_MIPMAP_NEAREST
Bilinear Filtering: GL_LINEAR_MIPMAP_NEAREST
Trilinear Filtering: GL_LINEAR_MIPMAP_LINEAR

On video cards except Voodoo-based ones, older pre-GeForce NVidia, and pre-Radeon ATI cards, Nearest-Neighbor filtering can actually be SLOWER than Bilinear or Trilinear filtering.

In fact, if you have a GeForce, Kyro, Matrox Gxxx, or Radeon card, Trilinear is, effectively, free. If you have an older Voodoo card, TNT, or pre-Radeon ATI card (Rage series), Bilinear is still free as a safe assumption. This is especially true if you use compressed textures. Trilinear can actually be faster than Bilinear for some cards in some cases.

Only older Matrox Mystique-class cards would gain any speed from Nearest-Neighbor over Bilinear filtering.

(n00ber) #5

Oh yeah, and could I put these commands into my etconfig.cfg? or should I put it in the etconfig.cfg that’s located in my profile?

(n00ber) #6

Are there any possible console commands that I could do to improve my “map travelling” time?

(DG) #7

map loading?

if youre vid card has at least 64mb of memory, try setting Compress Textures to No in the system options