Hello,

I have bought this little keyboard from Ali… (Minikeyboard CH57X)

 

It has several buttons and two rotary knobs. Knobs are not axis, but “buttons” - one is triggered when turning knob to right, second is triggered when turning knob to left. So ideal for autopilot.

My issue is, MSFS is not registering this knob ideally - see this video: 

 

I have set it to control heading, but heading change is registered only with 30% change. It does not change heading every time I rotate with knob. Small adjustment by one position is hardly registered at all.

Device is set to write “+” when turned to one side, “ě” when turned to second. The main thing is that turning knob in Windows works well, for every rotate it writes correct character. Also in MSFS menu, when searching Airport, it works well, every character for every movement.

In MSFS I have set “+” and “ě” as keyboard input for increasing/decreasing heading bug.

I have suspicion it’s not only MSFS issue - I think when knob is rotated, input for character writing is send, but this input is not long enough to be registered 100% by MSFS, but long enough to be registered by Windows writing. I tried program reWASD, creating virtual joystick - Device in this program is also registering rotary knob not great, same as in MSFS. In Device settings program there is no way to extend duration of button action.

Please, do you have ANY idea how to fix it?

You might want to try Lorby's AxisAndOhs. In the button setup, you can set timing/auto-repeat etc. I think you can try a fully functional (time limited) version for free.

3 hours ago, Rakes said:

Please, do you have ANY idea how to fix it?

The simple of it is that MSFS doesn't recognize every single device out there, so you need a "software" between the device and MSFS.

For example I have the Beringer X-Mini with SPAD.next as the software, the software may/or may not recognize your device depending on how it's recognized by your computer but it does recognize my X-mini. With a little bit of YT I was able to configure my X-Mini to do exactly what your looking to do.

This is a good place to start.

 

Edited December 20, 20223 yr by FPStewy

33 minutes ago, FPStewy said:

The simple of it is that MSFS doesn't recognize every single device out there, so you need a "software" between the device and MSFS.

This is just *insane*. If *Microsoft* Windows can recognise a hardware device then a *Microsoft* sim should be able to see it. Pretty as the sim is, let's face it - the (Asobo) GUI is a total disaster.

2 hours ago, Adamski_NZ said:

This is just *insane*. If *Microsoft* Windows can recognise a hardware device then a *Microsoft* sim should be able to see it. Pretty as the sim is, let's face it - the (Asobo) GUI is a total disaster.

That doesn't make sense - Windows recognizes many thousands of hardware devices, but why would MSFS recognize (and map) every single hardware device that Windows does?

There are many specialized hardware controllers - should MSFS natively recognize every MIDI controller in the world and allow you to map that into MSFS? MIDI controllers are just one example. How about this - https://www.blackmagicdesign.com/products/davinciresolve/techspecs/W-DRE-13

Should that big wheel be mapped natively into MSFS? How would that work? 

Or, what about this - https://www.blackmagicdesign.com/products/davinciresolve/techspecs/W-DRE-06

Why would a flight sim recognize random specialized hardware controllers and map their inputs into the sim? There's specialized software like AxisAndOhs for that. 

 

34 minutes ago, FlyingGoose said:

That doesn't make sense - Windows recognizes many thousands of hardware devices, but why would MSFS recognize (and map) every single hardware device that Windows does?

 

Because ... if Windows detects the hardware, then it will send the inputs to wherever/whater needs them. IMHO, the problem is with the "fancy" controller GUI that simply does not work.

At various times, I've had an X52, X56, TCA plus carious rudder setups. X-Plane, DCS, Elite ... all have no problem whatsoever.

6 hours ago, Adamski_NZ said:

Because ... if Windows detects the hardware, then it will send the inputs to wherever/whater needs them. IMHO, the problem is with the "fancy" controller GUI that simply does not work.

At various times, I've had an X52, X56, TCA plus carious rudder setups. X-Plane, DCS, Elite ... all have no problem whatsoever.

Are you really comparing a joystick that is designed to be used in a game with a hardware controller that is designed to be used in professional software like video editors or DAWs?

If yes, then I guess there’s nothing left to say. 

10 hours ago, FlyingGoose said:

That doesn't make sense - Windows recognizes many thousands of hardware devices, but why would MSFS recognize (and map) every single hardware device that Windows does?

I predict that this will change in 2023 when Keyboards start to come with knobs we're already seeing it with the Stream Deck for example.

Also there's already a Knob on your mouse that can be assigned to the heading but everyone just uses it for zooming in and out.

Now if MSFS would recognize the X-Touch Mini, the Stream Deck Plus, the Loopdeck then that would be a game changer for sure.

This is what my setup looks like for now. The knobs handle the heading, altimeter, radios and nearly all the controls of the AP and use at least 10 buttons and that's just one one layer, you have two.

 

My only nemesis with this is configuring the lights not the off/on but the dimming up/down. There's a bit of a learning curve with Spad but in my opinion it's better than x/o's

Edited December 21, 20223 yr by FPStewy

The Loupedeck has transformed my simming after my Logitech panels stopped working properly.  
It has six rotary fine control knobs as well as the buttons.  It has a profile to download that works perfectly in MSFS.  It has transformed the autopilot.Not cheap, but a lot are buying them as it looks like they are currently out of stock in the UK.

https://www.amazon.co.uk/Loupedeck-Live-Streaming-Customizable-Touchscreen/dp/B08F7RJYZV/ref=sr_1_3?crid=ITZNMZJBCYSV&keywords=loupedeck+live&qid=1671633032&sprefix=loupedeck+live%2Caps%2C79&sr=8-3

 

Yea the Loopdeck comes at a price for me it's $379 and that's $250 more than the touch mini.

In my experience this is a hardware problem with rotary encoders, they seem to be very sensitive to how long you dwell at any notch/position,it shows itself in many audio volume controls where they are used instead of potentiometers , sometimes you can slowly rotate one half a turn and get..well lets say 3 levels of volume gain out of it but turn it a bit faster and you might not even get 1 level of gain from the same movement

They can work with certain software parameters and speed of rotation and not others they are bloody picky as hell

 

...I hate the things.

 

Edited December 21, 20223 yr by Pathfinder633

Thank's for answers, in the end I have ended up buying Axis and Ohs which solved my issue.

9 hours ago, Rakes said:

Thank's for answers, in the end I have ended up buying Axis and Ohs which solved my issue.

Yay!!! That's good news indeed!