The major issue with my FPS is back, please help.

[ohurcool]

You really need to clean out your config or learn about cvars/scripting.. You probably have 150+ cvars in it that either don't exist or are functionless.

 

"r_picmip2" is a typo that gets copied over and over from one script kiddie to another. Easiest way to spot a cut-and-paste config is it has r_picmip2 in it. It's supposed to be "r_picmip 2" (or 3 or whatever). Again harmless but entertaining.

Not gonna comment on your other points.. but "r_picmip2" is not a typo. It's a real cvar that simply doesn't do anything. Type /r_picmip2 in your console, and you will see that it is set at 3 (default).

[PHANTASM]

Not sure if this helps. Not even sure if netclientprediction is ET cvar anyway.

 

from http://quakeworld.xbb.in/viewtopic.php?id=7

 

net_clientPrediction Adjusts client side prediction so that your client predicts gameworld updates such as player movement. Defaults to 10 milliseconds and it is best to leave this setting alone if you are not experiencing problems.Increasing this value adds additional client side prediction which may help if you have problems with gameworld updates from the server not being rendered in time. If this is the case try increasing net_clientPrediction to a small positive value of 5,10,15,20, 25 or 30, never higher. See net_clientLagOMeter for an explanation of how to determine if gameworld updates are not being rendered in time.If you have a stable connection, feel that Quake4 is over compensating and/or your projectile (rockets, bullets etc.) are not hitting despite you feeling they are on target you may wish to decrease net_clientPrediction to 1.Negative values are not recommended online except in extreme circumstances, for LAN play you may wish to set net_clientPrediction to 0.

 

/endcopy

 

You really need to clean out your config or learn about cvars/scripting.. You probably have 150+ cvars in it that either don't exist or are functionless.

 

 

Not gonna comment on your other points.. but "r_picmip2" is not a typo. It's a real cvar that simply doesn't do anything. Type /r_picmip2 in your console, and you will see that it is set at 3 (default).

 

I've read that it is a typo. Have to check on it. Thanks.

 

I learn nothing from people who agree with me lol.

[PHANTASM]

Hope this clears things up:

 

Posted 09 April 2009 - 04:16 PM (by Medic)

 

Thank you ^^

 

Just one thing about r_picmip2, there is a little story saying that someone was about create a cfg for his game and by ERROR he want to spell "set r_picmip 2" he did it wrong by spelling it "set r_picmip2" without space since then that r_picmip2 become regular cvar...

 

Oops Nice story!!! but you won't believe it ok here is something more realistic

 

r_picmip2 doesn't exist in ET and had no effect in Wolf multi player the only game where this cvar exist is wolf single player but r_picmip2 did the same thing as r_picmip for i.e. enemy player skin... It's the character Textures setting in the Wolf Single player system menu

but people copy past all cfg around and this cvar become popular and make people think it's very important in ET

 

/endcopy

[SunLight]

Here is the config which is made for bad graphics for more fps.. Which is why I dont know whats going on how can I get 18 fps with such awful graphics??? Someone help..i reinstalled issues still here.. :///

[...]

 

Many of the cvars you have in your config are *not* ET cvars (either misspelt, like g_fov, or totally invented/taken from other games). Don't know where you took those settings , anyway if they are not ET setting they won't do any harm as it's been said. They are just useless. Lol maybe I am answering in the wrong forum and this is not ET-related or your config is weird

 

Remember: if you can't see a cvar name inside et.exe or mods dll (using a hex editor or some find command) then that cvar doesn't exist. period.

 

Have you tried that benchmark demo thing I told you? Have you checked cpu usage, etc.?

 

If I have time I could go through all those (fake and real ;p ) settings, and maybe suggest you something.

 

Not gonna comment on your other points.. but "r_picmip2" is not a typo. It's a real cvar that simply doesn't do anything. Type /r_picmip2 in your console, and you will see that it is set at 3 (default).

 

if you have a cvar in *your* config then it will show, it will be autocompleted with tab, etc.

 

The only way to know if a cvar exists in et (and now we have also the source code, but not etpro's so this method is still the only one) is to check inside et.exe (for the engine) or the dlls in the mods (mod specific cvar), as ReyalP (or was it bani?) had pointed out in etpro forums centuries ago.

 

I checked, and there is no trace of r_picmip2 anywhere. So it doesn't exist. (Of course you can't do this with encrypted mods like the now dead antipro, etc. but you can with all other mods, etpro included).

 

That cvar is in your config... and it was in mine too, before I made some cleanup of useless cvars. Everyone just copies from other player's cfgs before learning how to do his own. It's normal.

 

Hope this clarifies the matter.

[dedz]

Isn't r_picmip2 just an old cvar brought into the game from RtCW except it doesnt really do anything?

[Flip]

I had my computer built for hardcore gaming, therefore I never have problems, 6gb ram, 400 series Nvidia, but I had a computer before and I use to have FPS problems all the time on World of Warcraft and Counterstrike. It only had 1gb ram, more then likely overcloking the cpu and overheating the whole thing. Here are a few things that may help you, but upgrading your ram/video card always helps for gaming.

Graphics tweaks

 

Intro to tweaking

 

Here I'll go through some tweaks that can help boost your FPS (frames per second). A good FPS can make a world of difference; it's just damn hard to shoot enemies if they keep "warping" across your screen.

 

Your FPS is determined mainly by 3 things:

 

* CPU clock speed (ghz)

* Graphics card

* RAM

 

Unfortunately, there's not much you can do to change these, which doesn't involve paying money... You can try overclocking your CPU; this can make a 1.7 Ghz processor go at the speed of a 2.0 ghz processor for example. However, this can cause your CPU to overheat (not a good thing). You can try getting a new graphics card, but it might not boost your performance much if your processor is the problem. For example, if it's a wimpy 866mhz, then a shiny Geforce FX card isn't going to save you.

 

There are some things you can control though:

 

* Drivers: this is the code that "talks" to your hardware. (like, "video card, draw a picture!") Sometimes drivers are poorly written or have some compatability problem that makes it run slowly on your system. So, if you know you have a kickass system, but you're not getting the performance you expect, try updating drivers for your video and sound cards. Keep in mind the "latest" drivers aren't always the best, although usually they are.

 

* Tweaking: That's what this whole section is about.

 

Now before you begin tweaking, make sure to add "cg_drawfps 1" to your config, so you can see your frame rate.

 

Tweaking cvars in the console

 

There are a couple of cool things you should know about entering cvars in the console... Firstly, you can press TAB while entering a cvar and the name will be completed... For example, type "/cg_wol", and then press TAB, and ET will automatically fill the rest for you ("\cg_wolfparticles "). Suppose you type in "/r_ati", and then hit TAB. Well, there are multiple commands that start in "r_ati", so instead of auto-completing it, a list will be displayed in the console:

 

]/r_ati [tab]

r_ati_truform_pointmode = GL_PN_TRIANGLES_POINT_MODE_LINEAR

r_ati_truform_normalmode = GL_PN_TRIANGLES_NORMAL_MODE_LINEAR

r_ati_truform_tess = 1

r_ati_fsaa_samples = 0

 

This is just a handy thing to know, you could get a list of all cg_ variables for example by typing "cg_" then pressing TAB.

 

You can also find out the current value and default value of any cvar by simply typing its name (with a slash) at the console:

 

]/r_texturemode

"r_texturemode" is:"GL_LINEAR" default:"GL_LINEAR_MIPMAP_NEAREST"

 

Finally, let's say you mess up some cvar... Then, to reset it back to the default value, simply type in "/reset (cvar)" in the console... For example:

 

]/reset g_gravity

 

Tweaks

 

set com_maxfps <n>

This lets you cap your FPS to some value. Due to numerical error in the Q3 engine, trickjumps work best at a steady FPS of 43 (good), 76 (great), or 125 (best). So if you want a steady FPS of 76 for example, then try to get your average FPS to be something like 80-90 (set com_maxfps to some really big number while you're doing this so you can see you`r true FPS without capping). Then once you are satisfied with the performance, add "com_maxfpx 76" to your config to cap it.

 

Ex: set com_maxfps 76

 

set r_picmip <n>

The bigger n is, the crappier your textures look, but it may improve performance on older video cards. Default value for n is 1. Allowed values are from 0 to 3.

Ex: set r_picmip 3

 

set r_picmip2 <n>

Similar to r_picmip. The default is already 3, so I don't see any reason to change it. You might be able to get better quality by lowering it, but as far as I can tell, the difference isn't noticeable.

 

set cg_wolfparticles <n>

This is 1 by default. If you notice your system slows down any time an airstrike goes off, then set this to 0. Besides boosting your FPS, turning off particles will also let you see through airstrikes more easily so you can shoot at people on the other side. The only disadvantage is that, without particles turned on, you might run into artillery strikes more often.

 

One option is to create a toggle script:

 

Ex: bind "K" toggle cg_wolfparticles

 

set cg_atmosphericeffects <n>

Turns on/off effects like rain or snow. There's really No reason why you would ever want this to be on, it just makes it harder to see and lowers your frame rate...

 

Ex: set cg_atmosphericeffects 0

 

set r_gamma <n>

Higher values of n make your screen brighter, so you can spot enemies easier. Default is 1.0, allowed values are from 0 to 3. I recommend making your screen brighter because it lets you see targets more easily. Be careful you don't set it too high, otherwise levels like fueldump or radar with lots of snow will be way too bright.

Ex: set r_gamma 2.2

 

set r_intensity <n>

Higher values of n make your screen brighter. Default is 1.0, allowed values are from 0 to 1.5

Ex: set r_intensity 1.2

 

set r_mapoverbrightbits <n>

Higher values of n make the shadowy parts of a map lighter, so you can spot enemies hiding in darker areas. Default is 2, allowed from 1 to 3. Setting it to 3 may help see targets that are hiding in shadows

Ex: set r_mapoverbrightbits 3

 

set r_dynamiclight <n>

Turns on (n=1) or off (n=0) dynamic light. Dynamic light is used very little in the game. I suggest you leave it on, because it is what makes the "glow" around dynamite, which is very useful to know when dyno has been planted.

Ex: set r_dynamiclight 0

 

set cg_shadows <n>

Turns on (n=1) or off (n=0) the little circular shadows that appear under your feet. Set this to 0 if you want, although the FPS boost will probably be negligible.

Ex: set cg_shadows 0

 

set r_finish <n>

Setting this to 1 enables "sync every frame". This is ONLY important if you have some device lag, like mouse or keyboard. (Perhaps if you have a wireless mouse and you find it lags behind your actions). If you don't notice your keyboard or mouse lagging, then set this to 0 to gain a few FPS.

Ex: set r_finish 0

 

set r_detailtextures <n>

When detail textures are enabled (n=1), it means that basically every object is textured twice to make it look more detailed. Obviously this is slower, so try disabling this (n=0) if you want to get a nice FPS boost.

Ex: set r_detailtextures 0

 

set r_subdivisions <n>

If you want a little performance boost, set this to 999. Otherwise, set it to 4.

Ex: set r_subdivisions 999

 

set r_texturemode <n>

This lets you set texture filtering. The most common values are:

 

(low quality): GL_NEAREST

(good quality): GL_LINEAR_MIPMAP_NEAREST (a.k.a. bilinear filtering)

(great quality): GL_LINEAR_MIPMAP_LINEAR (a.k.a. trilinear filtering)

(good quality): GL_LINEAR

 

In case you don't know, filtering is somewhat like antialiasing, except for textures. You can see what the game looks like without filtering by setting r_Texturemode to GL_NEAREST. It's pretty ugly, and everything is very "pixelated" or "blocky".

 

The default is bilinear filtering, and this will give you the best performance, and pretty good quality. For "best" quality you can use trilinear filtering, although there might possibly be some dip in FPS.

 

There's one problem with bilinear and trilinear filtering; both of them make your crosshair blurry. Personally I like to use a small crosshair, so this really annoys me because when the crosshair is blurred, I can barely see it. So, if this happens with you, then I'd suggest using GL_LINEAR. This mode will filter the textures and looks almost as good as bilinear filtering; yet the crosshair will still appear pretty sharp. BUT, be warned, using GL_LINEAR will likely cause a noticeable decrease in your FPS.

 

You could even use GL_NEAREST as your filtering mode but I wouldn't recommend it, because it looks like crap. I actually used to use this because, well, I didn't know about GL_LINEAR at the time

 

Ex: set r_texturemode GL_LINEAR

 

set r_fastsky <n>

If you set this to 1, it will just draw a solid color for your sky. This may give you a slight improvement in your FPS. It's not much, but then again, who cares how pretty the sky looks?

 

Ex: set r_fastsky 1

[Glyphz]

Try R_mode 4 might help