Joystick support in ET:QW

(Sydney) #1

Is there any way of having joystick support for air vehicles only in ET:QW? I always missed the lack of joystick support until recently my joystick seemed to be bound with my controls ingame, that’s great, I thought at first, now I can fly with my joystick.

Problem is, it affects everything in my game, my X and Y axes on the joystick are bound to my X and Y axes on the mouse, and because my joystick is slightly unbalanced (it’s a rather old Logitech Extreme 3D Pro) my mouse will drift in the menu. Well, I went ingame, and it turns out that my soldier was looking straight up, and I couldn’t change it with my mouse, after a few seconds if thinking I lowered the throttle slider to the other side and now my soldier was looking straight down, so I had to set the throttle around the middle for my soldier to be looking forward and be controllable with the mouse.

So I jumped in a hog, and the slider was mouselook up and down, the Z axis (twist) was mouselook sideways, and the Y axis (roll) was throttle forward while X (pitch) was turning.

And yet, I couldn’t configure it otherwise in the control panel, do I have to disable my joystick for ET:QW or is there some way of confining the joystick controls to Tormentors and Ananasis only? (and configure them properly).

(murka) #2

there are a lot of commands for them, so bare to bind them.
first off, you need to set your axes to the right functions, or disable them. getting the axe number is not very complicated, you just try by trial and error, and write them down(assuming you can not remember them :P).
then bind axes(read from paper what axis nr is what movement) with commands(better to write a config and place it into C:\Documents and Settings\YourNameHere\My Documents\id Software\Enemy Territory - QUAKE Wars\base and name the file autoexec.cfg(or add it to your current autoexec, or even better, give it some name, and in the end of your autoexec write “exec yourchosenname.cfg” without quotes)
the cvars are in_“vehicle type/name/player”“function/movement”“command”
the commands 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 full list of commands that can be set for joystick is(just a copy&paste of my cfg):

[ul]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 “1”
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 “1”
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_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 “1”
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 “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 “0”
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 “1”
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 “1”
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 “1”
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_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 “1”
seta in_car_throttle_joy “1”
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_joy “0”
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_joy “0”
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_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 “3”
seta in_player_pitch_joy “0”[/ul]
a linky too http://community.enemyterritory.com/forums/showpost.php?p=55937&postcount=5

(Sydney) #3

Thanks, I’ll try it out.

Edit: How do I disable the stick from everything else than heli, just adding joy0 to them? or? (They are for some reason wrongly added)

Edit2: It didn’t work, the game wants to use the default joystick configuration which is completely wrong.

Here’s what the bottom of my autoexec looks like

seta in_joy1_device “346689”
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 “0”
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 “2”
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 “3”
seta in_heli_throttle_joy “1”

(murka) #4

it may be possible that it wont load the autoexec for some reason or you put it into the wrong dir(and i dont know for sure which one was right), so try placing it in all dirs, or in-game, write “exec autoexec.cfg”(no quotes) in console.
also dump the console to a file and check if it execed the autoexec, or you can look at the console while the game loads and you should be able to see it .
also look that there are no such commands existing that may interfere with your setup.
anyway, you can write them in console and they should work then.
and yes, joy0 is for disable.

also you should post on the official forums for help from the devs.

(Sydney) #5

seta com_allowconsole “1”
seta r_displayrefresh “100”
seta r_fullscreen “1”
seta r_mode “-1”
seta r_aspectRatio “0”
seta r_customHeight “960”
seta r_customWidth “1280”
seta com_unlockFPS “1”
seta com_unlock_timingMethod “2”
seta com_unlock_maxFPS "100
seta r_megadrawmethod 0

^The rest of my autoexec works fine, the joystick just won’t.

Oh, and I say again that my joystick is bound to the mouse, even in the menu, before I started to set it up, could there be some kind of conflict?

(murka) #6

controllers are bound to the cursor in the menu, just calibrate it and put throttle in the middle, or just unplug/replug.
strangely your joystick should be working now, are you sure you tried all values for axes for their right function? what if you change in-game, does the effect stay?

(Lighspeedkiller) #7

Murka, Sidney and whoever else that can help…

Do you know if i buy the Logitech Extreme 3D PRO Joystick and keep pluging and unpluging ONLY to fly and WHILE in game, if it will work, pls?

MANY THANKS!

(Rex) #8

[QUOTE=Lighspeedkiller;518461]Murka, Sidney and whoever else that can help…

Do you know if i buy the Logitech Extreme 3D PRO Joystick and keep pluging and unpluging ONLY to fly and WHILE in game, if it will work, pls?

MANY THANKS![/QUOTE]

Why don’t you just buy it and try? Additional grave digging won’t help much more.

(Lighspeedkiller) #9

Unfortunately, i cant afford £40 to be wasted (in case it does not work)…plus, i always thought that “Forums” are also for this kind of help/assistance/questions and answers…So, I will await a bit more “nicer” replies…