As a result I'd recommend leaving this set to 1.

Accidentally using a Rocket Launcher up close). In the heat of battle you may have difficultly knowing weapon you have (e.g. Bullet casings are ejected from nowhere) & B. There are 2 disadvantagous side-effects however A. You can see more of the screen (especially with larger weapons). Setting this to 0 will remove the weapon model from view. A value of 1 for x enables your weapon model to be shown on screen. Don't set it above your monitor refresh rate though or you may damage your monitor. Replace x with the desired refresh rate you want to use, e.g. With this you can force a specified refresh rate.

Once this amount is reached the oldest one(s) is removed & new one(s) placed. Reducing this number may help improve performance, especially in areas where there is a lot of action. x sets the maximum amount of decals that can be active in a singleplayer game. 0 will eliminate the flickering although can lower performance. Setting x to 1 may improve performance, although it may cause flickering with distant objects. 0 may improve frame rate in areas with normally wavy water. NOTE – 3dfx cards cannot perform Trilinear texturing filtering & Multi-texturing at simultaneously.

Setting it to the other settings will improve performance, but give increasingly worse image quality. Setting it to GL_LINEAR_MIPMAP_LINEAR (Trilnear) will yield best visual quality, but lowest performance. Valid entries for x are GL_NEAREST (worst), Setting this to 0 allows you set gl_overbright '1'. A value of 1 for x enables Multi-texturing, which can improve performance on some cards. Setting x to 0 disables this, although performance may improve as a result. Set x to 1 to enable Gourad shading of models for better improved visual quality. I'd recommend leaving this set to 0 or 1. 0.1, 1 or 20 reportedly fixes these problems. Leave at the default if none of the glitches mentioned are occuring. NOTE - This will not solve flickering cause by gl_ztrick '1'. Other values may fix flickering with decals or missing decals. I’d recommend leaving this at either 0 or 1. Setting it higher (up to 2) may improve performance but reduce image quality for models. Setting x to 0 gives best texture quality for models. Setting it higher (0 to 4) may improve performance but reduce image quality. A setting of 0 for x gives best image quality. Set it to 0 if your videocard doesn't support palettized textures. A value of 1 for x enables paletted textures. This will yield brighter & more vivid textures being displayed. A value of 1 for x enables maximum brightness mode. Depending on your video you may be able to use larger textures, e.g. If you've set r_lightmap '0', then also set x to 1, otherwise set it to 0. 0 disables this & may run faster, although potentially with visual anomolies (cracks between textures). Setting x to 1 may fix some visual tearing (fills cracks between textures), although possibly at a slight performance hit. If you have a card that can render in colour depths greating than 16 bit then try set this to 0. 0 renders all regardless which should reduce performance. Setting x to 1 enables the rendering of visible objects only. 0 is slower than 1, although more pleasing visually. A value of 0 for x fills cracks between textures, 1 makes these visible. Not appearing) try a lower value than the default. If you experience that such surfaces aren't displaying correctly (e.g. This has to do with surfaces such as fences. I'd recommend setting this to 1 if you want to see the 'real' effect tweaking display settings has on your frame rate. Setting x to 1 enables the display of your current frame rate, 0 disables this counter. 0 is the default, which uses slightly lower quality player models, although performance is oosted as a result.Ĭl_showfps 'x'. Setting x to 1 enables higher quality player models when playing network/internet games.

Half life 1 valid texture sizes