View Full Version : My UT2003 Tweak Guide

Pages : [1] 2

10-06-02, 07:00 PM
DXnfiniteFX's UT 2003 Tweak Guide

We all agree--UT2003 rocks, but it'll rock your system even harder. I have been trying to tweak the heck out of it to get it to run better while sacrificing a minimal amount of image quality. Here are some general settings that you may or may not need that will effect performance. Obviously, everyone's system is different and many variables can effect performance. I will first explain what the setting does and the type of performance hit it can potentially create. My recommendation will follow. Again, the minimal FPS is your own preference, so follow the guidelines to tweak to what you believe to be the best of both worlds.


Before any tweaking happens, make sure all your drivers are the most current and up to date. This is very important and vital. First, install the latest version of DirectX. Then, install the latest video card drivers and sound card drivers. Another worthy update are chipset drivers. Also, install the latest updates for your OS. Last but not least, install the latest patch for UT2003. As of now, there isn't one, but rumors are there will be one eventually and hopefully it will feature performance optimizations.

Now the tweaking can begin in earnest. First, locate your D3D settings in the ut2003.ini file in your system directory. Here are the settings that you can tweak:


I find that this gives me a good amount of image quality with some performance tweaks added in from what is by default. Again, these are general guidelines and you can tilt your tweaking toward either image quality, performance, or a good mix of both. Allow me to go into further detail regarding these settings:

DetailTextures--Does not offer much more FPS when disabled. Besides, it makes the game look more detailed. Certainly can't hurt to leave it on. I recommend to leave it on.

HighDetailActors--This is the "high world detail" setting. Depending on the map, it can create a significant performance decrease. When playing with bots, this will really kill your FPS. Note that when disabled extra special effects will not be rendered. For example, the shock rifle fires a bland line instead of the curvy energy bolt. Recommend leaving it off.

SuperHighDetailActors--This is the "highest world detail" setting. I find the only difference from "high" is that it renders extra map objects such as more trees. Recommend leaving it off.

UsePrecaching--Loads all textures to memory before starting map. Recommend set to on.

UseTrilinear--Increases image quality of textures with minimal performance hit. Recommend it on.

AdapterNumber--This is for machines with more than one graphics card. Don't know how this setting is changed, but it likely doesn't matter since you probably don't have more than one graphics card anyway.

ReduceMouseLag--Setting this to off will increase your FPS, but some find it causes too much mouse lag. I myself do not notice too large of a difference as far as mouse movement goes. Whether or not it is worth the extra FPS is purely up to you. Set to your preference.

UseTripleBuffering--Increases performance. Creates an extra buffering zone beyond doube buffering to render frames ahead of what you are seeing. Leave it on.

UseHardwareTL--Uses hardware T&L. Obviously, it is faster and prettier than software. Leave it on.

UseHardwareVS--Controls vertex shading. The water might use this feature, but not sure if anything else does. Leaving it on is probably best for both image quality and performance.

UseCubemaps--I know this is used to render some objects such as water. You might get additional FPS with it off. I recommend leaving it on.

DesiredRefreshRate--Refresh rate. Set to the highest refresh your monitor supports on the resolution you want to play on.

UseCompressedLightmaps--Compresses lightmaps. A demanding game like this with huge textures should be compressed. Leave it on for best performance.

UseStencil--Stencil may be stencil shadowing. However, I do not know how this setting is used and in what way. I do not know if it makes the game look better or worse, nor do I know what performance impact it has. Leave it the way it is for now.

Use16bit--Uses 16 bit color. If you got a newer card, leave it off for 32 bit color and more precise rendering. They can process the extra color with little performance impact. Older cards strongly recommended to set it on.

Use16bitTextures--Uses 16 bit textures. Use the same logic above. One thing worth of nothing is that switching it off to use 32 bit textures consumes twice as much VRAM.

MaxPixelShaderVersion--Has to do with pixel shaders. Leave it the way it is.

UseVSync--Syncs image with your monitor refresh rate. Can reduce "tearing," but might lower FPS. Some find it increases average FPS. If you want higher FPS and don't mind tearing, set it off. If you do mind tearing, set it on.

LevelOfAnisotropy--Anisotropic filtering. This can cause a performance hit. Set to "0" will increase FPS with minimal image quality loss. You won't tell the difference unless you look really hard. Recommend it set to "0."

DetailTexMipBias--Controls the LOD bias of textures. Set to your preference. The lower, the better the image. However, there is a small performance hit.

DefaultTexMipBias--Controls the LOD bias of detail textures. Set to your preferences. The lower, the better the image. However, there is a small performance hit.

UseNPatches--ATI users might want to leave this enabled. Smooths out edges with (from what I heard) minimal performance loss. If indeed it doesn't create a large performance hit, ATI users should set it on.

TesselationFactor--Has something to do with the number of subdivisions that make up curves. Increasing will make curves look better but increase polygon count, and decrease performance. Gamers familiar with the Quake engine know this as "curved surfaces." UT2003 already makes use of enough polygon count, and it is smart not to increase this setting. I haven't experimented with decreasing the setting, however. More than likely it will improve FPS, but how much I don't know, probably not drastically.

CheckForOverflow--No idea. Leave it as is for now.

DecompressTextures--Setting it on will not compress textures. With the incredible texture usage of UT2003, it is recommendded you leave it on if your video card supports this.

UseXBoxFSAA--Quite obviously, disable it. It doesn't do anything.

D3D is supposedly the API that UT2003 and its engine is optimized for. However, if you wish to try OpenGL to see if it helps out FPS (and for some, it does) do the following:

1) Go to your ut2003.ini in the ut2003\system folder.
2) Change RenderDevice=D3DDrv.D3DRenderDevice to RenderDevice=OpenGLDrv.OpenGLRenderDevice

As of the current build of UT2003, the some claim that OpenGL offers higher performance than D3D. Users made statements saying that the OpenGL API is less CPU dependent. In a game using the UT2003 engine, it is wise to save every bit of CPU power you can. Although Epic has made the claim that D3D also offers better image quality, users claim no reduction in image quality was noticable. I have tried OpenGL and I actually think it actually increases image quality and sharpens textures. However, I have also noticed some negative aspects. OpenGL has some very serious issues with grass. Walk near some and you'll know what I mean. I seriously believe this is also the same issue plaguing MOHAA when trees are around. There are also some sudden and drastic FPS drops. The renderer currently appears buggy. Hopefully in a future patch, both APIs would be optimized and not just D3D. The possible tweaking options for OpenGL are the same as the ones on D3D. The section for OpenGL is right below that of D3D. Follow the general guidelines above.

Now I will go into in-game settings:

Texture Detail--As far as I know, textures are simply stored in VRAM. As long as you have enough, it shouldn't degrade performance much, if at all. My testing supports my theory. Users with 64MB cards may want to set to either normal or high. Users with 128MB cards should set it to highest for best image quality.

Chararacter Detail--Same logic as above.

World Detail--Already covered in the "Actor Detail" section of the .ini file.

Physics--This is one of the strangest settings one can set in the game. When set to a higher setting, there is no warning about adverse performance hits. When testing this, I have found little to no difference in FPS. The only difference I am aware of is the shimmering in the water when set to normal or up. I don't seem to notice a difference in actual death animations. Have tested this numerous times in various bombing run maps and have enjoyed doing so:D As far as I know, the only benefit one gets for setting it higher than "low" is for the shimmering in the water. I recommend that you leave it on low just to save those CPU cycles.

Character Shadows--Draws shadows. For some, it kills performance. You're probably not gonna care much about the shadows either. Leave it off.

Detail Textures--Already covered in the .ini section.

Projectors--Don't possess much knowledge about what it does. I do know that character shadows are considered a projector. I also know the bulldog's headlights are projectors. But I don't know if this is used to any extent on the maps or characters, as I do not notice any difference nor do I know what impact it has on FPS. Although character shadows is considered a projector, I do not know if other projectors have the same impact on FPS. Leave it as is for now.

Decals--Draws scarring effects. Doesn't seem to make much performance difference, according to my tests. Set to your preference.

Decal Amount--When set to a higher setting, there is no warning about a performance decrease. According to my testing, there is little to no performance hit. Set to your preferences.

Foliage--Surprisingly, grass can take a good FPS hit. As of the current build of UT2003, OpenGL will cause massive drops in FPS when you stare at some. When I mean stare, I mean, filling the screen with foliage. Although you wouldn't normall do that, there is something definitely wrong with it. D3D users don't experience this issue. You may not miss the grass very much and I believe it is worth disabling. I recommend it off.

Trilinear Filtering--This is a filter that improves texture quality beyond bilinear filtering. If you got a semi-recent video card, enable it as it does not cause a performance hit. Users with older cards may want to leave it off.

Now on to the tweaks possible with the sound settings. Here is what the section looks like in the .ini file.


UseEAX--This uses the EAX capabilities on many newer sound cards. You can expect better effects + better sound positioning with this set on. However, expect a relatively large performance hit with it enabled. Whether or not it is worth the loss in FPS is hard to tell. Set to your preference.

Use3DSound--This uses positional audio to 5.1 speakers. Again, it will create a performance hit, but less than that of EAX. Set to your preference.

UseDefaultDriver--Uses the default driver in the system directory of UT2003. Setting it to false will use the driver located in the Windows directory. This has caused sound issues for me, but some claim it reduces the performance hit of hardware and EAX audio. Others claim it doesn't do much for performance hits. I would recommend you use the default driver.

CompatibilityMode--Uses a safe mode for the sound drivers. This will reduce sound quality and performance. Unless you have problems with sound, keep it off.

UsePrecache--Caches the sound before the match begins. Will increase performance in game. Keep it on.

ReverseStereo--This reverses the sound channels. For example, it reverses the sound usually broadcasted on the right channel to the left channel and vice versa. Set to your speaker set up.

Channels--Sets the amount of sound that can be broadcasted at one time. More channels will cause a performance hit while less channels will reduce sound quality. I recommend to leave it.

MusicVolume--Music volume. Set to your preference.

AmbientVolume--Ambience volume. Set to your preference.

SoundVolume--Effects volume. Set to your preference.

DopplerFactor--No idea.

Rolloff--No idea.

TimeBetweenHWUpdates--Not sure. I would guess this is the amount of time before sound is actually played. No idea what setting is best. Keep it that way for now.

DisablePitch--Disables pitch. I don't know what pitch is, but more than likely it is a sound effect or something. In addition, setting it off may save some performance, but probably not much. Not sure what setting is best. For now, leave it that way.

LowQualitySound--Uses bad sound quality to reduce CPU load. However, I doubt that it will increase FPS very much. I would say it isn't worth the bad sound. However, you should set this to your own system.

One final tweak that for some users create a noticable performance increase is to disable the page file and run the OpenGL renderer. This combo has worked very effectively for some users even with an older configuration. Do so if you are running Windows 2000/XP. But do not, repeat do not disable it if you are running Windows 9x.

I hope I have been able to help out. Thanks for the input. If I get additional feedback, I will add it in. However, the guide seems to be hampered by text amount limitations. Any solution, moderators?

10-06-02, 07:06 PM
thats a well tweaked ut2k3 setting for your system, but the problem is people will have different specs. slower/faster cpu, videocard, etc. if you want to make a good tweak, just elimanate the settings your ut2k3.ini is, and just explain every setting. also suggest people to update their drivers, use tweakxp pro to tweak their overall system, use a thirdparty videocard utility to enable agp4x/sba/fw, overclock their videocard and system, all of course under stable settings first. and than defrag their harddrives.

The Baron
10-06-02, 07:12 PM
UseHardwareVS--Not sure what it does, but pretty sure leaving it on would be better. ANY IDEAS ON THIS SETTING?

Guessing vertex shaders for the water (not sure). Stencil might be stencil shadowing a la Doom 3.

10-07-02, 06:05 PM
thcdru2k, I am already more or less satisfied with my performance. This is not a post on how to increase PFS for me, it is a guide on how to tweak the game for other people to read. Thanks, Baron, for the input. Addition advice would be welcomed.

If any moderator reads this, can this be stickied?

The Baron
10-07-02, 07:28 PM
Addition--dump D3D and use OGL if you are using the 4072 drivers. I've had a great deal of luck with it...

10-07-02, 10:13 PM
Originally posted by =SSC=The Baron
Addition--dump D3D and use OGL if you are using the 4072 drivers. I've had a great deal of luck with it...

You should always use OpenGL if possible in any game. It's a much less CPU dependent API and I notice absolutely no degredation in visual quality, but much improved performance all the way around. Sure, OGL has points where my framerate dips but even when it does that, the game is still very playable.

10-07-02, 11:58 PM
I have added in the recent submissions. Thanks again, Baron, for the help and participation.

I would prefer the additions of more information on the individual settings in the game, but actual comments on the guide itself are more than welcome. I would like to know if it is good enough.

Of course, more tweaking coverage will be added in at a later date.

By the way, anyone notice any difference with the physics and decal?

Most importantly, has this guide helped anyone?

The Baron
10-08-02, 12:41 AM
Physics helps if your CPU, not the GPU, is the major bottleneck. If you've got a 1Ghz CPU or so, lower physics a bit. Otherwise, it shouldn't make too big of a difference.

10-08-02, 12:47 AM
When my Ti4600 comes in on thurs, I'll make a multi-monitor guide. I made one for UT, so it shouldn't be hard. What do you guys want? 2 monitors @800x600 sound good?

10-08-02, 01:18 AM
Great job DXnfiniteFX! I got my UT2k3 running even faster!:D

10-08-02, 10:08 AM
Originally posted by =SSC=The Baron

Guessing vertex shaders for the water (not sure). Stencil might be stencil shadowing a la Doom 3.

Yes it's an option to use vertex shaders (geforce 3 and above)
Besides that here is a great thread for tweaking your game:

10-08-02, 05:43 PM
Thanks to the moderator who made this a sticky. That should help me out.

Upon further testing, it seems that the OpenGL renderer has some issues. There are some very sudden and unexpected drops in performance. I will later revise my guide.

Any opinions on the decal setting? I will add the changes to physics later tonight if possible.

I find it is strange that Epic did not include performance warnings for those two specific settings.

I will add sound and additional tweaking later.

Does anyone know if the iFeel settings have an impact on performance?

The Baron
10-08-02, 08:09 PM
Gonna go give D3D another shot.

I DO have some odd performance drops (mainly in Slaughterhouse--for whatever reason, that map runs like all hell for me), and I don't know if I tried D3D with the 40.72s.

Will report back in a bit.

The Baron
10-08-02, 10:06 PM
I have seen the light.

My specs:

1.4 TBird, not OC'd
GF3 (stock, non-Ti model)
512 DDR
WinXP Pro

First, I recommend setting texture detail to normal. Yes, normal. It runs better if you don't have that 128 megs of ram that the ******* GF4 users have. :p

Next... this will sound crazy, I know... disable the pagefile. Yes, disable it.

See, the difference between D3D and OGL is this...

D3D: slower, but more inclined to be smooth

OGL: WAY faster, but can get jittery like a small child that found your crack stash

Now, if you watch OGL normally, you'll see that when it pauses, the HD light goes on. It's because WinXP always uses a bit of the pagefile, so kill it dead. (don't do this in Win9x. it causes explosive diarrhea for your computer. not pretty..)

Turn off VSync.

Watch the Magic. :D

10-09-02, 12:21 AM
Baron, when you mention page file, do you mention the Windows page file? Wouldn't one need an insane amount of memory to do that?

Or do you mean the UT2003 cache file?

Speaking of the cache file, has anyone experimented with it and gotten better performance? If so, what setting did you use?

The Baron
10-09-02, 12:25 AM
Reading on the Infogrames forums, one of the UT programmers responded to somebody suggesting to up the cache size of UT with "NO!!! It's 32 megs for a reason! LEAVE IT ALONE!", so I went back to 32. Can't really tell a difference, but oh well.

And yes, I DO mean the Windows pagefile. 512 megs is all you need... have been running that way all night with no problems.

10-09-02, 12:34 AM
Great. I will now add that in. Changes have already been made.

You are saying that this is solve the sudden performance drops in OpenGL? By the way, did you happen to notice FPS drops staring at grass?

Does the page file tweak effect D3D performance?

It is strange a game that uses so much memory doesn't die when the page file is off, but that's a good thing.

The Baron
10-09-02, 12:56 AM
Doesn't solve them entirely, but they were MUCH better for me (maybe a 5 FPS drop now and then instead a 25 or 35).

Doesn't seem to affect D3D performance much. D3D seems to be a LOT more CPU-limited than OGL--somebody with a faster proc please check this out for me.

Haven't checked the grass... will check tomorrow.

10-09-02, 01:40 PM
I was running the game in d3d at 10x7 and it was horrible. That was using my old 28.90 driver set. I upgraded to 40.72s and ran ut binder, fired up OGL and watched my frame counter go no lower than 45 fps in a heavy fire fight, as high as 90fps while running. I am stoked.

10-09-02, 02:13 PM
In OpenGL, I do notice performance drops. I may drop down to about 40-45 fps which is much better compared to performance drops in D3D where I might go down to about 25-30 fps. I think it's pretty obvious which renderer I'll be using. :)

10-09-02, 02:43 PM
Here D3D runs much smoother than OGL.

The Baron
10-09-02, 03:09 PM
Like I said, I think it's CPU-related more than anything else, so there will eventually be a threshold in terms of CPU power where D3D WILL run better than OGL, at least for this version (who knows, one of them might be vastly improved in a patch).

10-09-02, 05:43 PM
Regarding the patch, Epic has stated there is one in the works. However, nothing about performance optimizations have been mentioned. The statement can be found at the official UT2003 forums.

Does anyone know if the next version will have better performance? This game seems to be screaming for better hardware.

The Baron
10-09-02, 06:39 PM
Of course it will have better performance--memory leaks and such will be eliminated.

10-09-02, 07:33 PM
I finally had a chance to review this guide from my home system that has my Ti4600. Following this, 1024x768 with Quincux in D3D runs fabulously and looks no worse than before, from what I can see. I might play around with a couple more settings, but I think we might have a winner here. :D

Side note w/regard to mouse lag. You can set it to false in the UT2003.ini file, but if you have RivaTuner in the D3D settings, under vsync, set your prerender limit to 2. That should reduce any mouse lag significantly while still allowing you to have the better performance that setting mouse lag to false in the .ini file provides. :)