Jump to content

Recommended Posts

Posted

Hi,

 

I'm having an unusual problem with my Saitek X-52, in IL2: BOS (other sims are all fine).

When assigning the X-52 to press a key combination (say, I push a button and the X-52 outputs SHIFT+X), about 60% of the time BOS understands the command. The other 40% of the time it drops the modifier (CTRL, ALT, SHIFT, etc.) and only enters the other key (in this example X).

 

If I'm in the key mapping page, and I open a function to map it, and press the same button repeatedly (hitting "retry" each time) it will show, for instance: shift+x -  shift+x -  x - x  -  shift+x  -  x  -  shift+x. This demonstrates that BOS is getting the "X" all of the time, but not receiving the "SHIFT" (or other modifier) sporadically.

 

Unfortunately this makes it difficult to play as I cannot rely on BOS to accept the correct command for buttons on the joystick, often it deploys something unrelated to what I'm attempting to achieve, and it's common enough that I can't just fly and hope it doesn't happen on a given mission.

While, technically, I could work around this by only assigning buttons directly (not using an X-52 profile) this is limiting as I cannot use the "pinky" button to assign a second command to each button (effectively cutting my number of HOTAS buttons in half).

 

Please let me know if there is any fix for this.

 

Thanks!
 

Posted

FIXED.

 

As far as I can tell, I've discovered a work-around. I was unable to find this mentioned anywhere, so it may be useful to leave this up in case anyone else has this issue.

 

IL-2 BOS apparently struggles if the modifier is pressed at EXACTLY the same time as the letter key. For instance, if a button on the X-52 is set to "SHIFT+X" it presses SHIFT and X at precisely the same instant.

 

There is a delay function (only accessible under "New Advanced Command" in the Saitek profiler), and setting that delay so that SHIFT is struck .1 seconds before X (or whatever key combo you need) appears to give BOS time to register the first and THEN second press (and does not add any lag that I can feel in game, it's very fast).

 

F/JG300_Gruber
Posted

FIXED.

 

As far as I can tell, I've discovered a work-around. I was unable to find this mentioned anywhere, so it may be useful to leave this up in case anyone else has this issue.

 

IL-2 BOS apparently struggles if the modifier is pressed at EXACTLY the same time as the letter key. For instance, if a button on the X-52 is set to "SHIFT+X" it presses SHIFT and X at precisely the same instant.

 

There is a delay function (only accessible under "New Advanced Command" in the Saitek profiler), and setting that delay so that SHIFT is struck .1 seconds before X (or whatever key combo you need) appears to give BOS time to register the first and THEN second press (and does not add any lag that I can feel in game, it's very fast).

 

 

 

Hehe, this is what I was about to suggest after reading the first post.

 

Another solution would be to map one of the button of the joystick to the shift key only, and map all the others to single keyboard keys.

Thus by pushing or not the shift button of the joystick, you can virtually almost double the number of commands on your joystick. 

I haven't tested that (the X55 I have has more buttons than what I'm using in BoS) but it sounded as an interesting thing to try.

[CPT]Pike*HarryM
Posted

Ah, I wound up remapping stuff as there were enough unused keys, rather annoying, for example trying to release airbrakes and having your bombs drop.

AKA_Ramstein
Posted

Ah, I wound up remapping stuff as there were enough unused keys, rather annoying, for example trying to release airbrakes and having your bombs drop.

that's what happen to me, the same damned thing! I have Saitek too...... airbrake made the bombs drop!

  • 2 weeks later...
Posted

It's not Saitek Related, we have the same problem with a Warthog.

This game is really strange, it does nothing like the others (and it's everytime in the wrong way).

  • 1 month later...
Posted

Hi guys,

I´m still suffering this issue reported by squaco with the key mapping in game. Are you planning to solve this in future releases?

Thanks.

E69_Vulcanel
Posted

I´ve updated X52 Pro drivers for W10 and all seems to work properly.

Sorry for disturbing you.

Thanks.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...