Heading Bug 10 Degree Only & Altitude 1000 foot Only Increments Issue for Thrustmsaster HOTAS

[othergoosepilot]

Hello All!

The above subject is discussed on several different posts but I am listing this post to highlight the same issue that also occurs with my Thrustmaster HOTAS Throttle Quad.

Aircraft affected: All Native and 3rd party aircraft that have a heading bug and Altitude selection setting!

Peripherals affected: Thrustmaster Warthog HOTAS Quad and like many of you I can confirm it’s also happening with my Honeycomb Alpha Yolk!

The Issue: In a nutshell is that when I use my mouse wheel to either increase or decrease the heading bug OR change the Altitude Window higher or lower whilst using a toggle switch thrown to activate a system/light/heater (for example; when I turn on the landing lights using a mapped switch on my HOTAS or my Alpha yoke), the mouse only scrolls the heading bug (up or down) in increments of 10 degrees and the altitude window by 1000 foot increments. Once this switch is changed to the previous state (that has not being mapped), the heading bug can then be changed (up or down) in increments of 1 degree and the altitude window can be changed in increments of 100 foot, as it should be.

Also, I have noticed that in addition to the affected heading bug and altitude window setting above, this increased default setting also affects changing the Speed bug, HSI Compass and Compass Rose (that I’ve noticed).

Good news!! Whilst we would all like the good folks at Asobo to fix this please, I have this morning found a really simply work around. To make a change to the effected instrument, hover the mouse as you would over the knob and instead of using the wheel, click and hold the left mouse button. The first movement the bug will make is unfortunately the 10 degrees, 1000 foot, or 10 knots but then the next and subsequent increments will be 1 degree, 100 foot or 1 kt! This is how it seems to be working on my setup.

Lastly, this issue doesn’t seem to manifest itself with all items controlled with the toggle switches. For example, with me, when using it to control the beacon, its fine. But not with the landing lights! Go figure

Cheers!!

[TomZ85]

I believe they already spoke to this in a Twitch stream, that whatever was fixed was some other related bug, but they acknowledge that this still exists and is being worked on.

[hobanagerik]

@othergoosepilot

Just as one example, using a switch on any of the above peripherals to control the beacon light (on any aircraft), does NOT cause this issue. However, if the same switch IS used to control the pitot heat, the issue comes back.

An interesting distinction. I was under the impression that if any latching switch was bound at all it would cause the bug.

If you want it to be voteable, you should petition a mod to move this thread to Self Service/Wishlist. I ran a quick search on Wishlist for “10 degree bug”, and found nothing which actually surprised me given how prominent this is.

[othergoosepilot]

Thank you for the advise!

[Super275327]

Hi,
I have same issue with my Thrustmaster Warthog as well as the Honeycomb Alpha and Bravo in MSFS.
In X-Plane 11 and DCS they all work perfectly.
This 10 degree issue should be addressed by Asobo ASAP and a hoffix should be issued, rather than waiting for an update at some time in the distant future.

[MichaMMA]

Large heading bug increments when using Honeycomb yoke

Hi, I had similiar issue , heading bug , compass and so on , moved in 10 degree steps only. In contrast to you , I own an “Thrustmaster Warthog Throtte” and also fly active DCS with the A10C. I find out what happens, because also the FLAPS not really worked: MSFS does auto assign the flaps-up/down to the FLAPS switch , BUT it doesnt works as the real switch is ! [Snap 2020-10-10 at 15.55.30] The switch is “UP/Manoever/Down” … MSFS does not use these positions, it simple use the “click-…

=> this is in meanwhile for the issue more or less the master thread which collects all votes :

Heading Increment Bug (10 degree instead of 1) Explained

Imagine you’re designing a flight simulator and realize that sometimes the user will hold down a keyboard key or joystick button to make scrolling something faster. Maybe they want to increase their heading bug or their autopilot altitude setting faster so they hold down that key or button. One thing you could do is nothing. Just let them hold down the button and let that input increment up by one repeatedly. That can work. Or you could give the user some help. Maybe you could code in somethin…

not sure whether a split into sub-sub-sub distincations is good, because we lost votes on the main - issue.

[Super275327]

Hi,
I have voted at the other thread already. Since there is no news from Asobo concerning this subject, I responded to this thread as well. Also sent a ticket to zendesk, but no news.
Will have to stay with X-Plane 11 till this gets resolved.

[othergoosepilot]

Hello All!

As this issue is not isolated to only one piece of hardware, I do believe there are many of us that are experiencing this same issue in some way or form with the different hardware pieces we are using. I do hope the folks at ASOBO don’t get to see several posts listing essentially the same issue but as they don’t individually have many votes, this issue is staying at the bottom of the pile of must do ASAP bug fixing list!?!

Best regards!

[othergoosepilot]

Hello All!!

So I just checked a short while ago and it appears that WU 4 has fixed this bug! Another step closer to 100% real world aircraft emulation! Happy days