Controller Configuration

[Joe999]

i have started making a configuration for flying vehicles using the xbox360 controller on the pc. if someone wants to try out, here it is:

/* ====================== */
/* xbox360 controller */
/* ====================== */
// ----------------
// d-pad:
// ----------------
// up: enter vehicle/switch seats
bind "joy1_DPAD_UP" "_activate" "" "vehicle"
bind "joy1_DPAD_UP" "_usevehicle" "" "default"
// down: leave vehicle/parachute
bind "joy1_DPAD_DOWN" "_usevehicle" "" "vehicle"
bind "joy1_DPAD_DOWN" "_activate" "" "default"
// left: select rockets
bind "joy1_DPAD_LEFT" "_weapon1" "" "vehicle"
// right: select LAW etc
bind "joy1_DPAD_RIGHT" "_weapon2" "" "vehicle"
// ----------------
// buttons:
// ----------------
// right analog trigger: thrust forward
bind "joy1_RIGHT_TRIGGER" "_sprint" "" "vehicle"
// top right button: thrust backwards
bind "joy1_6" "_speed" "" "vehicle"
// left analog trigger: fire weapon
bind "joy1_LEFT_TRIGGER" "_attack" "" "vehicle"
// top left button: switch weapon
bind "joy1_5" "_weapnext" "" "vehicle"
// A button: fire decoy
bind "joy1_1" "_weapon0" "" "vehicle"
// B button: select rockets
bind "joy1_2" "_weapon2" "" "vehicle"
// X: vehicle camera
bind "joy1_3" "_vehiclecamera" "" "vehicle"
// Y button: select missile
bind "joy1_4" "_weapon1" "" "vehicle"

just put the above into your autoexec.cfg file.

feel free to extend it and share what you've created :)

[Rawrness]

Does this work with a stick Joystick too? Or is it possible to modify it to work with one?

[Joe999]

don't know how mine works with a single stick, but it's definitely possible to modify the binding script that it works with yours

you can also use the controls settings menu to configure your stick

[Rawrness]

you can also use the controls settings menu to configure your stick

Problem is...I can't, there isn't any option for the Joystick there and attempting to bind keys to it doesn't work either, but the Joystick works perfect in other games. Is there any secret setting to enable the Joystick?

[FeaRog]

You can indeed configure other controllers & joysticks for the game, however as it is not yet exposed to the menu it is quite tricky. For those of you who already have a good understanding of using the console to set variables and bind controls though it shouldn't be too hard.

We support very flexible & powerful analog controller input, supporting up to four joysticks that can all be mapped to different controls/axes. For example, I once took a wheel & pedal setup and put just the pedals underneath my desk, and a joystick on either side of my keyboard - I set it up so the pedals give me Anansi yaw control, and the sticks controlling the other axes. All sorts of funky things like that are possible :)

Without further ado, here is a guide I wrote some time ago on the topic:


CONTROLLER INPUT GUIDE

Each controller device has a unique ID value identifying it.
Use the "listControllers" command to display a list of currently
connected controllers and their unique IDs. There are 4 joystick
slots available for binding, and you set the controller associated
with each using the cvars in_joy1_device through in_joy4_device.



BUTTON BINDING

The buttons of a controller are bound as follows:

bind joy<number>_<button> [command]

where <number> is the slot number for the controller, and <button>
is between 1 & 32, or one of the following:

DPAD_UP
DPAD_DOWN
DPAD_LEFT
DPAD_RIGHT
LEFT_TRIGGER
RIGHT_TRIGGER

eg: You want to bind the right trigger of the first joystick

bind JOY1_RIGHT_TRIGGER _attack


AXIS ASSIGNMENT AND ADJUSTMENT

There are several different input modes, at the moment these are
player, car, heli, and hovertank. Each input mode has a number of
axes defined - each is fully configurable. The parameters to tune
are:

joy - Joystick number (1-4) used to control this axis
axis - The axis of the controller that provides the input (0-7)
Note that the axis numbers vary between different
devices.
invert - Reverses the axis
deadZone - The threshold of controller input. Eg, if dead zone is
0.2, you have to move your controller past the 20% point
before it starts to affect the game
offset - The value of the controller when it first passes the
dead zone. Eg 0.2 deadzone with 0.1 offset: When the
controller is at 20% the input value will be 0.1 (10%),
and will increase from there
power - The input value is raised to the power of this number,
to allow acceleration. By default, the player input uses
a power of 4 for aiming, providing the ability to finely
aim using small inputs, but turn fast by moving the
stick to its limits. One gives a linear response.
speed - The scale factor used once the other calculations are
complete. The maximum value the other calculations will
reach is 1.0, so the speed is equal to the maximum value
that is fed into the game.

The CVars used to control these settings are of the form:

in_<mode>_<axis>_<parameter>
eg: in_player_yaw_axis


Unfortunately there is no standard for which button is where on your controller. Each manufacturer sets up their drivers differently, and there is even a lot of variance between different devices from the same manufacturer - for example I have two joysticks on my desks both from the same manufacturer, both in the same series of models, and they have entirely different axis & button numbering schemes. At present to determine which button is which is to use the Game Controllers section of the Control Panel - you can press each button in turn and note down the button number it corresponds to. At the moment you will have to use trial-and-error to figure out which axis is which. Note that this process doesn't take that long really.

A quick tutorial of me setting up a controller:

Plug joystick in, and fire up ETQW
Bring down the console, type listControllers
This should give you an entry something like "302105: Logitech Attack 3" (this is the joystick I'm using for this example). The number is the ID number of the controller.
Set this up to be joy1 by typing the following: in_joy1_device "302105" (of course, substituing the relevant ID for your controller)
Assuming you want to set this up to be helicopter yaw, enter the following:
in_heli_yaw_joy 1 -> this tells the input that for heli yaw it needs to look at joystick number 1 (which you previously configured to be your joystick)
in_heli_yaw_axis 0 -> this tells the input to look at axis number zero of the joystick



Then test it out. You will almost definitely need to use trial-and-error to figure out which axis number you should be using to map to the stick twist. All you need to do is set in_heli_yaw_axis to different numbers until you discover the right one. Odds are this may be reversed - you can flip this by using in_heli_yaw_invert. Once you've got that right you can then tweak the other values for the axis. The main ones of interest will be deadZone and speed, most likely - speed is basically sensitivity, and deadZone is how much you have to move the stick before the game will start responding. By increasing power you can make it so that the further you move the stick from the center the faster it will respond.

Binding is much simpler, eg:
bind "JOY1_1" "_attack"

This will set up button number one on your joystick to shoot. Most joysticks these days have the main trigger as button one, and the secondary trigger (often a thumb trigger) as button two - but these can vary wildly from manufacturer to manufacturer.

I generally set mine up in windowed mode, configuring it & tweaking it in a .cfg file so that my settings are all saved and easy to read & retrieve.

Note that the console has tab completion, so you can type things like in_heli_<TAB> and it'll list the cvars you can tweak.

I hope this helps! :)

[Pyroclastic]

Thats awesome thanx heaps, just going through the motions now of setting it up, will let you know how i go.

[Amuro]

the in_heli commands don't seem to work with the hovercraft.

[Rawrness]

A lot of good information in the guide, but I'm afraid it still isn't working. The strange thing is that my joystick is able to move the mouse cursor in the menus and such.

Edit:
To provide some more information to the developers in case the problem isn't that common:
Saitek X45 Joystick (and throttle)
Windows Vista 32 bit
And it's using the drivers provided by Vista, Joystick works perfectly in Flight Simulator X and the calibration tool in Windows but only the buttons work in ET:QW.

[Amuro]

A lot of good information in the guide, but I'm afraid it still isn't working. The strange thing is that my joystick is able to move the mouse cursor in the menus and such.
Same here. I was able to bind the buttons but not the axes.

[TTK-Bandit]

no success here either.
in menu it works, slow though. but in the world, no matter what axis I set, it does not change anything.

[ToonarmY]

I have the logitech extreme 3d pro. I would like to fly the tormentor with it, although i do not think i have the patience to write all those commands in console. If any1 has already dont it id much appreciate it if they posted the binds they used here and i could just copy them over. At this stage in the game i find it pretty stupid that there is no joystick configuration

[DragonTHC]

DITTO, buttons work, Axes don't
what gives?

using original xbox controller w/ xbcd 1.07

[DragonTHC]

how about a bump!

[dommafia]

I also have a logitech extreme 3d pro and would like to be able to fly the tormentor with it, FeaRog enlighten us :D

edit: hmm i have the joystick moving the flyer left and right and up and down. Now i just have to figure out how to assign the throttle

Ok now another problem, why does setting up the heli give the joystick control of the player movements too? i hope this is a bug. I thought vehicle control setup would not affect player control too...

[FartLUMP]

I have had some success, but i am having similar problems too. I managed to get the twist action of my stick set to the yaw (or rudder) as i want and i have set my throttle to gain and lower my altitude as I want. but i cannot at all seem to get my pitch and roll axis set. THIS IS EXTREMELY FRUSTRATING!!
I am using a microsoft force feedback 2 which the console picked up straight away. I have made a stop gap solution for the time being using joytokey and using it to mimic the mouse for pitch and roll, but it wont let me adjust the speed of which they work. (if i pull back it will pull back at one speed, pulling back slightly will go at the same speed as if i had pulled back hard)

[Rawrness]

As it seems the developers want all bugs/feedback in the Fileplanet forum I posted a thread there linking to this thread, but it went off page 1 within an hour and could use a bump here (http://www.forumplanet.com/QuakeWars/topic.asp?fid=28178&tid=2067033).

[Xerstau]

Here's a very basic config that I've just set up. The in_player, car and tank lines are to stop the joystick from working when I'm not in the flyer. Remember to use listControllers to find your joystick ID and use that instead of what I've used in "in_joy1_device". The axes may be messed up for you, but trial and error can fix that easily enough. Next task for me is to get the deadzones and power nice.

in_joy1_device "449029"
in_player_side_joy "0"
in_player_forward_joy "0"
in_player_yaw_joy "0"
in_player_pitch_joy "0"
in_car_side_joy "0"
in_car_forward_joy "0"
in_car_yaw_joy "0"
in_car_pitch_joy "0"
in_hovertank_side_joy "0"
in_hovertank_forward_joy "0"
in_hovertank_yaw_joy "0"
in_hovertank_pitch_joy "0"
in_heli_side_joy "1"
in_heli_forward_joy "1"
in_heli_yaw_joy "1"
in_heli_pitch_joy "1"
in_heli_throttle_axis "3"
in_heli_forward_axis "0"
in_heli_side_axis "2"
in_heli_yaw_axis "1"

[DragonTHC]

I think only those who have the logitech or MS joysticks seem to have it working. The rest of us have no axes.

I tried mapping all axes 0-7 to my player movement, to no avail. Axes do not work for my controller.

xbox controller s, xbcd 1.07
# 300866

[camper1]

Use Joy2Key as well, really good tool.

[Hakuryu]

For some reason my Logitech Dual Action (kind of like the PS2 controller) axis's are reversed (not inverted). Pushing left makes me go forward, right makes me go back, forward makes me turn left and backward makes me turn right.

Seems we need a in_heli_switch_axis command or something.

[TTK-Bandit]

having a logitech wingman extreme digital here, using microsofts "logitech wingman extreme" drivers.
the joystick works, as I can see the movement in the menu, but ingame does not work.
any ideas besides an emulator ?

[FartLUMP]

i still cannot map my stick axis except for throttle and twist only, they are axis 0 and 1 will be picked up by QW but any other axis are not picked up. switched every cvar to every access to test. every command i assign to 0 and 1 axis work fine. wondering if QW is having trouble picking up joystick configs properly. there is nothing wrong with my stick, works fine with other games for years

[DragonTHC]

maybe they didn't implement the joystick code fully into the public beta

[FeaRog]

Keep in mind that this is an unsupported system at the moment, as we are focusing on getting everything else right first. As such it is possible that there are currently bugs for some joysticks etc.
If you're having trouble getting it working then sit tight for now.

[DragonTHC]

Keep in mind that this is an unsupported system at the moment, as we are focusing on getting everything else right first. As such it is possible that there are currently bugs for some joysticks etc.
If you're having trouble getting it working then sit tight for now.

of course we know it's not supported. that's not going to stop us from whining about it :(

[grizzlybear]

thrustmaster dt rumble seta in_joy1_device "402540"

left ministick works in the console (mouse movement) but not ingame.(_axis 2&3)
right ministick (_axis 0&1), d-pad and buttons all work ingame

is there any chance of forcefeedback ?

[Rockn-Roll]

Here's a very basic config that I've just set up. The in_player, car and tank lines are to stop the joystick from working when I'm not in the flyer. Remember to use listControllers to find your joystick ID and use that instead of what I've used in "in_joy1_device". The axes may be messed up for you, but trial and error can fix that easily enough. Next task for me is to get the deadzones and power nice.

in_joy1_device "449029"
in_player_side_joy "0"
in_player_forward_joy "0"
in_player_yaw_joy "0"
in_player_pitch_joy "0"
in_car_side_joy "0"
in_car_forward_joy "0"
in_car_yaw_joy "0"
in_car_pitch_joy "0"
in_hovertank_side_joy "0"
in_hovertank_forward_joy "0"
in_hovertank_yaw_joy "0"
in_hovertank_pitch_joy "0"
in_heli_side_joy "1"
in_heli_forward_joy "1"
in_heli_yaw_joy "1"
in_heli_pitch_joy "1"
in_heli_throttle_axis "3"
in_heli_forward_axis "0"
in_heli_side_axis "2"
in_heli_yaw_axis "1"


And for what game is this for? There is NO in_car_side_joy command! there's pitch, steering, throttle, and yaw. I have a MoMo Racing wheel as well as a 3D Pro. I can not get either one to work...still trying. When I get some real commands working hten I will post them.

Don't we need to re-initialize the joysticks or something? Should we be able to just change it in the console while in the game and it will immediately start working? Do we need to restart the game? This is so frustrating...joysticks have been around for decades...even before the mouse...everything should already be set up so that we just need to change the in_joy#_device number and get SOMETHING to work.

[DragonTHC]

SD, you have you started looking into the axis issues with other sticks and controllers?

works fine in menu, but doesn't work in game.

[MadJack]

I decided to take a look at the controllers' settings posted by Joe999 and FeaRoq to come up with a way to make my Cordless Wingman work with ETQW. The buttons part has been explained already, so I won't go into that again except to say it has 11 buttons you can use in the game. The eleventh being the Start button.

The two main things about the Wingman is if it's either in Analog or Digital mode.

The main thing about the Wingman is its 2 levers and 1 pad. In analog mode, the left lever is disabled and is replaced by the pad. I didn't test that thoughroughly but it should work that way. I suggest you use digital because that's what I used to make my tests. If you prefer using the pad, you'll have to test yourself.

The Wingman has 5 axis to work with. Two for each lever and one for the throttle (slider in the back right).

The right lever uses axis 0 and 1. 0 being up and down, 1 being left and right.
The slider uses axis 2 and should be reversed because its leftmost position gives highest value.
The left lever uses axis 3 and 4. 3 up and down, 4 sideways.

What you want to do is hook your in_[vehicle]_[direction]_axis [axis (hence lever) number to use]

So, for exemple, if you'd want to use the Strogg Tormentor, you would modify the in_heli_* settings similar to these.

in_heli_side_axis "2" <-- turn lef/right with left lever
in_heli_forward_axis "3" <--- pitch forward/backward with left lever
in_heli_yaw_axis "0" <---- roll left/right with right lever
in_heli_throttle_axis "1" <--- power up/down with right lever

You also could tweak the other variables to smooth out the way that particual vehicle will respond to the way you handle the levers. In the case of the Tormentor, you probably want the yaw to have a slow response so you don't turn upside down too fast.

That covers the meat of it.

Hopefully that will help someone. :)

If I made blatant errors or missed something, please PM me with the info, I'll look into it.

[DragonTHC]

why do controller numbers Change when you re-install them?

[Clord]

What is the point anyway? Mouse + Keyboard is superior combination against controllers. However this might be interesting.

[dommafia]

What is the point anyway? Mouse + Keyboard is superior combination against controllers. However this might be interesting.

Mouse & keyb is not better when it comes to aircraft.

[murka10]

today i started to configure my joystick, okay its a Trust Predator QZ501
i mapped the keys, but when coming to axes, by default my x and y were mixed, throttle was yaw and yaw was throttle. okay, i did my throttle and yaw and when i came to x and y i tried some axes and now only x works and when i move it left it moves both, i can't seem to understand as i have put every axis its number. will try to sort it out. tho to map buttons you dont have to bind, just open controls and press the joy button after you have defined in_joy1
i might have to write everything down and put them together, i just put two things for one axis
hmm, seems like all controllers including mouse have delay, i saw a thread once, i will look into it, it might be the acceration i feel is delay :P but when i move my stick its about 400msec of delay

i have also configured my PSX/PC wheel which has loads of buttons and is a well, steering wheel, will try to use this only in game, i wish i had a both hand joystick as in desecrator i use my petals/joystick to move and wish i could use my mouse to aim... well mouse aiming is the only way, i can still use my joystick in the tormentor but i have never used a joystick for a heli/jet mix, only used it in crimson skies.

[VMax]

I also have a Logitech Wingman Extreme Digital 3D. I tried entering the various incantations listed in this thread w/o success. Here's my question: In ET, you could make a *.cfg file to set FOV, buttons, vsays, etc. Pull down the console and type exec vmax.cfg. Can this be done in ET:QW and what is the filetype and where does it go?

I'd much rather type all this stuff into an editable file...so I can edit on-the-fly, then share with ya'll when I get it 'right.'

Appreciate hearing your thoughts (and successes) on this...

VMax

of the Junkyard Dawgs
www.clanjyd.com

[Icarus]

You can indeed configure other controllers & joysticks for the game, however as it is not yet exposed to the menu it is quite tricky. For those of you who already have a good understanding of using the console to set variables and bind controls though it shouldn't be too hard.

We support very flexible & powerful analog controller input, supporting up to four joysticks that can all be mapped to different controls/axes. For example, I once took a wheel & pedal setup and put just the pedals underneath my desk, and a joystick on either side of my keyboard - I set it up so the pedals give me Anansi yaw control, and the sticks controlling the other axes. All sorts of funky things like that are possible :)

Without further ado, here is a guide I wrote some time ago on the topic:


CONTROLLER INPUT GUIDE

Each controller device has a unique ID value identifying it.
Use the "listControllers" command to display a list of currently
connected controllers and their unique IDs. There are 4 joystick
slots available for binding, and you set the controller associated
with each using the cvars in_joy1_device through in_joy4_device.



BUTTON BINDING

The buttons of a controller are bound as follows:

bind joy<number>_<button> [command]

where <number> is the slot number for the controller, and <button>
is between 1 & 32, or one of the following:

DPAD_UP
DPAD_DOWN
DPAD_LEFT
DPAD_RIGHT
LEFT_TRIGGER
RIGHT_TRIGGER

eg: You want to bind the right trigger of the first joystick

bind JOY1_RIGHT_TRIGGER _attack


AXIS ASSIGNMENT AND ADJUSTMENT

There are several different input modes, at the moment these are
player, car, heli, and hovertank. Each input mode has a number of
axes defined - each is fully configurable. The parameters to tune
are:

joy - Joystick number (1-4) used to control this axis
axis - The axis of the controller that provides the input (0-7)
Note that the axis numbers vary between different
devices.
invert - Reverses the axis
deadZone - The threshold of controller input. Eg, if dead zone is
0.2, you have to move your controller past the 20% point
before it starts to affect the game
offset - The value of the controller when it first passes the
dead zone. Eg 0.2 deadzone with 0.1 offset: When the
controller is at 20% the input value will be 0.1 (10%),
and will increase from there
power - The input value is raised to the power of this number,
to allow acceleration. By default, the player input uses
a power of 4 for aiming, providing the ability to finely
aim using small inputs, but turn fast by moving the
stick to its limits. One gives a linear response.
speed - The scale factor used once the other calculations are
complete. The maximum value the other calculations will
reach is 1.0, so the speed is equal to the maximum value
that is fed into the game.

The CVars used to control these settings are of the form:

in_<mode>_<axis>_<parameter>
eg: in_player_yaw_axis


Unfortunately there is no standard for which button is where on your controller. Each manufacturer sets up their drivers differently, and there is even a lot of variance between different devices from the same manufacturer - for example I have two joysticks on my desks both from the same manufacturer, both in the same series of models, and they have entirely different axis & button numbering schemes. At present to determine which button is which is to use the Game Controllers section of the Control Panel - you can press each button in turn and note down the button number it corresponds to. At the moment you will have to use trial-and-error to figure out which axis is which. Note that this process doesn't take that long really.

A quick tutorial of me setting up a controller:

Plug joystick in, and fire up ETQW
Bring down the console, type listControllers
This should give you an entry something like "302105: Logitech Attack 3" (this is the joystick I'm using for this example). The number is the ID number of the controller.
Set this up to be joy1 by typing the following: in_joy1_device "302105" (of course, substituing the relevant ID for your controller)
Assuming you want to set this up to be helicopter yaw, enter the following:
in_heli_yaw_joy 1 -> this tells the input that for heli yaw it needs to look at joystick number 1 (which you previously configured to be your joystick)
in_heli_yaw_axis 0 -> this tells the input to look at axis number zero of the joystick



Then test it out. You will almost definitely need to use trial-and-error to figure out which axis number you should be using to map to the stick twist. All you need to do is set in_heli_yaw_axis to different numbers until you discover the right one. Odds are this may be reversed - you can flip this by using in_heli_yaw_invert. Once you've got that right you can then tweak the other values for the axis. The main ones of interest will be deadZone and speed, most likely - speed is basically sensitivity, and deadZone is how much you have to move the stick before the game will start responding. By increasing power you can make it so that the further you move the stick from the center the faster it will respond.

Binding is much simpler, eg:
bind "JOY1_1" "_attack"

This will set up button number one on your joystick to shoot. Most joysticks these days have the main trigger as button one, and the secondary trigger (often a thumb trigger) as button two - but these can vary wildly from manufacturer to manufacturer.

I generally set mine up in windowed mode, configuring it & tweaking it in a .cfg file so that my settings are all saved and easy to read & retrieve.

Note that the console has tab completion, so you can type things like in_heli_<TAB> and it'll list the cvars you can tweak.

I hope this helps! :)

is there anyway to assign turn-left/right to mouse X and pitch axi to mouse Y? please help!

[VMax]

Logitech Wingman Extreme Digital 3D update
This will probably be a long post, but I wanted to contribute what I learned through trial and error...even though I'm not done...

The config file you want to edit is located at...C:\Documents and Settings\*your name*\My Documents\Enemy Territory Quake Wars Public Beta\sdnet\*your tag*\base\profile.cfg

1. Before you start tweaking, make a folder called 'backup' and copy your cfg to it. Of course, you won't screw up your original file, right? But why take chances...

2. Initially when I started mapping, I couldn't figure out why some axes worked and some didn't. Then I re-read someone's thread where they mentioned mapping all the other vehicle (and player) joy references to "0".
Example
seta in_hovertank_side_joy "1" before
seta in_hovertank_side_joy "0" after

Change every 1 to a 0 (except for your in_heli stuff of course). Why do this? My trials and errors lead me to believe that you cannot have axes of joystick X mapped differently for different vehicles. One possible solution is to map everything (but the helicopter) to a non-existent joystick, 0. That's why you're doing this...

3. By trial and error I configured my joystick so the Tormentor flies like a helicopter...see syntax below. NOTE: two axes, rudder and elevator, were backwards for me, so I changed the invert from a "0" to a "1."

seta in_joy1_device "625016"

//rudder
seta in_heli_side_power "1"
seta in_heli_side_offset "0"
seta in_heli_side_invert "1"
seta in_heli_side_speed "140"
seta in_heli_side_deadZone "0.2"
seta in_heli_side_axis "1"
seta in_heli_side_joy "1"

//elevator
seta in_heli_forward_power "1"
seta in_heli_forward_offset "0"
seta in_heli_forward_invert "1"
seta in_heli_forward_speed "140"
seta in_heli_forward_deadZone "0.2"
seta in_heli_forward_axis "0"
seta in_heli_forward_joy "1"

//aileron
seta in_heli_yaw_power "1"
seta in_heli_yaw_offset "0"
seta in_heli_yaw_invert "0"
seta in_heli_yaw_speed "140"
seta in_heli_yaw_deadZone "0.2"
seta in_heli_yaw_axis "2"
seta in_heli_yaw_joy "1"

//blade pitch (for up & down)
seta in_heli_throttle_power "1"
seta in_heli_throttle_offset "0"
seta in_heli_throttle_invert "1"
seta in_heli_throttle_speed "140"
seta in_heli_throttle_deadZone "0.2"
seta in_heli_throttle_axis "3"
seta in_heli_throttle_joy "1"

4. I am having trouble configuring the buttons. I've read and re-read this thread and tried numerous times, but the binds do not take...here's what I'd like, if anyone has an answer - if not, I'll keep plugging away at it.

bind "joy1_1" "_attack"
bind "joy1_3" "switch between strockets and hyperblaster"
bind "joy1_6" "accelerate"
bind "joy1_7" "fire a decoy"
bind "joy1_8" "bail out"

Hope this helps someone...

-V-

of the Junkyard Dawgs
www.clanjyd.com

[FeaRog]

My trials and errors lead me to believe that you cannot have axes of joystick X mapped differently for different vehicles. One possible solution is to map everything (but the helicopter) to a non-existent joystick, 0. That's why you're doing this...

This shouldn't be the case - can you try remapping one of the other vehicle types to joystick 1, now that you've got a config working for the heli? They should all be independent. Since this is unsupported at the moment there are likely a bunch of bugs in it ;)

[murka10]

after long time flying with my joystick i dont like it anymore(dunno why), but i wonder if i can reconfig my mouse so x axis will be the tormentor yaw not side, it really helps in aiming with the mouse.

[Icarus]

This shouldn't be the case - can you try remapping one of the other vehicle types to joystick 1, now that you've got a config working for the heli? They should all be independent. Since this is unsupported at the moment there are likely a bunch of bugs in it ;)

can you please take a look at the config request I posted for keyboard and mouse, help is very much appreciated!

[dommafia]

i 3rd the request of changing the mouse X behavior.

[FeaRog]

It is not currently possible, sorry.

[dommafia]

It is not currently possible, sorry.

:( hopefully in beta 2 or even afterwards :infiltrator:

[VMax]

BUMP

What is the exact syntax to enable the following button/trigger operations...

bind "joy1_1" "_attack"
bind "joy1_3" "switch between strockets and hyperblaster"
bind "joy1_6" "accelerate"
bind "joy1_7" "fire a decoy"
bind "joy1_8" "bail out"

Joe999 added "vehicle" to the end of the strings. Tried that, then changed the word "vehicle" to "heli", "helicopter", etc. w/o any luck.

FeaRog said bind "JOY1_1" "_attack" but that doesn't work either. Case sensitive? Tried that too. BTW, thanks for reading/responding. I'm 99% sure that mapping joy1 to other vehicles, with different axes & buttons confuses the joystick inputs so nothing works - I never had success with the Tormentor until I mapped everything else to joy0. Will try again tonight per your recommendation, but I think I've found a bug for you.

I know someone reading this has a solution to the buttons for a Logitech Wingman Extreme Digital 3D. Post up fellas! The only way I can kill GDF now is by landing on them...:)

Thanks and to be continued.

-V-

of the Junkyard Dawgs
www.clanjyd.com

[murka10]

i guess you haven't put your device on the list.
you can actually map your joy buttons by using the controls menu, but when you want more buttons for one function like _weapon0 i have it on "1" "joy1_3" "END(mapped as a thumb button on my mouse)" you need to bind them.
also i have combined my 2 controllers (joystick + wheel) on some vehicles like tormentor, i use the foot petals for throttle... now i don't have to holt my second hand near the joysticks bottom.

[Tallen]

So you can't do something like, say:

seta in_heli_side_MOUSE

...and then rig the proper axis from there?

I tried fiddling with it but it wouldn't let me change to MOUSE while I was playing and I'm too tired right now to keep joining/leaving an empty game (heck the server I was on started filling up anyways).

[Icarus]

So you can't do something like, say:

seta in_heli_side_MOUSE

...and then rig the proper axis from there?

I tried fiddling with it but it wouldn't let me change to MOUSE while I was playing and I'm too tired right now to keep joining/leaving an empty game (heck the server I was on started filling up anyways).

dev just stated that it's impossible, maybe next patch? (big hope for me here)

[VMax]

you can actually map your joy buttons by using the controls menu, but when you want more buttons for one function like _weapon0 i have it on "1" "joy1_3" "END(mapped as a thumb button on my mouse)" you need to bind them.


Bingo - Thanks to Murka's tidbit I successfully configured my joystick.

-V-

[Ifurita]

Feel like posting your config? I'll combine it with Fearog's initial guide + some other resources I found and post it on 4 newbies

[Icarus]

It is not currently possible, sorry.

Can you point me on how to do the following control scheme?

Keyboard up and down arrow: pitch up and down in air
keyboard left and right: turn left and right in air
keyboard A and D: roll left and right.

[DragonTHC]

so, is the "axes in menu/no axes in game" problem being looked into?

[peoples]

Can I disable the joystick(MOMO Force) somehow? I don't want it to be used in ETQW.

[murka10]

lol, unplug? or easier is to put in_joy1_device "" and then its disabled, or you can just disable every axial movement.....

[peoples]

Plugging and unpluggin is bit too much for just 1 game hah. Commands are the thing I am after.

[peoples]

Didn't help, so no more ETQW for me then.

[dommafia]

Didn't help, so no more ETQW for me then.
Of all the ... ah never mind.

Let me get your game key i'll give it to someone that will appreciate this game...

[peoples]

It's not the game, I would gladly play it, but unpluggin the wheel everytime I wan't to play QW - if there would be a way.

[dommafia]

It's not the game, I would gladly play it, but unpluggin the wheel everytime I wan't to play QW - if there would be a way.

Someone already gave you the solution, you have to reset the joy1 to another device#. Theres no way for your controller to affect QW if it's not set in one of the 4 joy devices.

Read the first page for instructions.

[TTK-Bandit]

I would be happy if I could get it working just by unplugging my joystick, man the only thing that works for me are the joystick buttons. :(

[peoples]

Someone already gave you the solution, you have to reset the joy1 to another device#. Theres no way for your controller to affect QW if it's not set in one of the 4 joy devices.

Read the first page for instructions.

I did, and it didn't help.

[murka10]

now that cannot be possible, if you disable the joystick(by taking it off the list) it wont work in-game. are you shure you put seta in_joy1_device "", maybe you had it on joy2, try all, or type in_joy and press tab and you see all commands and values.

[dommafia]

now that cannot be possible, if you disable the joystick(by taking it off the list) it wont work in-game. are you shure you put seta in_joy1_device "", maybe you had it on joy2, try all, or type in_joy and press tab and you see all commands and values.

seta in_joy1_device ""
seta in_joy2_device ""
seta in_joy3_device ""
seta in_joy4_device ""

After you try those get back to us ;)

[peoples]

I cycled through all of them and no help, Wingman profiler should do the trick - disabling it from there in a profile for QW.

[peoples]

Seems that my logitech profiler is messing this up, so it is not QW's fault.

[IceCreamMan]

got ps2 controller working perfectly. great thread.

[mythosmc]

i got most of my config working on the joystick now, but is it possible to bind the rolling left /right to keyboard keys.. and make the up/down action on the joystick rudder up/down ? right now my up/down on joystick is actually set to rolling

[Acidictadpole]

Would it be possible (or even already available?) to have a mode which shows the buttons that have been pressed... maybe echoed in the console?

Such a system would make binds quite easy in the future. Although I don't know if it exists or not already

[Edam]

What exactly are the commands to enter to alter deadzone and the like? I keep getting unknown command errors...

[murka10]

check out the first page, it has a big tut(hint:few posts below)

Acidictadpole: prolly it will be done in the future, this beta has no real joystick support, just something for those who really need it.

mythosmc:hmm, every axis has its number differently on different joysticks... so try setting in_(vehicle)_(yaw/roll/forward/throttle/side/steering)_axis (number)

[DragonTHC]

alright, even in BETA 2, I still have the exact same problem.

my controller xy works in menu. I can configure any buttons I want and they work in-game, BUT, no axes work in-game.

Now is the time to fix these issues SD.

my controller is the original xbox controller with the xbcd 1.07 drivers.
controller ID is "301280"

it has left stick (x/y), right stick (rx/ry), triggers (-z/+z), dpad (hat), and 10 buttons which work just fine. I can map the axes to anything I want. I can map the buttons to anything I want also.

The controller works great in every other game I own.

[Quicksilver420]

What I need to do is somehow map my stick axis,all my buttons work fine.If I go forwards/backwards on the stick I go left/right on the screen and if I go left/right on the stick I go forwards/backwards on the screen.Could someone help me a bit? I tried in_player_forward_joy1_axis x and axis y

All I need to use the stick for is forward/backward movement,my mouse aims

[murka10]

no you put numbers not names of axes in that cvar. they are different with every joystick.

[Quicksilver420]

no you put numbers not names of axes in that cvar. they are different with every joystick.

Maybe like this? in_player_forward_joy1_axis 1 or 0,1,2,3 etc?

Is the actual command correct? just the axis I need to figure out now?

[DragonTHC]

Maybe like this? in_player_forward_joy1_axis 1 or 0,1,2,3 etc?

Is the actual command correct? just the axis I need to figure out now?

the problem may not be your axes.

There is an "unacknowledged" bug that causes controller axes not to work in-game.

[Jack-Carver]

It seems to me that force feedback joys dont work. I cannt get the axis of my MS Forece Feedback 2. Neither does the Logitech G25 worl. Only the gas and break beddals work but not the clutch. My old MS SW Precission Pro without Force Feedback works nut i really dont like it. Anyone also has that problem?

[murka10]

Maybe like this? in_player_forward_joy1_axis 1 or 0,1,2,3 etc?

Is the actual command correct? just the axis I need to figure out now?

type in in_ and press tab and youll see many cvars, the one you want is in_player_forward_axis 1(or 0-5)

[Quicksilver420]

type in in_ and press tab and youll see many cvars, the one you want is in_player_forward_axis 1(or 0-5)

I fixed it by inverting the x-y axis in the Logitech Profiler Program,it made the x axis the y axis,and vice-versa solving my problems.Although I would rather change it in game than having to run yet another program while gaming:mad:

[murka10]

you can, by the sentence i said or by the tut on the first page by fearog.
hmm, some vehicles will still have this problem with throttle and twist, you cant use a program to fix it.

[DragonTHC]

that's it. controllers with force feedback don't work in-game.

it's not that the force doesn't work, the axes don't work.

[Quicksilver420]

you can, by the sentence i said or by the tut on the first page by fearog.
hmm, some vehicles will still have this problem with throttle and twist, you cant use a program to fix it.

It doesnt work,my axis are criss-crossed in game,funny it works correctly in the menu.

[mythosmc]

is it possible to bind pitch up/down and yaw left/right to the joystick axis movement? and bind roll left/right to keyboard keys?

edit: I was able to bind all the joystick axis properly, but the real question is how do i bind rolling to keyboard?

[dommafia]

but the real question is how do i bind rolling to keyboard?


The developer (FearRog) said that is not currently possible on the previous page. Hopefully they'll add this on the final game.

[mythosmc]

bummer :( I guess flying with the mouse isnt so bad as long as the sensitivity gets toned all the way down

[DragonTHC]

so, SD why don't my controller axes work in-game?

[Knife]

I have an issue with setting up the Logitech 3D Pro. I can bind all the controls, run around, shoot, and when i fly the first time every thing is great. BUT, when I get out of the aircraft or are killed (and respawn), my character looks at the ground. My mouse can move the view up to normal, but it just goes back down to the ground, like as if I have a giant rubberband pulling my head to the ground. I haven't locked it down to which bind my be the cause of this, but I'm tired of toying with it for now. The next time I get a chance I will look into it further and report back my findings.

I truly hope that SD will be able to look into this, as well as other joystick makes, for the reason that many players fly with a joystick. Joystick binding issues can be a major hiccup when it comes to release. I know many existing players will be turned off if they can't use their controls.

[murka10]

im pretty shure that you have a throttle control on your joystick, or its not calibrated well. every joystick movement will defaultly have some affect, but it isnt right(ie throttle for look up/down). just disable joystick for player and car, look at the first page for those commands.

[kmfdm]

Does anyone have a config for the Logitech PS2-style mouse yet?

[Knife]

Here is the settings for the Logitech Extreme 3D Pro joystick. You may want to tweak the sensitivity settings and whatnot, but the the Axis and Inverts are correct, and I added some weapons, switch, decoy, and thrust.

Please note, to simplify things and to avoid a forward/pitch issue I had, I assigned the joystick "number" to Joystick "2", not joystick 1 like previously posted in this topic. Fill in the Joystick number where I have the "xxxxxx" by typing 'listcontrollers' in the console to find the one that corresponds to the Logitech 3D Pro.




//Controller Assignment//

in_joy2_device "xxxxxx"

//Joystick Axis Assignment//

in_heli_side_power "1"
in_heli_side_offset "0"
in_heli_side_invert "1"
in_heli_side_speed "140"
in_heli_side_deadZone "0.2"
in_heli_side_axis "1"
in_heli_side_joy "2"
in_heli_forward_power "1"
in_heli_forward_offset "0"
in_heli_forward_invert "0"
in_heli_forward_speed "140"
in_heli_forward_deadZone "0.2"
in_heli_forward_axis "0"
in_heli_forward_joy "2"
in_heli_yaw_power "1"
in_heli_yaw_offset "0"
in_heli_yaw_invert "0"
in_heli_yaw_speed "140"
in_heli_yaw_deadZone "0.2"
in_heli_yaw_axis "2"
in_heli_yaw_joy "2"
in_heli_throttle_power "1.5"
in_heli_throttle_offset "0"
in_heli_throttle_invert "1"
in_heli_throttle_speed "140"
in_heli_throttle_deadZone "0.2"
in_heli_throttle_axis "3"
in_heli_throttle_joy "2"

//Joystick Button Assignment for weapons//

bind "joy2_11" "_SPRINT" "" "default"
bind "joy2_12" "_back" "" "default"
bind "joy2_1" "_attack" "" "default"
bind "joy2_2" "_weapon0" "" "default"
bind "joy2_3" "_weapnext" "" "default"
bind "joy2_4" "_weapprev" "" "default"



These settings seem to work fine for me after a little sensitivity tweaking in the Wingman Software.

:dance:

[Rockn-Roll]

Can I disable the joystick(MOMO Force) somehow? I don't want it to be used in ETQW.

Someone already gave you the solution, you have to reset the joy1 to another device#. Theres no way for your controller to affect QW if it's not set in one of the 4 joy devices.

Read the first page for instructions.

Everyone...please pay attention. There are TWO issues in this thread! We need to break them up because the joystick/pad controllers are working, but none of the WHEELS are working, MOMO and G25 are racing wheels...they have a steering wheel like on a car...same size...it's not a little bitty controller like the wheel pads. They also have several digital buttons including a sequential shifter, paddle shifters like on formula one race cars, optional 6 speed shifter; plus analog brake & gas pedals, and optionally clutch pedal.

The whole point of peoples post is that the wheel is causing the mouse to move in the menus...the same thing will happen to a joystick that is not centered. It basically prevents him from selecting anything from the menus i.e. selecting online game, selecting a server, and clicking join because the wheel is turned and is moving the cursor to the edge of the screen.

All peoples needs to do is center his steering wheel...nothing else will work unless he manages to get Wingman to disable it, but even then I don't think it will work because for some reason ETQW is capturing the wheel for use in the menus, but not in the game. We either need a new thread to deal with racing wheels, or you joystick/pad people need to be more understanding with us wheel people. I'm still trying to get the wheel or pedals to work and still have not been able to succeed. We need some support for wheels in ETQW.

Another thing I might add is RAGE will be a racing game, and it would be idiotic for idsoftware to ignore wheels in that game...in ETQW it's just poor judgment on SD to put vehicles in a game and not support wheels. I really think it would be a good idea to support wheels in ETQW...that way idsoftware will have some wheel experience before going into RAGE. wheel controller settings are not simple...they are even more complex than joysticks. For an example check out the settings in rFactor of GTR2...both of which are top notch racing simulations...not just a game. Real race car drivers are turning to simulators...not the $69 ones with $300 racing wheels like the MOMO and G25, but $250,000 simulators with complete cockpit...some of us actually build scaled down versions that cost nearly $10,000 because we like to race that much.

[nasxxx]

ROFL, joystick on a FPS game with mouse players. GJ!

[Quicksilver420]

ROFL, joystick on a FPS game with mouse players. GJ!
You look for me online...you will get schooled.....old school style:cool:

[Rockn-Roll]

ROFL, joystick on a FPS game with mouse players. GJ!

I suppose you will get totally owned by us in RAGE especially since I will be using a steering wheel and pedals to drive my vehicle. When I get out of the vehicle then I switch to mouse and keyboard of course.

[contagan]

hi!
at first, i'm from germany so i want you to excuse bad english, if i do use it i hope you do understand me anyway.

a friend of mine got this "no axis is working in-game" problem with his joystick. so we tried some things and we got the idea that there could be a problem with joysticks connected via soundcard gameport.
my sidewinder precision pro works just fine in the game on my computer. i connected it via USB. his joystick doesn't work on his system, he connected via gameport. since we can't do a crosscheck, perhaps some of you guys can try out something. if you use a joystick via USB<->gameport adapter you can try to connect via gameport. if your joystick won't work via gameport the idea ist verified.

i hope you understand my point.

best regards

[bxgeant]

yeah pointless thread

[The Pope]

hi!
at first, i'm from germany so i want you to excuse bad english, if i do use it i hope you do understand me anyway.

a friend of mine got this "no axis is working in-game" problem with his joystick. so we tried some things and we got the idea that there could be a problem with joysticks connected via soundcard gameport.
my sidewinder precision pro works just fine in the game on my computer. i connected it via USB. his joystick doesn't work on his system, he connected via gameport. since we can't do a crosscheck, perhaps some of you guys can try out something. if you use a joystick via USB<->gameport adapter you can try to connect via gameport. if your joystick won't work via gameport the idea ist verified.

i hope you understand my point.

best regards

I've also been unable to get my gameport joystick working in Quake Wars, so that might be it. I don't have a USB joystick so I can't check that.

[ChiefRedCloud]

Bring down the console, :)


Please, color me DUMB. But how do I enter the consol? Thx.:confused:

[dommafia]

Please, color me DUMB. But how do I enter the consol? Thx.:confused:

ctrl + alt + ` (tilde key left of the #1 key)

[McAfee]

This joystick doesn't work correctly:
Logitech Rumblepad 2 (USB) (http://www.logitech.com/index.cfm/gaming/pc_gaming/gamepads/devices/264&cl=us,en)

The left analog stick doesn't work ingame, but works in menu. The right analog stick is recognized as Axis 0 and 1, while it is supposed to be 2 and 3. Seems the game is simply skipping the first pair of axis (the left stick)

PS: This is on the demo

[Quicksilver420]

yeah pointless thread
Go away,we are attempting to accomplish something:cool:

[ChiefRedCloud]

Thx dommafia. I appreciate the help. Most likely my last comment/question on the joystick. Is there not going to be any direct support for the joystick (any joystick) without haveing to hack the game?

I realise that this isn't a flight simulator. And I will most likley buy the game anyway. And I HAVE used a mouse to fly before and it has worked well. But this, I do not know. I will try turning the mouse sensativity down but I suspect that then the majority of my timeon the ground will be messed over. So final answer, most likely NO flying except as a passenger.

Any way thx for a very interesting game. I will pick up my copy next week if there are any left on the shelves. See you guys in game.

[montylee]

got ps2 controller working perfectly. great thread.

Hey bro, i have a PS2 controller connected to the PC and i am trying to make it work in ETQW. I got the button mapping right, but the two analog sticks don't work correctly. The right stick behaves weirdly i.e. when i move it to the left, the vehicle moves forward, so the directions are all messed up.

Since, u have managed to get it working, please post ur config file. Thanks in advance!

[bkv]

yep, same here please.

[MadKane]

i have started making a configuration for flying vehicles using the xbox360 controller on the pc. if someone wants to try out, here it is:

/* ====================== */
/* xbox360 controller */
/* ====================== */
// ----------------
// d-pad:
// ----------------
// up: enter vehicle/switch seats
bind "joy1_DPAD_UP" "_activate" "" "vehicle"
bind "joy1_DPAD_UP" "_usevehicle" "" "default"
// down: leave vehicle/parachute
bind "joy1_DPAD_DOWN" "_usevehicle" "" "vehicle"
bind "joy1_DPAD_DOWN" "_activate" "" "default"
// left: select rockets
bind "joy1_DPAD_LEFT" "_weapon1" "" "vehicle"
// right: select LAW etc
bind "joy1_DPAD_RIGHT" "_weapon2" "" "vehicle"
// ----------------
// buttons:
// ----------------
// right analog trigger: thrust forward
bind "joy1_RIGHT_TRIGGER" "_sprint" "" "vehicle"
// top right button: thrust backwards
bind "joy1_6" "_speed" "" "vehicle"
// left analog trigger: fire weapon
bind "joy1_LEFT_TRIGGER" "_attack" "" "vehicle"
// top left button: switch weapon
bind "joy1_5" "_weapnext" "" "vehicle"
// A button: fire decoy
bind "joy1_1" "_weapon0" "" "vehicle"
// B button: select rockets
bind "joy1_2" "_weapon2" "" "vehicle"
// X: vehicle camera
bind "joy1_3" "_vehiclecamera" "" "vehicle"
// Y button: select missile
bind "joy1_4" "_weapon1" "" "vehicle"

just put the above into your autoexec.cfg file.

feel free to extend it and share what you've created :)

I could not get this to work. And where do I find the autoexec.cfg? Is this code complete or untested? thanks!

[Mordenkainen]

I could not get this to work. And where do I find the autoexec.cfg? Is this code complete or untested? thanks!

See this (http://community.enemyterritory.com/forums/showthread.php?t=9160) thread for information on autoexec.cfg and config files in general.

[Niwon]

Here is the settings for the Logitech Extreme 3D Pro joystick. You may want to tweak the sensitivity settings and whatnot, but the the Axis and Inverts are correct, and I added some weapons, switch, decoy, and thrust.


:dance:


Used your settings to get my Logitech Extreme 3D Pro to work. Thanks m8, now mine is working too, and I've played around a bit with the keys most suited for what I am used to. :D

[FlyingSquirrel]

Still having a terrible time with this and my Sidewinder Forcefeedback 2 (no, I don't use it for the FF).

SD - WHY would you overlook something as basic as joystick input control panel, especially for the demo? This is how players decide if they're going to buy the game or not, especially when the hype is built around stealing Battlefield players...

1. Used the Logitech Wingman 3D settings provided as a base. Did the Listcontrollers trick and my joystick started working at least.

2. Pasted the settings in C:\Users\...\Documents\id Software\Enemy Territory - QUAKE Wars Demo\sdnet\flyingsquirrel\base\autoexec.cfg. Created autoexec.cfg from the existing profile.cfg there.

3. Right off the bat, the joystick is only offering RUDDER = Strafe Left/Right and THROTTLE = Forward/Backward. Axis 1 and 2 are not working, nor are the button binds.

Am I going to have to get my Ph.D. in Quake engine bindings to make the necessary modifications or is SD going to fix this?

Anyway, hoping someone here can help. It's been frustrating watching everyone fly around and be stuck on the ground - even if dropping arty is somewhat fun.

[FlyingSquirrel]

I didn't see enough "new at manually binding keys" feedback on the threads, so trying to provide more 101-level material below.

Also, nobody seems to mention Sidewinder, so here are the settings I found to be true with my FF2.

[Problems]
1. _FORWARD and _SIDE still not mapping to Sidewinder axis. :(
2. Not sure which wins out - Profile.cfg or Autoexec.cfg - if there are conflicts?
3. Usage of "_SPRINT" as a separate vector from _THROTTLE for hover-based aircraft is hard getting used to :)
4. Having problems when introducing carriage-returns in PROFILE.CFG.

[Progress]
5. All Buttons mapped properly. Had some problems with autoexec.cfg, but modifying bindings.cfg directly worked fine.
6. Twist Rudder (_Yaw, Axis 0, Rudder) and Throttle (_Throttle, Axis 1, Collective) working just fine with the below config.


[SIDEWINDER FF2 PHYSICAL TO VIRTUAL AXIS MAPPINGS]
AXIS 0: _YAW = RUDDER (Twist Left/Right)
AXIS 1: _THROTTLE = COLLECTIVE (Throttle Forward/Back).
AXIS 2?: _FORWARD = PITCH DOWN/UP (Stick Forward/Back)
AXIS 3?: _SIDE = ROLL (Stick Left/Right)


C:\...\sdnet\flyingsquirrel\base\PROFILE.CFG
seta in_heli_side_power "1"
seta in_heli_side_offset "0"
seta in_heli_side_invert "0"
seta in_heli_side_speed "140"
seta in_heli_side_deadZone "0.2"
seta in_heli_side_axis "3"
seta in_heli_side_joy "1"
seta in_heli_forward_power "1"
seta in_heli_forward_offset "0"
seta in_heli_forward_invert "1"
seta in_heli_forward_speed "140"
seta in_heli_forward_deadZone "0.2"
seta in_heli_forward_axis "2"
seta in_heli_forward_joy "1"
seta in_heli_yaw_power "1"
seta in_heli_yaw_offset "0"
seta in_heli_yaw_invert "0"
seta in_heli_yaw_speed "140"
seta in_heli_yaw_deadZone "0.2"
seta in_heli_yaw_axis "0"
seta in_heli_yaw_joy "1"
seta in_heli_throttle_power "1.5"
seta in_heli_throttle_offset "0"
seta in_heli_throttle_invert "1"
seta in_heli_throttle_speed "140"
seta in_heli_throttle_deadZone "0.2"
seta in_heli_throttle_axis "1"
seta in_heli_throttle_joy "1"


C:\...\sdnet\flyingsquirrel\base\AUTOEXEC.CFG
seta ui_name "FlyingSquirrel"

seta in_heli_side_power "1"
seta in_heli_side_offset "0"
seta in_heli_side_invert "0"
seta in_heli_side_speed "140"
seta in_heli_side_deadZone "0.2"
seta in_heli_side_axis "3"
seta in_heli_side_joy "1"

seta in_heli_forward_power "1"
seta in_heli_forward_offset "0"
seta in_heli_forward_invert "1"
seta in_heli_forward_speed "140"
seta in_heli_forward_deadZone "0.2"
seta in_heli_forward_axis "2"
seta in_heli_forward_joy "1"

seta in_heli_yaw_power "1"
seta in_heli_yaw_offset "0"
seta in_heli_yaw_invert "0"
seta in_heli_yaw_speed "140"
seta in_heli_yaw_deadZone "0.2"
seta in_heli_yaw_axis "0"
seta in_heli_yaw_joy "1"

seta in_heli_throttle_power "1.5"
seta in_heli_throttle_offset "0"
seta in_heli_throttle_invert "1"
seta in_heli_throttle_speed "140"
seta in_heli_throttle_deadZone "0.2"
seta in_heli_throttle_axis "1"
seta in_heli_throttle_joy "1"

[FlyingSquirrel]

Finally got it working. :D

1. Misread a post earlier about Force Feedback joysticks not recognizing the axis. Dragged out my Precision Pro 2 (non FF) and it worked great.

2. I hate binding controls manually this way. Finally got my autoexec.cfg working though. Below is my gift to anyone else who was forced to learn this. Yay, for some reason I feel smarter after wasting 2 hours on this.


C:\...\SDNET\FLYINGSQUIRREL\BASE\AUTOEXEC.CFG
seta ui_name "FlyingSquirrel"
seta in_joy1_device "590118"

seta in_joy2_device "541323"


//Joystick Axis Assignment For Precision Pro (541323)//


//AXIS 0, PITCH. STICK FORWARD/BACK, DON'T INVERT, CUSTOM SPEED 30 (140 DEFAULT)//
seta in_heli_forward_power "1"
seta in_heli_forward_offset "0"
seta in_heli_forward_invert "0"
seta in_heli_forward_speed "30"
seta in_heli_forward_deadZone "0.2"
seta in_heli_forward_axis "0"
seta in_heli_forward_joy "2"

//AXIS 1, ROLL. STICK LEFT/RIGHT, INVERT//
seta in_heli_side_power "1"
seta in_heli_side_offset "0"
seta in_heli_side_invert "1"
seta in_heli_side_speed "140"
seta in_heli_side_deadZone "0.2"
seta in_heli_side_axis "1"
seta in_heli_side_joy "2"

//AXIS 2, COLLECTIVE UP/DOWN. THROTTLE FORWARD/BACK, INVERT//
seta in_heli_throttle_power "1.5"
seta in_heli_throttle_offset "0"
seta in_heli_throttle_invert "1"
seta in_heli_throttle_speed "140"
seta in_heli_throttle_deadZone "0.2"
seta in_heli_throttle_axis "2"
seta in_heli_throttle_joy "2"

//AXIS 3, RUDDER LEFT/RIGHT. TWIST LEFT/RIGHT, DON'T INVERT//
seta in_heli_yaw_power "1"
seta in_heli_yaw_offset "0"
seta in_heli_yaw_invert "0"
seta in_heli_yaw_speed "140"
seta in_heli_yaw_deadZone "0.2"
seta in_heli_yaw_axis "3"
seta in_heli_yaw_joy "2"

//Joystick Key Bindings for Precision Pro//

BIND JOY2_1 "_ATTACK"
BIND JOY2_2 "_VEHICLECAMERA"
BIND JOY2_3 "_WEAPNEXT"
BIND JOY2_7 "_WEAPON0"
BIND JOY2_8 "_SPRINT"

[Mordenkainen]

Finally got my autoexec.cfg working though. Below is my gift to anyone else who was forced to learn this. Yay, for some reason I feel smarter after wasting 2 hours on this.

You are. Thanks for doing this!

[McAfee]

This joystick doesn't work correctly:
Logitech Rumblepad 2 (USB) (http://www.logitech.com/index.cfm/gaming/pc_gaming/gamepads/devices/264&cl=us,en)

The left analog stick doesn't work ingame, but works in menu. The right analog stick is recognized as Axis 0 and 1, while it is supposed to be 2 and 3. Seems the game is simply skipping the first pair of axis (the left stick)

PS: This is on the demo

Still no luck...
To be more specific, right analog stick is recognized in-game as:
(Physical::Logical)
Vertical movement::Axis 0
Horizontal movement::Axis 1

So I can succesfully map the right analog stick to whatever I want, but I got no luck with the left analog stick.

I've already tried using axis from 2 to 8, but nothing happens
Is there anyway to debug input? or see some raw stuff?

NOTE: The gamepad is fine, works fine on windows and other games. The left analog stick even works in the ETQW main menu (without setting any cvars at all)

[Homer J]

What does listControllers give you? Does it just list one controller?

[Gamehostingreviews.com]

Of those of you who have tried both the control and mouse, which one did you end up going with? I have a 360 control for pc on order, I'm curious. :)

[Amuro]

Finally got it working. :D

1. Misread a post earlier about Force Feedback joysticks not recognizing the axis. Dragged out my Precision Pro 2 (non FF) and it worked great.


So there's no way to make the Sidewinder Force Feedback 2 to work with the game?

[Mordenkainen]

Of those of you who have tried both the control and mouse, which one did you end up going with? I have a 360 control for pc on order, I'm curious. :)

I use the xbox 360 controller for piloting the anansi and tormentor and mouse/keyb for everything else (even the bumblebee).

[Cr0wley]

that's it. controllers with force feedback don't work in-game.

it's not that the force doesn't work, the axes don't work.

Damn :( I was getting quite good with the console (imho) too, just couldn't figure out why I couldn't actually move... Thanks for everyone's hard work, fingers crossed this changes in a patch - planes are meant to be flown with a stick! :)

[Sqwert]

set up a saitek evo so i can move using it + mouse to aim as player

seta in_player_side_power "1"
seta in_player_side_offset "0"
seta in_player_side_invert "0"
seta in_player_side_speed "140"
seta in_player_side_deadZone "0.2"
seta in_player_side_axis "1"
seta in_player_side_joy "1"
seta in_player_forward_power "1"
seta in_player_forward_offset "0"
seta in_player_forward_invert "1"
seta in_player_forward_speed "140"
seta in_player_forward_deadZone "0.2"
seta in_player_forward_axis "0"
seta in_player_forward_joy "1"
seta in_player_yaw_power "4"
seta in_player_yaw_offset "0"
seta in_player_yaw_invert "1"
seta in_player_yaw_speed "230"
seta in_player_yaw_deadZone "0.5"
seta in_player_yaw_axis "3"
seta in_player_yaw_joy "0"
seta in_player_pitch_power "4"
seta in_player_pitch_offset "0"
seta in_player_pitch_invert "1"
seta in_player_pitch_speed "230"
seta in_player_pitch_deadZone "0.2"
seta in_player_pitch_axis "4"
seta in_player_pitch_joy "0"

bind "joy1_1" "_attack"
bind "joy1_2" "_prone"
bind "joy1_3" "_movedown"
bind "joy1_4" "_sprint"

below works for Saitek evo axis numbers

tanks use joystick to move mouse to aim

seta in_hovertank_side_power "1"
seta in_hovertank_side_offset "0"
seta in_hovertank_side_invert "0"
seta in_hovertank_side_speed "140"
seta in_hovertank_side_deadZone "0.2"
seta in_hovertank_side_axis "1"
seta in_hovertank_side_joy "1"
seta in_hovertank_yaw_power "4"
seta in_hovertank_yaw_offset "0"
seta in_hovertank_yaw_invert "1"
seta in_hovertank_yaw_speed "230"
seta in_hovertank_yaw_deadZone "0.2"
seta in_hovertank_yaw_axis "2"
seta in_hovertank_yaw_joy "0"
seta in_hovertank_pitch_power "4"
seta in_hovertank_pitch_offset "0"
seta in_hovertank_pitch_invert "1"
seta in_hovertank_pitch_speed "230"
seta in_hovertank_pitch_deadZone "0.2"
seta in_hovertank_pitch_axis "3"
seta in_hovertank_pitch_joy "0"
seta in_hovertank_turn_power "1"
seta in_hovertank_turn_offset "0"
seta in_hovertank_turn_invert "0"
seta in_hovertank_turn_speed "140"
seta in_hovertank_turn_deadZone "0.2"
seta in_hovertank_turn_axis "3"
seta in_hovertank_turn_joy "1"
seta in_hovertank_forward_power "1"
seta in_hovertank_forward_offset "0"
seta in_hovertank_forward_invert "1"
seta in_hovertank_forward_speed "140"
seta in_hovertank_forward_deadZone "0.2"
seta in_hovertank_forward_axis "0"
seta in_hovertank_forward_joy "1"
seta in_heli_side_power "1"
seta in_heli_side_offset "0"
seta in_heli_side_invert "1"
seta in_heli_side_speed "140"
seta in_heli_side_deadZone "0.2"
seta in_heli_side_axis "1"
seta in_heli_side_joy "1"
seta in_heli_forward_power "1"
seta in_heli_forward_offset "0"
seta in_heli_forward_invert "1"
seta in_heli_forward_speed "140"
seta in_heli_forward_deadZone "0.2"
seta in_heli_forward_axis "0"
seta in_heli_forward_joy "1"
seta in_heli_yaw_power "1"
seta in_heli_yaw_offset "0"
seta in_heli_yaw_invert "0"
seta in_heli_yaw_speed "140"
seta in_heli_yaw_deadZone "0.2"
seta in_heli_yaw_axis "3"
seta in_heli_yaw_joy "1"
seta in_heli_throttle_power "1.5"
seta in_heli_throttle_offset "0"
seta in_heli_throttle_invert "1"
seta in_heli_throttle_speed "140"
seta in_heli_throttle_deadZone "0.2"
seta in_heli_throttle_axis "2"
seta in_heli_throttle_joy "1"
seta in_car_yaw_power "4"
seta in_car_yaw_offset "0"
seta in_car_yaw_invert "1"
seta in_car_yaw_speed "230"
seta in_car_yaw_deadZone "0.2"
seta in_car_yaw_axis "2"
seta in_car_yaw_joy "0"
seta in_car_pitch_power "4"
seta in_car_pitch_offset "0"
seta in_car_pitch_invert "1"
seta in_car_pitch_speed "230"
seta in_car_pitch_deadZone "0.2"
seta in_car_pitch_axis "3"
seta in_car_pitch_joy "0"
seta in_car_steering_power "1"
seta in_car_steering_offset "0"
seta in_car_steering_invert "0"
seta in_car_steering_speed "140"
seta in_car_steering_deadZone "0.2"
seta in_car_steering_axis "3"
seta in_car_steering_joy "1"
seta in_car_throttle_power "1"
seta in_car_throttle_offset "0"
seta in_car_throttle_invert "1"
seta in_car_throttle_speed "140"
seta in_car_throttle_deadZone "0.2"
seta in_car_throttle_axis "0"
seta in_car_throttle_joy "1"

[t-readyroc]

OK, I've got a Saitek Cyborg Evo as well. I'd like to use it for flying only. So what you're saying, Sqwert, is that I won't be able to copy/paste FlyingSquirrel's cfg's & have them work (with the appropriate id number)?

[Sqwert]

should work once you enter the correct id and axis numbers..

for some reason i "missed" testing "2" as axis number for throttle Doh!!

you dont have to use an autoexec , i just enter binds through console.

[Smiley]

hey there,

i finally got my Logitech Cordless Rumblepad working :dance:

may need some fine tuning:

//Logitech WingMan Cordless Rumblepad
//axis0 = right stick up/down
//axis1 = right stick left/right
//axis2 = throttle
//axis3 = left stick up/down
//axis4 = left stick left/right
//bindable keys:
//joy1_DPAD_UP, joy1_DPAD_DOWN, joy1_DPAD_LEFT, joy1_DPAD_RIGHT
//joy1_1 - joy1_11

seta in_joy1_device "427714"


//heli

seta in_heli_forward_joy "1"
seta in_heli_forward_axis "3"
seta in_heli_forward_power "1"
seta in_heli_forward_offset "0"
seta in_heli_forward_invert "0"
seta in_heli_forward_speed "140"
seta in_heli_forward_deadZone "0.3"

seta in_heli_side_joy "1"
seta in_heli_side_axis "1"
seta in_heli_side_power "1"
seta in_heli_side_offset "0"
seta in_heli_side_invert "1"
seta in_heli_side_speed "140"
seta in_heli_side_deadZone "0.3"

seta in_heli_throttle_joy "1"
seta in_heli_throttle_axis "2"
seta in_heli_throttle_power "1"
seta in_heli_throttle_offset "0"
seta in_heli_throttle_invert "1"
seta in_heli_throttle_speed "50"
seta in_heli_throttle_deadZone "0.1"

seta in_heli_yaw_joy "1"
seta in_heli_yaw_axis "4"
seta in_heli_yaw_power "4"
seta in_heli_yaw_offset "0"
seta in_heli_yaw_invert "0"
seta in_heli_yaw_speed "220"
seta in_heli_yaw_deadZone "0.3"


//car

seta in_car_steering_joy "1"
seta in_car_steering_axis "4"
seta in_car_steering_power "1.3"
seta in_car_steering_offset "0"
seta in_car_steering_invert "0"
seta in_car_steering_speed "250"
seta in_car_steering_deadZone "0.2"

seta in_car_throttle_joy "1"
seta in_car_throttle_axis "0"
seta in_car_throttle_power "1"
seta in_car_throttle_offset "0"
seta in_car_throttle_invert "1"
seta in_car_throttle_speed "160"
seta in_car_throttle_deadZone "0.2"

seta in_car_yaw_joy "1"
seta in_car_yaw_axis "-1" //disabled ;]
seta in_car_yaw_power "4"
seta in_car_yaw_offset "0"
seta in_car_yaw_invert "1"
seta in_car_yaw_speed "230"
seta in_car_yaw_deadZone "0.2"

seta in_car_pitch_joy "1"
seta in_car_pitch_axis "-1" //disabled ;]
seta in_car_pitch_power "4"
seta in_car_pitch_offset "0"
seta in_car_pitch_invert "1"
seta in_car_pitch_speed "230"
seta in_car_pitch_deadZone "0.2"


//tank

seta in_hovertank_side_joy "1"
seta in_hovertank_side_axis "2"
seta in_hovertank_side_power "2"
seta in_hovertank_side_offset "0"
seta in_hovertank_side_invert "1"
seta in_hovertank_side_speed "180"
seta in_hovertank_side_deadZone "0.3"

seta in_hovertank_yaw_joy "1"
seta in_hovertank_yaw_axis "1"
seta in_hovertank_yaw_power "4"
seta in_hovertank_yaw_offset "0"
seta in_hovertank_yaw_invert "1"
seta in_hovertank_yaw_speed "230"
seta in_hovertank_yaw_deadZone "0.2"

seta in_hovertank_pitch_joy "1"
seta in_hovertank_pitch_axis "0"
seta in_hovertank_pitch_power "0.4"
seta in_hovertank_pitch_offset "0"
seta in_hovertank_pitch_invert "1"
seta in_hovertank_pitch_speed "30"
seta in_hovertank_pitch_deadZone "0.2"

seta in_hovertank_turn_joy "1"
seta in_hovertank_turn_axis "4"
seta in_hovertank_turn_power "1"
seta in_hovertank_turn_offset "0"
seta in_hovertank_turn_invert "0"
seta in_hovertank_turn_speed "140"
seta in_hovertank_turn_deadZone "0.2"

seta in_hovertank_forward_joy "1"
seta in_hovertank_forward_axis "3"
seta in_hovertank_forward_power "1"
seta in_hovertank_forward_offset "0"
seta in_hovertank_forward_invert "1"
seta in_hovertank_forward_speed "140"
seta in_hovertank_forward_deadZone "0.2"


//player
seta in_player_side_joy "1"
seta in_player_side_axis "4"
seta in_player_side_power "2"
seta in_player_side_offset "0"
seta in_player_side_invert "0"
seta in_player_side_speed "160"
seta in_player_side_deadZone "0.2"

seta in_player_forward_joy "1"
seta in_player_forward_axis "3"
seta in_player_forward_power "2"
seta in_player_forward_offset "0"
seta in_player_forward_invert "1"
seta in_player_forward_speed "160"
seta in_player_forward_deadZone "0.2"

seta in_player_yaw_joy "1"
seta in_player_yaw_axis "1"
seta in_player_yaw_power "0.4"
seta in_player_yaw_offset "0"
seta in_player_yaw_invert "1"
seta in_player_yaw_speed "100"
seta in_player_yaw_deadZone "0.2"

seta in_player_pitch_joy "1"
seta in_player_pitch_axis "0"
seta in_player_pitch_power "0.4"
seta in_player_pitch_offset "0"
seta in_player_pitch_invert "1"
seta in_player_pitch_speed "100"
seta in_player_pitch_deadZone "0.2"



thanks to all here!

[Downtown1]

Hello,

I was trying to use the X360 configuration for my controller. I can fly around and use both my analog sticks, but it doesn't seem like any of the other buttons work (especially the fire button which definitely doesn't work).

What am I doing wrong? I have a wired controller btw.

[DireFog]

I played with the settings for my Sidewinder FF2, and the main axes don't work (as expected). However, setting
- inverted axis 1 as throttle and
- non-inverted axis 0 to yaw
gives nice controls for collective and rotation. Now if there was a proper driver for the stick that allowed using it as a pure analog stick with spring force... :( Using a combination of stick and mouse (don't ask) hints at a beautiful experience.

[FlyingSquirrel]

I must have inadvertently overwritten something, but after perusing some config files, can't seem to find what it is.

If I use the "force mouselook" key and hold it down, it works, but it won't stay in mouse look mode to move my turret or let me steer jetpacks anymore.

Can't swing the gun around with my mouse w/o pressing a button. Bah - any ideas?

[Temragon]

I've read a few of you are using the 360 controller for controls successfully, could you please post your configs, and what drivers you're using?

[PHA-Scorpion]

Hi...
I just have one problem left with configuring my Logitech Freedom 2.4..

Was wondering..is it possible to Bind the Pitch movement to a joystick key ??

IE ..
seta in_heli_side_axis" "1"
seta in_heli_side_joy" "1"

would this be the comand line ??..
bind "joy1_3" "in_heli_side_joy" "1"
bind "joy1_4" "in_heli_side_joy" "1"

Your help in this is greatly appreciated

[DocSnyper]

i am using a saitek impact controller and while the right analog stick is working with FWD/BAck on the vertical axis and strafe left/strafe right on the horizontal axis - the axis on the left stick are mixed up left is lookdown, right lookup - up is look left and down is turn right. the butons aren´t working at all.
as i have read so far in this thread, i have to asign all axis manually. it would be much easier if somebody could tell me how they are assigned by default so i can just switch axis rather than start from the beginning.

it´s really a hassle to find out by trial and error. start a game, wait for a tormentor to spawn. get in, crash because the joypad is not working, wait for anotherone to spawn....
quit the game modify the config, fire it up again... repeat for 10 times ????
am i asking too much of a full price game if i want it to recognise my controller
and enable me to use/configure it in the game ?
having to play around with your config for two hours can´t really be considered customer friendly at id and SD.
the least would have been a little tool like the config maker (ETQW Tweaker) - poor enough that this tool had to be provided by the community.
i was expecting more.

p.s. got the buttons working now.

[videodrone83]

anyone got a vehicle/flying config for the regular keyboard. i dont know the advanced fly binds

[videodrone83]

anyone got a working config for the xbox360 controller?

[r00b]

help

When I type listControllers in the console it says Unknown command 'listControllers'.

[Pozo]

help

When I type listControllers in the console it says Unknown command 'listControllers'.Use 'small letters', ie
listcontrollers

I'm also haveing the same trouble with my Logitech Rumblepad 2, no left stick but it does control the mouse in menus :( It just won't work. I'm thinking of using the dpad for up/down and yaw controls as those can be set trough the wasd keys.

[DocSnyper]

this forum has a search function - use it !!!!

i have started making a configuration for flying vehicles using the xbox360 controller on the pc. if someone wants to try out, here it is:

/* ====================== */
/* xbox360 controller */
/* ====================== */
// ----------------
// d-pad:
// ----------------
// up: enter vehicle/switch seats
bind "joy1_DPAD_UP" "_activate" "" "vehicle"
bind "joy1_DPAD_UP" "_usevehicle" "" "default"
// down: leave vehicle/parachute
bind "joy1_DPAD_DOWN" "_usevehicle" "" "vehicle"
bind "joy1_DPAD_DOWN" "_activate" "" "default"
// left: select rockets
bind "joy1_DPAD_LEFT" "_weapon1" "" "vehicle"
// right: select LAW etc
bind "joy1_DPAD_RIGHT" "_weapon2" "" "vehicle"
// ----------------
// buttons:
// ----------------
// right analog trigger: thrust forward
bind "joy1_RIGHT_TRIGGER" "_sprint" "" "vehicle"
// top right button: thrust backwards
bind "joy1_6" "_speed" "" "vehicle"
// left analog trigger: fire weapon
bind "joy1_LEFT_TRIGGER" "_attack" "" "vehicle"
// top left button: switch weapon
bind "joy1_5" "_weapnext" "" "vehicle"
// A button: fire decoy
bind "joy1_1" "_weapon0" "" "vehicle"
// B button: select rockets
bind "joy1_2" "_weapon2" "" "vehicle"
// X: vehicle camera
bind "joy1_3" "_vehiclecamera" "" "vehicle"
// Y button: select missile
bind "joy1_4" "_weapon1" "" "vehicle"

just put the above into your autoexec.cfg file.

feel free to extend it and share what you've created :)

[Smiley]

I'm also haveing the same trouble with my Logitech Rumblepad 2, no left stick but it does control the mouse in menus :( It just won't work. I'm thinking of using the dpad for up/down and yaw controls as those can be set trough the wasd keys.

Hmm, i had the same when i connected my Rumblepad (first version) the first time - did you try to change the axis-bindings? Changing them worked fine for me. Btw. i dont have the Logitech drivers installed - just the common windows driver ;)

have a look at my config (if not already done ;)
http://community.enemyterritory.com/forums/showpost.php?p=159135&postcount=118

//Logitech WingMan Cordless Rumblepad
//axis0 = right stick up/down
//axis1 = right stick left/right
//axis2 = throttle
//axis3 = left stick up/down
//axis4 = left stick left/right
//bindable keys:
//joy1_DPAD_UP, joy1_DPAD_DOWN, joy1_DPAD_LEFT, joy1_DPAD_RIGHT
//joy1_1 - joy1_11

[Pozo]

@ Smiley,
Thanks, didn't think of that yet. I'm using Vista and I think I recall the pad wouldn't work with M$ drivers, but I'll try tomorrow. Like I said, I've now mapped the DPAD to the wasd functions, but it's not ideal.

[Smiley]

The best way is to open the console and play around with those values - oh, and i´m using vista, too. The Rumblepad works like a charm! :)

[Shagbag]

So... there's still no way to map axes for FF joysticks (not for FF, just for control)?

There goes my acing dream... I'm officially pissed. :mad:

[PHA-Scorpion]

With regards to a Logitech Freedom Cordless 2.4 Joystick - Here is my CFG

// Joystick - Logitech Freedom 2.4 Cordless
seta in_joy1_device "349207"


// These keep the JoyStick from controllering the Player.
seta in_player_yaw_joy 0
seta in_player_pitch_joy 0
seta in_player_forward_joy 0
seta in_player_side_joy 0


// Pitch Left - Right
seta in_heli_side_power "1" "" "flyers"
seta in_heli_side_offset "0" "" "flyers"
seta in_heli_side_invert "1" "" "flyers"
seta in_heli_side_speed "75" "" "flyers"
seta in_heli_side_deadZone "0.2" "" "flyers"
seta in_heli_side_axis "1" "" "flyers"
seta in_heli_side_joy "1" "" "flyers"

// Pitch Forward - Back
seta in_heli_forward_power "1" "" "flyers"
seta in_heli_forward_offset "0" "" "flyers"
seta in_heli_forward_invert "1" "" "flyers"
seta in_heli_forward_speed "40" "" "flyers"
seta in_heli_forward_deadZone "0.2" "" "flyers"
seta in_heli_forward_axis "0" "" "flyers"
seta in_heli_forward_joy "1" "" "flyers"

// Rudder
seta in_heli_yaw_power "1" "" "flyers"
seta in_heli_yaw_offset "0" "" "flyers"
seta in_heli_yaw_invert "0" "" "flyers"
seta in_heli_yaw_speed "140" "" "flyers"
seta in_heli_yaw_deadZone "0.2" "" "flyers"
seta in_heli_yaw_axis "3" "" "flyers"
seta in_heli_yaw_joy "1" "" "flyers"

// Throttle (for up & down)
seta in_heli_throttle_power "1" "" "flyers"
seta in_heli_throttle_offset "0" "" "flyers"
seta in_heli_throttle_invert "1" "" "flyers"
seta in_heli_throttle_speed "200" "" "flyers"
seta in_heli_throttle_deadZone "0.2" "" "flyers"
seta in_heli_throttle_axis "2" "" "flyers"
seta in_heli_throttle_joy "1" "" "flyers"

// Joybuttons
bind "joy1_1" "_attack" "" "flyers"
bind "joy1_2" "_weapnext" "" "flyers"
bind "joy1_7" "_sprint" "" "flyers"
bind "joy1_8" "_weapon0" "" "flyers"
bind "joy1_5" "clientquickchat quickchat/enemy/infantryspotted" "" "flyers"
bind "joy1_6" "clientquickchat quickchat/enemy/vehiclespotted" "" "flyers"

Hope this helps those out there :
Only question i ask about this cfg is, If those out there know if its possible to bind the pitch left/right to a joystick button rather than an axis movement plz post it here for me plz..

[c4ppy]

I need a cfg for a Trust Predator joystick, i,m not much of a programmer..sorry :)

Why not the same options like BF 2? ingame setup, so we ALL can use a joystick and not alome the ppl who can make own cfg,s.

[Jazkal]

anyone got a working config for the xbox360 controller?

Yes, if you have a 360 controller, please post your config setup.

(and for those people who feel the need to post the first post from this thread, and tell us to use the search, go elsewhere and bother someone else, please.) I have done searches, but have not seen a xbox 360 controller config that wasn't posted way back in the early beta (like the first post).

I'm looking for a config that will work well for Fliers and Tanks.

[Downtown1]

Here is my tweaked xbox 360 controller configuration.


/* ====================== */
/* xbox360 controller */
/* ====================== */
// ----------------
// d-pad:
// ----------------
// up: enter vehicle/switch seats
bind "joy1_DPAD_UP" "_activate" "" "vehicle"
bind "joy1_DPAD_UP" "_usevehicle" "" "default"
// down: leave vehicle/parachute
bind "joy1_DPAD_DOWN" "_usevehicle" "" "vehicle"
bind "joy1_DPAD_DOWN" "_activate" "" "default"
// left: select rockets
bind "joy1_DPAD_LEFT" "_weapon1" "" "vehicle"
// right: select LAW etc
bind "joy1_DPAD_RIGHT" "_weapon2" "" "vehicle"
// ----------------
// buttons:
// ----------------
// left analog trigger: thrust forward
bind "joy1_LEFT_TRIGGER" "_sprint" "" "vehicle"
// top left button: thrust backwards
bind "joy1_5" "_speed" "" "vehicle"
// right analog trigger: fire weapon
bind "joy1_RIGHT_TRIGGER" "_attack" "" "vehicle"
// top right button: switch weapon
bind "joy1_6" "_weapnext" "" "vehicle"
// A button: fire decoy
bind "joy1_1" "_weapon0" "" "vehicle"
// B button: select rockets
bind "joy1_2" "_weapon2" "" "vehicle"
// X: vehicle camera
bind "joy1_3" "_vehiclecamera" "" "vehicle"
// Y button: select missile
bind "joy1_4" "_weapon1" "" "vehicle"
// ----------------
// axis manipulations:
// ----------------
// use left analog stick to tilt (yaw)
in_heli_yaw_axis 2
// use right analog stick to turn (side)
in_heli_side_axis 0

Save into
My Documents\id Software\Enemy Territory - QUAKE Wars\sdnet\<<player_name>>\base\autoexec.cfg file

Essentially it is the same as the OP config, except that I am using the left analog stick to tilt (yaw), and the right analog stick to turn (side) instead of the other way around. This makes aiming using the right analog stick a little easier.

Unfortunately I still do not like this configuration. Using the an analog stick as a throttle is very annoying, it means the moment you let go you will stop, if you push too hard you will go past, etc. (For flying)

If anyone has played around with it, and has figured out a better solution of mapping the axis (or if they are unsure how to do the binding themselves but have a good idea) please post here.

Also note that I am completely uninterested in using the 360 controller for anything but flying, the mouse&keyboard is far superior in everything else.

I have a Wingman Force Feedback 3d joystick that I just brought up from home a week ago, I'll post the configuration for that once I have time to play around with it.

[belegdol]

The listControllers command does not seem to exist in Linux client. Is it different, or are joysticks unavailable for linux users at all? Cheers.

[Lunarbunny]

The listControllers command does not seem to exist in Linux client. Is it different, or are joysticks unavailable for linux users at all? Cheers.

Same question. Are we stuck without any sort of joystick support in Linux?

EDIT: Nevermind, found the answer in the FAQs. No joystick support for Linux yet.

[FischCommand]

has anyone a config for my USB Gamepad. It's a Gamepad from Foxconn.
The game pad was at my graphics card with it ;)

http://www.elitebastards.com/hanners/foxconn/7900gs/images/gamepad_tn.jpg

The racing game "Flatout2" works great with it

[NESv1]

Can someone just tell me what to type in the console to get my right analogue stick to be reversed? It's inverted right now, and I hate it.

[Judaszeuger]

Hi form Germany,

I hope you will welcome my first question!
This Xbox-Controller doesn't work in QW.
What am I doing wrong?
I found out the controller-id like 'seta in_joy1_device "541957" '.
After this I tried by copying and pasting all the nice configs show in this thread into my autoexec.
Unfortunately nothing works but the buttons, especially the two analog sticks and triggers -one of them is doing well in the menu- show no functionality.
Please help!

Regards
Judaszeuger

[urdead]

Is there a hover state in the aircraft so we can aim the rockets/strockets/law...etc with a d-pad on the Joystick?

[problem_causer]

Fearog-

Thank you for taking the time to create this work-around document. It would be more helpful to newbs like me and many others if certain steps didn't assume Quake-experience in modifying cvars. In original ET, tilde called down the console. In ET:QW, I don't know how to get the console. Also, can't figure out how to set up 'windowed mode'.


Without further ado, here is a guide I wrote some time ago on the topic:


Bring down the console, type listControllers


..........

I generally set mine up in windowed mode, configuring it & tweaking it in a .cfg file so that my settings are all saved and easy to read & retrieve.


I hope this helps! :)

Thanks again for working to make a great game. Let's make it better.

Appreciatively,

Problem Causer

[reyalp]

Fearog-

Thank you for taking the time to create this work-around document. It would be more helpful to newbs like me and many others if certain steps didn't assume Quake-experience in modifying cvars. In original ET, tilde called down the console.
http://community.enemyterritory.com/forums/showthread.php?t=9160

[ThunderFlash]

Hmmmmm...just been trolling thru this thread and its a shame that the players now have to write fixes so they can get the game to work with their chosen controllers, do ET:QW actually have programmers that can fix these joystick issues or will the game remain as is?

Come on devs, pull yer fingers out and give us joystick config options ingame please

Not all of us are whizz kids at creating cfg files and programming, it would be nice if the ET:QW programmers would make joystick config part of the settings so we can set-up our joystick ingame without any hassle, surely that's not too much to ask huh?

Oh and while we're on the subject of people writing cfg files, Will any changes made be deemed as an advantage and/or hacking the game as it gives players an advantage over players using standard set-ups as intended by ET:QW?

Surely if files can be adjusted then settings can be changed also to give players advantages which can only lead to cheaters and hackers

[reyalp]

Not all of us are whizz kids at creating cfg files and programming

settings cvars in a cfg file isn't programming. Anyone with a grade-school level education should be able to do it if they are willing to invest a small amount of time reading.

The idea that the existence of cvars will lead to "cheaters and hackers" is nonsense. The cvars that are unlocked are the ones they intended you to be able to change. Any exploitable ones found later can be restricted with PB.

[archemedes]

settings cvars in a cfg file isn't programming. Anyone with a grade-school level education should be able to do it if they are willing to invest a small amount of time reading.


the thing is consumers should not have to do this (and changing files is technically programming) if it was a console game, and you had to do the same thing the game would not sell, why should pc users be at a lower standard

[Scottso]

Umm.. sticky vote for this one..

[D0pamine]

Same question. Are we stuck without any sort of joystick support in Linux?

EDIT: Nevermind, found the answer in the FAQs. No joystick support for Linux yet.

sonofa... i've been reading this whole thread too :S

EDIT: i'm going to try and use

app-misc/joymouse

and

app-misc/joy2key

it wouldnt be very elegant but its a start

[Pigpen]

Since, u have managed to get it working, please post ur config file. Thanks in advance!

Here's my config for my PS2 pad connected with a Rockfire converter doodad. I've left some comments in there that might be helpful regarding button bindings and joystick axis. I mostly just cut and paste bits from this thread, it looks a bit messy but it works.


// INIT
seta in_joy1_device "404552"
//
// DPAD CONTROLS
//
// up: enter vehicle/switch seats
bind "joy1_DPAD_UP" "_activate" "" "vehicle"
bind "joy1_DPAD_UP" "_usevehicle" "" "default"
// down: leave vehicle/parachute
bind "joy1_DPAD_DOWN" "_usevehicle" "" "vehicle"
bind "joy1_DPAD_DOWN" "_activate" "" "default"
// left: select rockets
bind "joy1_DPAD_LEFT" "_weapon1" "" "vehicle"
// right: select LAW etc
bind "joy1_DPAD_RIGHT" "_weapon2" "" "vehicle"
//
// BUTTONS CONTROLS
//
// -----------
// Buttons Key
//
// X = 1
// O = 2
// Sq = 3
// Tr = 4
// L1 = 5
// R1 = 6
// L2 = 7
// R2 = 8
// L3 = 9
// R3 = 10
// Select = 11
// Start = 12
// ------------
//
// R1 : Fire weapon
bind "joy1_6" "_attack" "" "vehicle"
// R2 : Thrust forward
bind "joy1_8" "_sprint" "" "vehicle"
// L2 : Thrust backwards
bind "joy1_7" "_speed" "" "vehicle"
// Triangle : switch weapon
bind "joy1_4" "_weapnext" "" "vehicle"
// L1 : Decoys
bind "joy1_5" "_weapon0" "" "vehicle"
//
// CONTROL SURFACES
//
// ------------------
// Joystick Axis Key
// ------------------
//
//axis 0 = right stick up/down
//axis 1 = right stick left/right
//axis 2 = left stick up/down
//axis 3 = left stick left/right
// ------------------
//
// - rudder
seta in_heli_side_power "1"
seta in_heli_side_offset "0"
seta in_heli_side_invert "1"
seta in_heli_side_speed "140"
seta in_heli_side_deadZone "0.2"
seta in_heli_side_axis "3"
seta in_heli_side_joy "1"
// - pitch
seta in_heli_forward_power "1"
seta in_heli_forward_offset "0"
seta in_heli_forward_invert "0"
seta in_heli_forward_speed "140"
seta in_heli_forward_deadZone "0.2"
seta in_heli_forward_axis "2"
seta in_heli_forward_joy "1"
// - roll
seta in_heli_yaw_power "1"
seta in_heli_yaw_offset "0"
seta in_heli_yaw_invert "0"
seta in_heli_yaw_speed "100"
seta in_heli_yaw_deadZone "0.2"
seta in_heli_yaw_axis "1`"
seta in_heli_yaw_joy "1"
// - cyclic
seta in_heli_throttle_power "1"
seta in_heli_throttle_offset "0"
seta in_heli_throttle_invert "1"
seta in_heli_throttle_speed "140"
seta in_heli_throttle_deadZone "0.2"
seta in_heli_throttle_axis "0"
seta in_heli_throttle_joy "1"

Its difficult to coordinate the controls at first, I find myself spinning in circles or rolling over upside-down quite a lot but its just practice. I might re-bind the R2 and L2 buttons to rudder at a later date, it might make things easier to control.

[PuP]

VMax's config for the Logitech Wingman Digital 3D worked fairly well as a starting point for my Logitech Extreme 3D Pro (X3D). But I'm having trouble with roll control. The relavent cvars chunk is:

//aileron
seta in_heli_yaw_power "1"
seta in_heli_yaw_offset "0"
seta in_heli_yaw_invert "0"
seta in_heli_yaw_speed "140"
seta in_heli_yaw_deadZone "0.2"
seta in_heli_yaw_axis "2"
seta in_heli_yaw_joy "1"

Trouble is that it just doesn't seem to work. I move my joystick side to side and no response. I swapped out the axis for the rudder with 'seta in_heli_side_axis "2"', and i could control turning by moving the stick side to side... so i know it's not my joystick.

anyone have any ideas? FeaRog's example use this syntax exactly several times (e.g. in_heli_yaw_axis), so i don't think it's a simple typo.... but i just don't have roll control. one thing i just thought of, i've been flying on the anansi... it does have roll control doesn't it?

[peoples]

...The whole point of peoples post is that the wheel is causing the mouse to move in the menus...the same thing will happen to a joystick that is not centered. It basically prevents him from selecting anything from the menus i.e. selecting online game, selecting a server, and clicking join because the wheel is turned and is moving the cursor to the edge of the screen...

Correct, but it is centered, and properly configured. The only problem is that it takes over mouse in menus. I though this would be fixed after these months, I finally got the game, but seems it is not fixed.

[TOG.Requiem]

so from what I've read Force Feedback joysticks don't work?

Has anyone got a FF joystick to work or is it just non-FF sticks that work?

[reyalp]

so from what I've read Force Feedback joysticks don't work?

Has anyone got a FF joystick to work or is it just non-FF sticks that work?
They won't have force feedback, but they should still work.

[kombat03]

has anyone got a working hotas cougar config yet? I tried to set one up but I can not get it to work exactly like how the mouse works, it can turn left right or roll but not do both.

Kombat03

[MetalDream]

HI All

using the Logitech Force 3D PRO

The Listcontrolers cmd put up this number "404545"

and using some cfg´s tha are on this thread only got the thrust and yaw axis
to work.

here are the binds


//joy stuff - - - TEST

seta in_joy1_device "404545"

//rudder
seta in_heli_side_power "1"
seta in_heli_side_offset "0"
seta in_heli_side_invert "1"
seta in_heli_side_speed "140"
seta in_heli_side_deadZone "0.2"
seta in_heli_side_axis "2"
seta in_heli_side_joy "1"

//elevator
seta in_heli_forward_power "1"
seta in_heli_forward_offset "0"
seta in_heli_forward_invert "0"
seta in_heli_forward_speed "140"
seta in_heli_forward_deadZone "0.2"
seta in_heli_forward_axis "3"
seta in_heli_forward_joy "1"

//aileron
seta in_heli_yaw_power "4"
seta in_heli_yaw_offset "1"
seta in_heli_yaw_invert "0"
seta in_heli_yaw_speed "140"
seta in_heli_yaw_deadZone "0.2"
seta in_heli_yaw_axis "0"
seta in_heli_yaw_joy "1"
//Correcto

//blade pitch (for up & down)
seta in_heli_throttle_power "1"
seta in_heli_throttle_offset "0"
seta in_heli_throttle_invert "1"
seta in_heli_throttle_speed "140"
seta in_heli_throttle_deadZone "0.2"
seta in_heli_throttle_axis "1"
seta in_heli_throttle_joy "1"
//CORRECTO

Well one more FF joy not working on all the axis

[Ranthalion75]

Here's what I've got in my autoexec.cfg, and only rudder and throttle work. I use a Logitech Wingman Force 3D and it's ID in QW is 469349

in_joy1_device "469349"
in_player_side_joy "0"
in_player_forward_joy "0"
in_player_yaw_joy "0"
in_player_pitch_joy "0"
in_car_side_joy "0"
in_car_forward_joy "0"
in_car_yaw_joy "0"
in_car_pitch_joy "0"
in_hovertank_side_joy "0"
in_hovertank_forward_joy "0"
in_hovertank_yaw_joy "0"
in_hovertank_pitch_joy "0"
in_heli_side_joy "1"
in_heli_forward_joy "1"
in_heli_yaw_joy "1"
in_heli_pitch_joy "2"
in_heli_throttle_axis "1"
in_heli_forward_axis "3" <-- NOT WORKING
in_heli_side_axis "2" <-- NOT WORKING
in_heli_yaw_axis "0"


I've changed these non-working axes to quite a few numbers, but no response. :-(

[shim]

sorry to bump such a old topic, but is there a way to bind heli pitch and straife to axises?

[BioSnark]

yeah, that.

is there anyway to assign turn-left/right to mouse X and pitch axi to mouse Y? please help!

It is not currently possible, sorry.

:( hopefully in beta 2 or even afterwards :infiltrator:

Any word on if it's possible now? (that is, almost a year later) Only other thing I can find are unanswered posts on it :confused:

[stfulton]

I have a logitech precision controller, and i was wondering if there was anyway i could set some of the buttons to act as a mouse, like to change the camera view, like on xbox 360, Call of duty, you use the sticks to look around...I was wondering if i could make my controller do this.

[Nigel]

I have a Saitek AV8R and none of the axes work at all.

Well, that's mostly true. At one point, while trying to disable the axes to start fresh, I got some response when yaw was set to axis 155, but it only worked if I twisted left, and not right. Otherwise, the buttons work, but there is no axis action at all.

I read earlier that there was some other, undisclosed reason that controller axes didn't work. Does anyone know anything about this, or is it really as undisclosed as I surmised?

[Tangles]

I also have a Saitek AV8R joystick and I'm having difficulties getting any of the axes to map correctly. I can bind any of the joysticks buttons without problem, but I've tried every combination of axis settings and I'm not getting ANY responses.

I've created a blank config file in my base directory called joystick.cfg that looks like this
seta in_joy1_device "422522"

seta in_pitchspeed "140"
seta in_yawspeed "140"

bind joy1_1 "_attack"
bind joy1_4 "_weapon0"
bind joy1_2 "_usevehicle"
bind joy1_3 "_weapnext"
bind joy1_5 ""
bind joy1_6 "_speed"

seta in_heli_side_power "1"
seta in_heli_side_offset "0"
seta in_heli_side_invert "1"
seta in_heli_side_speed "140"
seta in_heli_side_deadZone "0.2"
//seta in_heli_side_axis "2"
seta in_heli_side_joy "1"

seta in_heli_forward_power "1"
seta in_heli_forward_offset "0"
seta in_heli_forward_invert "0"
seta in_heli_forward_speed "140"
seta in_heli_forward_deadZone "0.2"
//seta in_heli_forward_axis "3"
seta in_heli_forward_joy "1"

seta in_heli_yaw_power "1"
seta in_heli_yaw_offset "0"
seta in_heli_yaw_invert "0"
seta in_heli_yaw_speed "140"
seta in_heli_yaw_deadZone "0.2"
seta in_heli_yaw_axis "7"
seta in_heli_yaw_joy "1"

seta in_heli_throttle_power "1"
seta in_heli_throttle_offset "0"
seta in_heli_throttle_invert "1"
seta in_heli_throttle_speed "140"
seta in_heli_throttle_deadZone "0.2"
//seta in_heli_throttle_axis "0"
seta in_heli_throttle_joy "1"


as you can see, i've commented out all the axes lines except for the seta in_heli_yaw_axis line so I could test without mapping the same axis to multiple functions.

I've tried changing the heli_yaw_axis line from 0 to 7, saving each time and switching back over to the windowed mode game and re-execing joystick.cfg but I don't get any responses when I'm hovering in the Anansi. All the buttons work fine. I've tried 0-7 with the power axis also and I can't get any thrusting to happen either.

I understand that joystick "ahem" support is not supported, but I'm just wondering if anyone out there with a similar setup got it to work a different way than how I'm approaching this.

[Keto]

I have a Saitek AV8R and none of the axes work at all.

I also have a Saitek AV8R joystick and I'm having difficulties getting any of the axis to map correctly.

I have a Logitech Cyberman II, and have the exact same problem you Saitek AV8R guys are having. I can bind the buttons no problem, but none of the axis's respond in game.

Whats really weird, is that the basic X and Y axis's will move the cursor in the pre-game menu screen. Have you guys noticed that with yours?

Like you, the controller works fine in everything else.

[stan.distortion]

Hiya. Problem with an MS sidewinder Dual Strike, both axis work and all the buttons (linux btw). The hatswitch (digital) is always a pain on this thing, in some games it shows up as buttons, others as 2 axis and again some others as a hat.
seta in_showJoy "1" in autoexec.cfg is giving me debug info for all buttons and axis but the only thing I'm getting for the hat is "SDL_JOYHATMOTION" for all movements. DPAD input had no effect, I'll have a look at joy2key later but this hat is a pain in the...neck and I couldnt get it working with joy2key in the past. Any ideas?

EDIT: tried qjoypad (linux) to set up the hat and it's working ok, qjoypad "just worked"(tm) with no messing around but there is a bit of lag from time to time so would still like to get it working in autoexec.cfg
cheers

[NixNix]

seta in_showJoy "1" in autoexec.cfg is giving me debug info for all buttons and axis


How do you get this debug information? I can not see anything, at least not in the console.

[stlava]

Might help..

// ETQW 360 controller config
// zombiecon_360.cfg

// ================================================== ==================


// Devices - these are XInput 360 controllers 1->4
seta in_joy1_device "232429"
seta in_joy2_device "232566"
seta in_joy3_device "232703"
seta in_joy4_device "232840"

// Xbox 360 controller button setup
bind "JOY_1" "_reload" // A
bind "JOY_2" "_weapnext" // B
bind "JOY_3" "_weapprev" // X
bind "JOY_4" "_usevehicle" // Y
bind "JOY_5" "_moveup" // Left shoulder pad
bind "JOY_6" "_activate" // Right shoulder pad
bind "JOY_7" "_prone" // Left stick press
bind "JOY_8" "_altattack" // Right stick press
bind "JOY_LEFT_TRIGGER" "_movedown"
bind "JOY_RIGHT_TRIGGER" "_attack"
bind "JOY_DPAD_LEFT" "_leanleft"
bind "JOY_DPAD_RIGHT" "_leanright"
bind "JOY_DPAD_UP" "_vehicleCamera"
bind "JOY_DPAD_DOWN" "_commandmap"


// Hovertank
seta in_hovertank_side_power "1"
seta in_hovertank_side_offset "0"
seta in_hovertank_side_invert "0"
seta in_hovertank_side_speed "140"
seta in_hovertank_side_deadZone "0.2"
seta in_hovertank_side_axis "-1"
seta in_hovertank_side_device "232429"
seta in_hovertank_yaw_power "4"
seta in_hovertank_yaw_offset "0"
seta in_hovertank_yaw_invert "1"
seta in_hovertank_yaw_speed "230"
seta in_hovertank_yaw_deadZone "0.2"
seta in_hovertank_yaw_axis "2"
seta in_hovertank_yaw_device "232429"
seta in_hovertank_pitch_power "4"
seta in_hovertank_pitch_offset "0"
seta in_hovertank_pitch_invert "1"
seta in_hovertank_pitch_speed "230"
seta in_hovertank_pitch_deadZone "0.2"
seta in_hovertank_pitch_axis "3"
seta in_hovertank_pitch_device "232429"
seta in_hovertank_turn_power "1"
seta in_hovertank_turn_offset "0"
seta in_hovertank_turn_invert "0"
seta in_hovertank_turn_speed "140"
seta in_hovertank_turn_deadZone "0.2"
seta in_hovertank_turn_axis "0"
seta in_hovertank_turn_device "232429"
seta in_hovertank_forward_power "1"
seta in_hovertank_forward_offset "0"
seta in_hovertank_forward_invert "1"
seta in_hovertank_forward_speed "140"
seta in_hovertank_forward_deadZone "0.2"
seta in_hovertank_forward_axis "1"
seta in_hovertank_forward_device "232429"

// Helicopter
seta in_heli_side_power "1"
seta in_heli_side_offset "0"
seta in_heli_side_invert "1"
seta in_heli_side_speed "140"
seta in_heli_side_deadZone "0.2"
seta in_heli_side_axis "2"
seta in_heli_side_device "232429"
seta in_heli_forward_power "1"
seta in_heli_forward_offset "0"
seta in_heli_forward_invert "0"
seta in_heli_forward_speed "140"
seta in_heli_forward_deadZone "0.2"
seta in_heli_forward_axis "3"
seta in_heli_forward_device "232429"
seta in_heli_yaw_power "1"
seta in_heli_yaw_offset "0"
seta in_heli_yaw_invert "0"
seta in_heli_yaw_speed "140"
seta in_heli_yaw_deadZone "0.2"
seta in_heli_yaw_axis "0"
seta in_heli_yaw_device "232429"
seta in_heli_throttle_power "1"
seta in_heli_throttle_offset "0"
seta in_heli_throttle_invert "1"
seta in_heli_throttle_speed "140"
seta in_heli_throttle_deadZone "0.2"
seta in_heli_throttle_axis "1"
seta in_heli_throttle_device "232429"

// Car
seta in_car_yaw_power "4"
seta in_car_yaw_offset "0"
seta in_car_yaw_invert "1"
seta in_car_yaw_speed "230"
seta in_car_yaw_deadZone "0.2"
seta in_car_yaw_axis "2"
seta in_car_yaw_device "232429"
seta in_car_pitch_power "4"
seta in_car_pitch_offset "0"
seta in_car_pitch_invert "0"
seta in_car_pitch_speed "230"
seta in_car_pitch_deadZone "0.2"
seta in_car_pitch_axis "3"
seta in_car_pitch_device "232429"
seta in_car_steering_power "1"
seta in_car_steering_offset "0"
seta in_car_steering_invert "0"
seta in_car_steering_speed "140"
seta in_car_steering_deadZone "0.2"
seta in_car_steering_axis "0"
seta in_car_steering_device "232429"
seta in_car_throttle_power "1"
seta in_car_throttle_offset "0"
seta in_car_throttle_invert "1"
seta in_car_throttle_speed "140"
seta in_car_throttle_deadZone "0.2"
seta in_car_throttle_axis "1"
seta in_car_throttle_device "232429"

// Player/Walker
seta in_player_side_power "1"
seta in_player_side`_offset "0"
seta in_player_side_invert "0"
seta in_player_side_speed "140"
seta in_player_side_deadZone "0.2"
seta in_player_side_axis "0"
seta in_player_side_device "232429"
seta in_player_forward_power "1"
seta in_player_forward_offset "0"
seta in_player_forward_invert "1"
seta in_player_forward_speed "140"
seta in_player_forward_deadZone "0.2"
seta in_player_forward_axis "1"
seta in_player_forward_device "232429"
seta in_player_yaw_power "4"
seta in_player_yaw_offset "0"
seta in_player_yaw_invert "1"
seta in_player_yaw_speed "230"
seta in_player_yaw_deadZone "0.2"
seta in_player_yaw_axis "2"
seta in_player_yaw_device "232429"
seta in_player_pitch_power "4"
seta in_player_pitch_offset "0"
seta in_player_pitch_invert "0"
seta in_player_pitch_speed "230"
seta in_player_pitch_deadZone "0.2"
seta in_player_pitch_axis "3"
seta in_player_pitch_device "232429"

// ================================================== ==================
//
// CONTROLLER INPUT GUIDE
//
// Each controller device has a unique hash value identifying it.
// Use the "listControllers" command to display a list of currently
// connected controllers and their unique hashes. There are 4 joystick
// slots available for binding, and you set the controller associated
// with each using the cvars in_joy1_device through in_joy4_device.
//
//
//
//
// BUTTON BINDING
//
// The buttons of a controller are bound as follows:
//
// bind joy<number>_<button> [command]
//
// where <number> is the slot number for the controller, and <button>
// is between 1 & 32, or one of the following:
//
// DPAD_UP
// DPAD_DOWN
// DPAD_LEFT
// DPAD_RIGHT
// LEFT_TRIGGER
// RIGHT_TRIGGER
//
// eg: You want to bind the right trigger of the first joystick
//
// bind JOY1_RIGHT_TRIGGER _attack
//
//
// AXIS ASSIGNMENT AND ADJUSTMENT
//
// There are several different input modes, at the moment these are
// player, car, heli, and hovertank. Each input mode has a number of
// axes defined - each is fully configurable. The parameters to tune
// are:
//
// joy - Joystick number (1-4) used to control this axis
// axis - The axis of the controller that provides the input (0-7)
// Note that the axis numbers vary between different
// devices.
// invert - Reverses the axis
// deadZone - The threshold of controller input. Eg, if dead zone is
// 0.2, you have to move your controller past the 20% point
// before it starts to affect the game
// offset - The value of the controller when it first passes the
// dead zone. Eg 0.2 deadzone with 0.1 offset: When the
// controller is at 20% the input value will be 0.1 (10%),
// and will increase from there
// power - The input value is raised to the power of this number,
// to allow acceleration. By default, the player input uses
// a power of 4 for aiming, providing the ability to finely
// aim using small inputs, but turn fast by moving the
// stick to its limits. One gives a linear response.
// speed - The scale factor used once the other calculations are
// complete. The maximum value the other calculations will
// reach is 1.0, so the speed is equal to the maximum value
// that is fed into the game.
//
// The CVars used to control these settings are of the form:
//
// in_<mode>_<axis>_<parameter>
// eg: in_player_yaw_axis
//
// The default values for these cvars have been set up for the first
// Xbox 360 controller, and if you lose your config they will reset to
// this state.
//

[NixNix]

Hmmm...

The configuration in the post above looks very different from the other that I have found on the net, but it was at least worth to test this.

Sorry, it didn't help. Tested this also for the device id code that was given for me by the listcontrollers command.

Anyway, the cvar in_heli_side_device and the other simmilar cvars can be defined but seems not to be used at all by the game. I google for these cvars and didn't find them in any cvar list.

For the bind commands above, the game say it is an invalid key.

[Nail]

afaik, that's been mentioned as being very old (06)and it's only for 360 controllers, although "Smooth" says his version works the best for the 360 controller

[charlielynch]

hey man um my controller is inverted (360 controller) how do i make it not inverted?

[Nagromme]

I use a PS2-style Rumblepad 2 with Quake Wars (Mac) and I love it. No more finger agony! I barely touch the keyboard.

(I do aim with my mouse of course. Don't get me started on "precision" gamepad aiming. So my left hand holds the gamepad and that's quite comfortable--I just don't use the right side of the pad much.)

My W and spacebar fingers used to KILL before I set up my gamepad.

[Malik22]

Anyone with a cyborg evo wireless play this game?

[deathCHILD2112]

I do not understand where you find how to set up your joystick. I have a dual action logitech(like ps2). How do I set up my joystick in easy no tech terms click by click then I probaly would understand what you are talking about???

[Stroggafier]

You do realize this is ETQW on PC, right? There is no such thing as "easy no tech terms click by click".

I have a rumblepad 2 connected. It was anything but easy.

In this thread is a sample of the autoexec.cfg I used...http://community.enemyterritory.com/forums/showthread.php?t=32004..go to the last post in the thread for the working version of my "in_player" setup.