Listen to these guys. Don’t do what I did. I finally figured out how to configure Gremlin from scratch and had it up an running on Tuesday. But by the way I was testing it I was still showing I had the 10/1000 Bug. So I spent the next 2 days going back over everything I had done and trying all the different ways to set up the A/P controls to get rid of it. Then today, after reading the suggestion to just check in MSFS itself, I found the offending button in less that 2-3 minutes. Mine was a button in vJoy page that set the Parking Brake. It wasn’t on the Alpha or the Bravo at all. Just flipped the switch down and the bug disappeared.
2 Likes
did you manage to figure out way Gremlin was sending a continous signal to vJoy?
You were absolutely right sorry for having doubts. This time I had the issue at the stand. Was my TCA throttle quadrant both engine starts buttons and ignition buttons giving continuous signal and heading bug was +/-10. I then unplugged the TCA throttle quadrant and the heading bug was then +/- 1. I don’t know why I have this intermittently though so will have to play around with it. Also why this would happen mid flight ? as I don’t touch the engine starts ( sometimes forget ignition though ) unless I have multiple buttons that do this.
So I know the reason for the problem now so thank you very much. Just need to record each instance and solve each one. Ignition is solved as I wont use in flight ( ignoring the bad weather recommendation) so need to resolve the engine starts ( for now).
What a performance.
1 Like
I didn’t look at that yet as I was just happy to find the cause and used MSFS for actually FLYING for a bit. I will check into it this afternoon as I need my desk for work this morning.
Have solved my issue by making a new profile for my TCA throttle quadrant and deleting the engine start buttons. Shame as the buttons are a nice touch but need my heading accuracy more. Hopefully Thrust master and ASBO will sort. Thanks all for the advice.
You can simply use the Trustmaster Target utility to set all the switches on your controller to pulse. That’s what i did on my Warthog throttle and i haven’t had any issues. Pretty easy to do.
I finally found a program easy to use and works very well to fix the 10 degree problems
It’s called “RC MAPPER” easy find on the web and I have a link to a guy that has a good tutorial for it.
Microsoft Flight Simulator | Heading/ALT Bug | Cause | FIX!! - YouTube
Hope this will help. Surely easier than gremlin!!!
Grrrr. Just got a Honeycomb and hit this with my rotaries 
. This really should get fixed by Asobo I don’t want to install more software to fix a bug in FS. I get having acceleration if the mapped button is held down but not some other button on some other joystick causing this.
Well I can just say that according to them, it is fix it seams!!
Believe me I didn’t want to do this neither. $300 for the honeycomb alpha
and $100 + for MSFS2020, yep we shouldn’t have to do anything!!
Where did they say it’s fixed?
In feedback snapshot under the link below.
April 1st, 2021 Development Update - Microsoft Flight Simulator
Like I said, that is the way I read it, I could be wrong as they do not explain things very well!!
It’s saying it’s fixed and it’s being released in 2021. As far as i can understand from that, what they mean is that they have a fix, it’s in testing, and will be released sometime this year.
It was meant to be fixed in the last sim update, then has been pushed back to “2021”, and the description has been changed to refer specifically to “mouse interaction”… So who knows if the fix will also apply to using controllers. They didn’t address the issue properly in the last Q&A so we are being left in the dark as to when the fix will come or if it will even fix the problem fully (or just for mouse interaction)…
There you go. Now it says “mouse interaction fixed”.
Sounds like this should solve the issue for most people. But i shall make a prediction: I have a feeling it won’t solve the issue for cockpit builders who use external hardware to interact with the heading bug.
Can you describe a use case for that?
The Honeycomb Bravo has a knob to select heading, altitude, ias, obs, etc and another knob to set the values of those bugs. This bug applies not only to the mouse interaction but also using 3rd party controllers (or even keyboard controls I guess) that set those bugs. Fixing the mouse interaction only is not enough
Depends how Honeycomb send those signals to the sim, and depends what Asobo mean by “mouse interaction”.
If Honeycomb use lvars or similar to control the sim and Asobo mean clicking on the control, then yeah, that’s bad. But if Asobo mean fixing the control itself that is tied to the click spots, it should be ok.
So there is hope, but i can definitely see how “mouse interaction” is not a very promising message.
Isn’t this fun!!!
Lol. Honeycomb doesn’t move your mouse pointer over the click spot and click it for you. That would be absolutely absurd! Too bad if you were in the external view or none of your controls would work! The mouse interaction isn’t the part that needs fixing, the way acceleration works for controls across the sim needs to be fixed.
Btw for that knob on the Bravo there are controls in the sim that can be mapped like any other control. They are called “plus” and “minus”. Those are what the honeycomb knob is designed to be mapped to.
Never said it does. What i said is that Honeycomb (and any other controller, actually) might be working through the same controls that capture mouse clicks. If you still don’t know what i mean, then i can explain some basics of GUI interactions if you want.
You don’t know that. I don’t know that. Neither of us have seen the code.