hoho ...

Is BiS using the number of people reporting an issue on the feedback tracker to judge if an issue is worthwhile fixing? It'd be interesting to know what that magic number is.

If they are, and them being the intelligent people they mostly seem to be, it shouldn't be unknown to them that the absolute majority of players NEVER EVER contact BiS about issues.

If it annoys players enough, they just stop playing the game.

Makeshift solution while BiS get their proverbial thumbs out of their proverbial asses (well, you can always hope they do)

While in-game ...

1. configure -> controls -> controller

2. Disable everything listed

3. back -> keyboard

4. Do your keybindings

5. back -> controller

6. Enable everything listed

7. Enjoy

WTH BiS! It wasn't like this before last patch. Can't you just acknowledge theres a problem and then fix it.

Are we supposed to UNPLUG stuff before we can map keyboard buttons?

Seem kinda lo-tek.

I really do have to say BiS representatives here on the bugtraqer often comes across as rather defensive and one eyed on the issues people are reporting in.

Using a Saitek X55 setup and same totally worthless issue here since last patch.

Is it possible to manually edit your profile cfg key bind section with like say notepad? I looked in there but it was all strange long numbers. \o/

Sad to see only 4 people considering this to be an issue.

It s really hard to understand why a developer would ignore important stuff like this.

Personally I use this method to place navigation markers when flying halicopter and it leaves me squinting for the marker rather than being able to focus fully on the flying itself.

Boggles the mind why they put this in a context menu and never gave it a proper key binding and now it lives buried and unloved on the feedback tracker.

@firefall70 @doveman

Pretty much the same thing works perfectly with vJoy without Windows test mode.

You might have to find your proper joystick device number so if it doesn't work off the bat, you have to find your proper joystick device number and replace the '2' inside the square brackets with it.

if starting:
joystick[2].setRange(-vJoy[0].axisMax, vJoy[0].axisMax);

vJoy[0].y = (joystick[2].y)

This commentary looks like it's ran out of acid again. Here, I got a couple of spare liters on my shelf I'm willing to contribute some more of ...

@rogerx Didn't you hear? It works PURRFECTLY already as it is. No need for trouble shooting. It's just the same old ignorant ungrateful whining from the community that keep failing to understand how to set up their controls properly.

That's some serious truth right there!

Anything going on with this issue or is BI still claiming the sky is full of flying sheep ...

Pro tip: rewrite controller handling for ArmA

C'mon BI ... it's not a rewrite of the game engine.