The latest patch notes claim “Honeycomb device 10 degrees heading issue has been fixed”
I’m curious, whether they’ve applied only a workaround that works only for the heading bug, and only for Honeycomb devices? Has anyone managed to test this yet?
I have a FSUIPC solution for this issue, so I’m not keen on screwing up the setup to test this out until the fix is confirmed to be working.
When i saw that, i had to chuckle. Well, let’s hope it’s at least fixed for the Honeycomb users, because i have a feeling that description is pretty literal.
I purchased FSUIPC this morning and I was trying to figure out how to set it up and two hours later this MSFS patch came out that “supposedly” fixes the issue. I am skeptical, I am downloading it now, BUT if it doesn’t work, can you share your knowledge on how to set up FSUIPC7 with me, cause it is not user friendly, that’s for sure. I have the Honeycomb quadrant also.
I feel you 
The FSUIPC solution is indeed hard to setup. The bright side is that the plugin is quite a powerful tool for all kinds of tweaks and complex settings, so I hope the purchase doesn’t go to waste even if the patch didn’t fix all the issues.
I’m testing the new World Update and it seems the increment bug is fixed. I’m playing with the TCA Quadrant.
Well… sounds like good news: Discussion + Poll: World Update IV (1.15.7.0) - #133 by Megadyptes7635
Yep, this made my day! I have yet to test it but reports are that it’s fixed. I have sidelined my Alpha and Bravo after the last update made the problem even worse! Finally time to dust them off and get a full VR flight sim experience 
This aged well.
I can confirm heading is now increasing/decreasing at 1 degree increments. Altitude is also increasing in 100s instead of 1000s
Also can confirm the heading bug is fixed. There are two updates.. you have to close the game and restart to get both. God bless you Asobo you magnificent bastages!
Many people’s expectations for this bug was for the fix to lead to the following two outcomes:
Holding down button X to affect variable A should never have an acceleration effect (increased increments) on variable B. This was happening and it appears to have been fixed as far as I can tell.
Holding down button X to affect variable A should have an acceleration effect (increased increment) on variable A, when appropriate. This is what I have a question about. Is everyone finding control acceleration still present where it should be? Because if that isn’t the case, I wouldn’t consider this a fix as much as a partial or full feature disability.
Also as an aside, while testing to see if this issue was fixed for the keyboard procedure I described in my original post (it is, as far as I can tell), I got the spinning heading bug of death bug. It’s a separate bug which keeps the heading bug spinning forever when you hold down the heading bug increment input (and possibly other inputs), and the application becomes unresponsive.
Mind you all I did was hold down ctrl-insert for a mere 4 seconds, just to get to the other side of the heading circle! But I digress, since it’s a separate bug.
It freaking works!
I think that what they did is remove acceleration from hardware controllers. If i hold a trim button pressed, it doesn’t accelerate. But if i repeatedly use my scroll wheel on the heading bug (with nothing else pressed, just to be clear), the heading bug will start to move in 10 degree increments after a while. So right now it looks to me like they did a good job. Not sure how it might impact cockpit builders actuating the heading bug with a hardware control. They may not get acceleration.
Yes, the 10 deg bug is fixed, but the $#$^$&#% performance issue is here again! Landing at 18 FPS is no fun my friend, and If I am getting this ■■■■■■ FPS with a Strix 3090 OC and 5ghz +64 gigs of DDR4, I hate to see what the rest of the folks are getting. Try a flight from Dalls to Austin TX . Oh, by the way, massive thunderstorms all the way with live weather, when in reality, the weather its been clear. I am getting tired of complaining, I might as well disconnect all my flight gear, connect an xbox controller, set it all in automatic and with the controller in one hand and a beer on the other, feet on the table, enjoy a nice view flying around and watching slide shows, because this is what is coming to.
There is something definitely wrong somewhere in your setup. I have a config barely above recommended and i’m getting 30-35 fps on high-ish settings. Have you tried reducing your graphics settings one by one to see if one is messing things up? Are you using any other external tool to manage FS performance, like the nVidia drivers? Have you perhaps increased the render scale resolution past 100% (not sure what it’s called, it’s not the resolution the game is displayed at, it’s the resolution it’s rendered at, a bit lower in the settings). Cause if you’re running in 4k and you’re rendering 8k… well…
I am not going through this again, there is nothing wrong with my setup…Been through this a thousand times. It is simple to understand. If you turn your flashlight on and it doesn’t work, and you put a new battery on and it works, then you know its the battery the issue. If my flight simulator was working fine (FPS) this morning BEFORE the update, same flight, same plane, and AFTER the update the FPS goes to hell, then it is the update. As simple as that.
You do know that your sim is now rendering about 4 times as many trees as before, right? Have you considered lowering the tree rendering distance to see if it has an effect? Are you using one of the “fix tree render distance” mods?
It depends:
Yessss finally it’s working as it should! Thanks Asobo!
I do not use any mods, other than a few “paid” cirties and airports purchased from ORBX. I am done with this. I hope that some day it becomes a simulator and not just a buggy game.