#Joystick sensitivity update#

#Joystick sensitivity update#

Here's a video that was uploaded back in November discussing the issue, this fix nolonger works as the game rewrites the values on launch after a update a while back and even if you set the ini to read only the engine still doesn't recognize the value and always acts as if it's on the default settings that are just WAY to friggen high to do anything other than piss away air resources on taxi's and completely avoid a dogfight or battle. Please for the love of gods fix this issue that has been being brought to your attention since the beta.you guys are having users upload activity logs every-time they log out, you know what everyone has connected to their PC, why don't you tally up the number of people actually using joysticks, i think you'll be shocked to see just how few pilots do and it isn't because most dont want to or haven't tried, it's because of the deadzone and sensitivity issues are a serious crippling issue to anyone attempting to use one. If your using a high DPI joystick like a thrustmaster T1600M your doubly screwed with it's 1600DPI and this absurdly high default sensitivity value.

The deadzone and sensitivity are both far too high on their lowest settings, most of us with joysticks can move halfway off center before the game detects motion and sensitivity makes it impossible to do anything other than use aircraft as taxies because there's absosluty no precision and wild over corrections, like a mouse with it's sensitivity value maxed out, makes target acquisition all but impossible and makes the mouse and keyboard far superior and a distinct advantage to joystick users. I suspect this hasn't been more of a louder issue because noone in this game flies with a joystick for just this reason, M&K are far superior because of it. Real hardware would do the same thing - inputs at the electronic level typically were not directional, but 4-bit binary, and that held true whether the joystick was 4-way or 8-way.I know I'm not the only one, a simple search for 'joystick' reveals many threads, last one a month ago about how huge of a problem the joystick sensitivity and deadzones are. It's still possible to hit diagonals - the switches are close enough that there's a small zone on each edge where the actuator will hit two of them at once - but that's quickly overridden once you move the joystick out of that zone and into the intended corner. It has a diamond-shaped restrictor plate, rather than the circular ones seen in most 8-way sticks, which prevents the joystick from getting stuck in diagonal corners. Pac-Man / Galaga repro joystick to solve the 4-way problem. Dig Dug may illustrate your point better. The only way to stop Pac-Man is to hit a wall.

He keeps moving forward when the joystick is in neutral position, and it's normal to make your turn inputs early. I don't think Pac-Man is the best example of this.

'We don't want to leave them as neutral because then Pac-Man would stop dead in his tracks in between direction changes,' These shorthand rules can be confusing, so I'll step through an example with the 8-way joystick. Repeated rows don't need to be specified.

If a row has been shortened to 5 or fewer characters by rule #2, repeated values at the end of a row string don't need to be specified.

The last four columns don't need to be specified if they're symmetric with the first four (left-right symmetry).

The last four rows don't need to be specified if they're symmetric with the first four (i.e., up-down symmetry).

These strings of characters can be a bit unwieldy, so MAME has a shorthand notation that uses the following rules: Putting all of this together, we can turn the joystick maps shown in the previous section into strings of numbers and letters: The only other value we need to represent is the sticky, which is denoted with an 's'.ДЇinally, we distinguish individual rows of the 9x9 grid by separating them with a period. Note that this is the same direction/number mapping that appears on the NumPad of a keyboard.