Fix for screwed up 109 flaps when using x55 and x56 throttle wheel

[von_Michelstamm]

I like the idea of having to spin a wheel to adjust flaps, just like on the actual Messerschmitt itself.

There's a big scrollwheel on the side of the throttle which should work perfectly for this, HOWEVER the way input is programmed in game, flaps are set by holding down a key, not rapidly tapping a key or button.

 

 

The result in game is you spin the wheel and either nothing happens or it very slowly, erratically adjusts the flaps by tiny increments.

The fix is in your Logitech setup controls.

First, find the wheel inputs. Then, have them activate a macro (I used F and G for this, use whatever you like).

Click on the little arrow in the corner of the box (it appears when you hover over it) and choose "new advanced command".

 

 

Click in the top box, and hold down F (or G) key to input it. Then, select the release input (the second one) and right click and set the delay. I find 0.200 works the best... higher values and it freaks out in game.

 

Then save it on top, click the little blue"profile" crosshair button, and you should be good to go.
 

In game unbind the wheel from flaps and instead make sure they are set to F and G.

Enjoy!

 

Edited May 4, 2019 by von_Michelstamm

[Apanos9]

Nice idea, anybody know how to do that with joytokey? 

Edited May 4, 2019 by Apanos9

[von_Michelstamm]

No clue, but if it can program macros it probably can time key press duration.

[VSlash]

Doesn't seem to work for me for similar 'hold to increase/decrese' settings (tried to put spit's gunsight distance on it).

 

Is there some trick?

[THERION]

Hi,

 

I've got the X55 Rhino combo which is very similar to your system, if not the same except of the colours. I originally wanted to map the flaps

on the rotary button too, but it doesn't allow you to do this for this function. So, I use this for the manual radiator operation (ME110, Spit VB),

where it works quite well - one rotary step = one radiator operation step.

 

For the flaps I use the two way button right next to this rotary button, because it allows you to keep the button pressed to move your flaps

more than one notch. The rotary button only allows you to send one key press and is not continuous (endless rotation), so it might be very

difficult to program a macro for it, as you never know how many key press are needed to fully deploy/retract your flaps and isn't applicable

to all planes we actually have.

 

And btw. I don't use the Logitech software to program all these functions - I'm sick and tired of it. I just map the buttons, rotaries etc. directly

in the key mapping function of the game. I used to program full macros for Thrustmaster's FCS/WCS, even with modifier back in the 90's.

If you only use your combo for one flight sim, then this might be OK, but otherwise you will need to program different setups for each flight

sim.

 

Cheerio

[von_Michelstamm]

First off, click the little gear icon in the Logitech app. On the test page, while spinning the wheel, are you seeing any letters appear?

if not, try saving/loAding the profile, quitting the Logitech app and reloading.

 

if it’s working, you should see a series of black and gray letters, sometimes blue ones...

8 hours ago, -IRRE-Therion said:

 

more than one notch. The rotary button only allows you to send one key press and is not continuous (endless rotation), so it might be very

difficult to program a macro for it, as you never know how many key press are needed to fully deploy/retract your flaps

 

Cheerio

 That’s the point of this. By setting a key press delay macro, the game treats it as basically being pressed the whole time.

i timed both holding down a button and this, Holding down it takes 25 seconds to max a 109s flaps, with this it takes around 27.

If you use a longer press interval it treats it as one long keyhold BUT sometimes it misreads the input and the flaps do nothing at all until the interval runs out. This is as close to it as I could get it. This way, if it hiccups on the the input it’s reading the next ‘press’ only 200 milliseconds later.