Forums » Bugs

binding problems for the Flight yoke.

May 29, 2009 PaKettle link
When I bind the activate or flymodetoggle commands to a joybutton the command is frequently executed as well. I have no clue why but it maybe a keybounce issue. My yoke has a three position switch (JB8,9,10) that i am using to dynamicly rebind the other keys with. (jb 2,3,4,5,6,7)

Also I cannot bind Joybuttons above 10 with the menu system. They can only be done by editting the ini file

Neither are severe problems but should be looked at when time permits. It may also affect other sticks that have more then one mode like the x52.
May 29, 2009 raybondo link
Hm, interesting. Your problems are with the X52 flight yoke or some other yoke?
May 29, 2009 PaKettle link
It is happening on my Saitek Pro Flight Yoke (PZ44).

The x52 is the saitek Joystick which also has 3 modes but I dont know if it is affected by this.
May 30, 2009 davejohn link
The same is true for the x52 JS.

http://www.vendetta-online.com/x/msgboard/5/17934

Might help with editing the config.
May 31, 2009 PaKettle link
Editting the config is more an inconvieniance then anything else. Not everyone is gonna be happy doing it that way.

The keybounce issue is a bit of a problem tho as it severely limits what functions I can bind on the fly with my mode switch...

The x52 has so many buttons that no one may have actually bothered to use the mode switch to change bindings on the fly. I do know a few have done it with thier keyboard setup so i am pretty sure its a quirk of some/all joysticks.
May 31, 2009 PaKettle link
Found a referance on saiteks site that some other models with mode switches rescan the buttons whenever the mode is changed....

Tried to put a wait command in the bind but the out going bind gets triggered....
Jun 01, 2009 PaKettle link
Tried it with a normal joystick and still had the problem...

This is a copy of the current binds....

alias ModeSwitch3 "NULLO; wait .5 CargoTarget; wait .5 SpeedAdjust; echo 'C A R G O'"
alias ModeSwitch2 "NULLO; wait .5 NormTarget; wait .5 SpeedAdjust; echo 'N O R M A L' "
alias ModeSwitch1 "NULLO; wait .5 FightTarget; wait .5 FightSpeed; echo 'C O M B A T' "
alias FightTarget "Bind JOYBUTTON6 RadarNextNearestEnemy; Bind JOYBUTTON7 RadarNextFrontEnemy"
alias NormTarget "Bind JOYBUTTON6 RadarNextFront; Bind JOYBUTTON7 RadarNext"
alias CargoTarget "Bind JOYBUTTON6 RadarNextNearestPowerup; Bind JOYBUTTON7 RadarPrevNearestPowerup"
alias SpeedAdjust "Bind JOYBUTTON4 +Accelerate; Bind JOYBUTTON5 +Decelerate"
alias FightSpeed "Bind JOYBUTTON4 +Accelerate; Bind JOYBUTTON5 Flymodetoggle"
alias NULLO "Bind JOYBUTTON4 ''; Bind JOYBUTTON5 ''; Bind JOYBUTTON6 ''; Bind JOYBUTTON7 ''"
Jun 02, 2009 PaKettle link
I did find a work around for the Flight assist. I added a "set flymodeflag 1" command after the bind to force it on.

The bug does appear to affect all joysticks and appears to affect all commands as well. F/A , A/A and the activate commands are just more obvious in thier effects.

Let me know if there is any other information that might help...