BoS bug issue with X55 HOTAS.

[AvengerSeawolf]

 Tried to take full advantage of all the modes of the X55 , so I want on and started programming  buttons.
I have inserted to each button the ky commants of the game that represent each command....So far , so good.

 

 BUT when I am in the game  any double keystroke command  will not work... SO  Lets say flaps  Flaps down = F , it will work, Flaps up = LShift+F = will not work.
 When then I am in the  keymapping of the game and try to put this through the joystic  instead of the assigned  keystrokes it only does the letter stroke , however this won't work in the game as keystroke as well ..
Example  Flaps  up = LShift+ F , if I do keymapping  putting at the same mode the same button as assigned to the programmer of the Saitek it will instead of LShift +F  write only the F , however in the game it won;t work either as only F ( flaps down.)

 Question does anyone else has this problem ??  Programming the  X55 with keystrokes from the program ??  or any other Joystick that uses programing like that ? 

 Do I miss something here ? How can this be corrected ?
 In war thunder it works OK as far as I have tried. Of course  other sims  like War Thunder recognizes the Joystick as well and the double programming strokes.

Here in BoS there is no recognition of any Joytic model however , just joy 0 for the stick and joy 1 for the throttle. nor any  multi keystroke programming accepted...

 

 With so many button orders it is impossible to assign most if not all needed so I can use the full realism of the game.

[Urra]

Try to assign the commands in the programming window as ordered keystrokes, not the first option on the drop down menu but next or the third (gotta check). Kind of like a macro. First for input - F, then Shift. And when releasing, order of Shift then F. The problem I think is with how it releases the shift key. I won't be able to check at my computer for next 12 hours Unfortunately. Someone posted this last year I think... try searching this forum for older posts for better explanations then mine.

[AvengerSeawolf]

Try to assign the commands in the programming window as ordered keystrokes, not the first option on the drop down menu but next or the third (gotta check). Kind of like a macro. First for input - F, then Shift. And when releasing, order of Shift then F. The problem I think is with how it releases the shift key. I won't be able to check at my computer for next 12 hours Unfortunately. Someone posted this last year I think... try searching this forum for older posts for better explanations then mine.

 I will check this out and try a macro order at the moment. Thanks very much for the advice. Find it wierd it doesn;t work as is while others do.. anyway. WIll try and post results.

[AvengerSeawolf]

 

 

Kind of like a macro.

 

 Well it is the macro

 

 I have tried that on 2 random orders I could program and it worked. So I did the keystrokes, so that the button is assigned then delete them then go press micro order and press both keys together and that was it.. >save> load to profile and OK

 

 Leave it here so it may help someone with same problem.

[AvengerSeawolf]

 Updating .-- not all double key commands finally  work to the game even done with macro. After some hours of testing and re testing and then again asingin controls to different modes and buttons , some orders do not work at all. Amd I do not think is a conflict cause I made sure only one time to be used.
 There must be something wrong in the game and how it understands double button orders and controllers, other sims do not do that as I said.

However I'll check out anything I can find and will help to solve the issue IF possible.

[Tye]

Okay I know this post is old but hopefully this will be helpful to someone. I think I figured it out....
No macros are required you just need to set a delay on the non modifier key stroke. When you are setting the keystroke right click to lets say "Weapon Group 2" ALT + Space ​Left mouse click on the Space keystroke icon to highlight it, then right click and go to set delay. I've set my delay to 0.100sec and it seems to do the trick.

p.s. yes that is a cell phone pic of my screen the print screen key was not functioning since I was in the program menu for the x-55 and was being lazy