Useful Keybinds

This site has very detailed information about UT2004 game settings

http://www.tweakguides.com/UT2004_1.html

Now that I have a Medic charater I will be switching between Medic and LW. Medic will be for small maps and LW for ONS. But I, being a slow typer, have a hard time hitting escape then SETTINGS then PLAYER the retyping my other charater name all before the next maps starts (depending on which map wins there's not much time)
Here are two ways to do this:
1. In your USER.INI file pick two unused keys and place your two names after them. Mine looks like this:
GreySlash=setname [DC]FodderFigure
GreyStar=setname [DC]FodderMedic
Now if I see an ONS map winning I just press GreySlash and when a small map is going to win I press GreyStar.

2. If you don't fell like doing like I wrote above or messing with the USER.INI file then open console in game and type setname new name

You can check to see if your name changed by hitting the F1 key to bring up the scores with the names in them. Your new charater doesn't take effect until the map changes or you log off then on again.

-------------------------------------------------------------------------------------
To fire continuously

As a medic I tend to run around a lot with my finger continuously on the fire button, boy does it get tired. So here's a bind I use to set fire to run continuously without any effort.

In the Aliases section you'll find lines which look like this:
Aliases[29]=
Aliases[30]=
Aliases[31]=
Aliases[32]=
etc...
Just place this line in that section where there are some aliases that aren't used. It doesen't have to be "35" .

Aliases[35]=(Command="Toggle bFire",Alias="ToggleFire")
Now just go down and place this line after the key you want to bind it to.

BUTTON=ToggleFire

just replace BUTTON with your prefered keyboard button

Press the button to toggle the fire mode on and off

I went to the site suggested at the top of this page, and I've now become addicted to 150 FOV. It looks insanely weird at first, but now I'm more used to 150 than 100 or 90. Consider trying it. If you do try it, don't change to anything less for at least a week. If you aren't indifferent or don't love it, tell me. FYI, the max FOV is 170, though that goes far enough so as to show environment culling around the edges.

Kohan wrote:

I went to the site suggested at the top of this page, and I've now become addicted to 150 FOV. It looks insanely weird at first, but now I'm more used to 150 than 100 or 90. Consider trying it. If you do try it, don't change to anything less for at least a week. If you aren't indifferent or don't love it, tell me. FYI, the max FOV is 170, though that goes far enough so as to show environment culling around the edges.

Yeah man. I use 120, and it's great. Feels a lot faster, too. It's weird playing on someone else's machine now, their game seems messed up :-O

Yeah, I once switched back to 100, went 'Oh my GAWD' and switched back in about three seconds. I seem to actually play better with 150; it's rather weird. Try it. I haven't tried 120, only 130 and 150. Thank god for the above site. Good info, too. I now want to save up (sort of; I have $450, but I'm using that for a new computer. A very good one for being under $600) for a Logitech X700 mouse or whatever it was because of the usefulness of all the buttons. Well, that and my current one sucks. two buttons (no middle) and a mouseball. That's like, 100 years old!

Kohan wrote:

Yeah, I once switched back to 100, went 'Oh my GAWD' and switched back in about three seconds. I seem to actually play better with 150; it's rather weird. Try it. I haven't tried 120, only 130 and 150. Thank god for the above site. Good info, too. I now want to save up (sort of; I have $450, but I'm using that for a new computer. A very good one for being under $600) for a Logitech X700 mouse or whatever it was because of the usefulness of all the buttons. Well, that and my current one sucks. two buttons (no middle) and a mouseball. That's like, 100 years old!

I'm using a Razer Diamondback and I highly recommend it. They have since come out with a new mouse, the Copperhead, and I'm sure it's just as good if not better than mine.

http://www.razerzone.com/

Oooooohhh... beautiful. I think I'mma gonna get me a copperhead! Only problem it that it's $54, twice what I could find for a used X700 or whatever. But man, it looks great. Thanks for the referral.

Guys this is a Keybind thread.. keep it that way! If I see something posted here I read it with the intention of copying it to the top post, I don't hink I can do that with your posts. Please start a new thread.

Y'know how some computer mice have buttons to change the sensitivity on the fly? I figured out a way to do that with keybinds.

First create an alias for each sensitivity you want to use.

Code:

Aliases[36]=(Command="set PlayerInput MouseSensitivity 1.25",Alias="SnipeSense")

Just replace "1.25" with the sensitivity you want to use, and "SnipeSense" with whatever you want to call the alias. The quotes in the code should remain. (Someone please verify that you can only have 40 aliases, and can't just insert "Aliases[40]..." to get more?)

Now, find the key you want to use and set it equal to "name" (whatever you names the alias. You should set up two sensitivity aliases and set up your keybinds so you can switch between them. You could try using the switch technique, with the:

Code:

Aliases[36]=(Command="set PlayerInput MouseSensitivity 1.25|set input [key] FragSense",Alias="SnipeSense")

In this case there would be a second alias call "FragSense" that would act similarly, and [key] would be replaced by the key you were using to toggle sensitivity.

Hope it's useful. Could definitely save money on having to buy one of those fancy mice.

Hey, that I like. I wonder.............I am gonna try to get my FOV set up this way for different weapons.

That could work, though I remember seeing talk that some servers block changing your FOV. Changing sensitivity with the weapon could be useful. Let us know how it works.

Chyster wrote:

Hey, that I like. I wonder.............I am gonna try to get my FOV set up this way for different weapons.

I've played with it a bit. My default fov is currently 95 and I have a keybind that will change it to 80 and onrelease, set it back to 95. Fov 80 is the minimum btw, so you can't get a free zoom. When trying to combine this with a switch weapon command, I started running into limitations.

For example, I tried to switch to the shock and change my fov to 80, then onrelease, switch back to flak and fov 95. It would switch back to flak but leave my fov at 80.

I also played with some piped commands and the mouse wheel but ran into similar problems.

What you could do is set fov and weapon to the number keys, I believe, but I need either a button or the mouse wheel to change weps. The numbers are too slow for me.

You could bind the weapons around your movement keys. This is my weapon binding (using WSAD for movement)

r: rocket launcher
e: flak cannon
q: minigun
f: shield gun
v: sniper/lightning
c: link gun
x: shock rifle
z: superweapon
middle mouse: translocator

I leave the assault rifle and bio rifle on two and three, since those are right above my hand anyway.

320, did you put onRelease before each command? You may have just put it in once, assuming all commands afterward would be onRelease. Also, does anyone know if you can use a key to toggle something? like, hit E to change FOV, hit it again to change back?

The guide linked at the top says how, though not directly. The basic idea is to create aliases that reassign the key to each other.

so say you wanted to use h to toggle the fov between 120 and 80, the aliases would look like this:

alias[]=(command="fov 120|set input h fov_down", alias="fov_up")
alias[]=(command="fov 80|set input h fov_up", alias"="fov_down")

then you'd set h equal to one of the aliases

h = fov_up

In other news, I wrote a couple of scripts to toggle the detail. Now if I get on a big map that's killing my framerate, I just hit a key and my game looks like crap!

If anyone is interested I'll post a tutorial.