10 Degree bug is fixed for me. Have a Honeycomb Alpha and Bravo. All Default key bindings and I can select Heading in 1 degree increments and altitude in 100FT! I also noticed a significant decrease in FPS about 15 or so, but suspected that would happen when I read the notes in the update that indicated Tress had been reworked. Still getting around 35 FPS in ATL which is perfectly flyable. Will decrease a couple of settings to reduce the burden on my my EVGA Black 2070 Super (the cheapest EVGA 2070 Super BTW). Should be able to recover most if not all FPS with careful experimentation and reducing my perceived visual quality. For those still experiencing the heading bug, suggest you rebuild all of your peripheral profiles from scratch, than make one change at time and test. I know it takes some time, but being an electrical engineer experienced with trouble shooting, only change one variable at a time. Finally, BE PATIENT AND LOGICAL! Also be glad that this issue has been fixed by the voting process!!! Thankyou MS, Asobo, and Honeycomb for fixing the issue in spite of all the negative comments on this forum. To be honest not sure who actually fixed the issue, but whichever company(ies) did, thanks!
Have you ever been at the Dallas/Ft Worth Airport, in person or in the Sim? There are no trees anywhere to be seen while you are sitting on the tarmac, therefore the Sim is not rendering any of them until you are airborne. At the Tarmac I went from 45-50 fps this morning before the update and now is barely 30. And I can go on and on…
And are you usually this caustic when someone tries to help you, or is it just me?
Except, sadly, it’s not. As far as most of us can tell they did not even remotely fix the tree rendering bug.
Don’t take it personal, I am just upset about the state of this software. Thank you for taking the time to reply to my angry post, but like I said it many times on multiple posts, when it was working fine an hour before a patch , then it is the patch, there is no other logical explanation. This issue is not the trees when you are stationary at an airport where there are no trees. If you look at my previous posts, I mentioned the Dallas/Ft Worth airport many times because when I do benchmarks, I use the same parameters to be consistent. People were telling me that it was my system, and some even said crazy things like putting caps on the FPS, when my hardware is not the bottleneck, the Sim is. Sure enough, if you read Asobo’s patch notes on the emergency patch before todays, they addressed the performance issue at the Dallas/Ft Worth airport, so I was correct all along; plus that patch fixed my FPS, that is, until today’s. The expression of one step forward and two step back applies to every single patch we got for the Sim since its release. Asobo would be crazy if after all these complains about performance, they add things like more trees. Frustrating
Uh, oh, exactly what I was afraid of. It seems the half-■■■■■ acceleration functionality - originating from the early 2000’s - is so deeply engraved in the code that it’s harder to re-do than remove entirely. I’m not sure if this is an improvement or regression.
The acceleration functionality for physical controller knobs is important as well.
How you select 10degrees movement now because 1degree is so slow?
Weird. To me it looks like i’m getting way more trees. The way Seb said it is that trees are now drawn twice as far out as before.
Would it be possible to take your frustration to a more appropriate thread? 
I don’t know about that… i personally don’t want my trim to accelerate. In fact, there are not a lot of controls i want to accelerate, and all of the ones i can think of are knobs i use with the scroll wheel. So far it all works as expected for me, but like i said above, there are a lot of use cases i am not covering in my setup.
Well, for me the heading bug starts moving in 10 degree increments if i keep scrolling on it. I tested this in the JF Arrow.
I agree about the electronic trim. In real life it does not accelerate and should not do so in MSFS either. However, currently the trim is very very slow, especially when using a trim wheel accessory that is rotary encoder based. The acceleration is a neat feature to overcome this issue.
Also people who use push buttons to adjust controls that are usually adjusted via knobs and rotaries appreciate the acceleration feature.
Yeah, i suspected that this would be the case. It would be good if they supplied the repeat sliders we used to have in FSX.
I would actually prefer a solution with a “shift” key or button on a controller device of my choice. When it’s pressed, you get 10 degrees heading or 1000 feet altitude. Could even be implemented for trim with no negative consequences.
10 deg / 1000 ft bug is still there for me with the Honeycomb Bravo. If I turn the physical knob around it increases/decreases by 10deg/1000ft.
Sadly there is no control acceleration when using rotary encoders with mobiflight. Just as I figured before they fixed it. Takes all day to move the HDG bug or CRS for example. I used to be able to hold an event mapped in MSFS to accelerate it. However when using the Bravo to control HDG and CRS it does have acceleration. So maybe Mobiflight will figure that out at some point, but I doubt it.
My Saitek radio panels now work great. My propwash transponder works but my Saitek Multipanel now has a blank screen.
Are you sure you updated your sim? What version is it reporting?
I use the Windows Store premium edition. Windows Store says the game is current version. The big 22GB patch is installed and I activated the WU4 in MSFS. And I did a content update as well (lot’s of scenery updates, approaches and airfield updates)
I have to check the version number tomorrow as I’m not near my PC now.
Both the physical knob on the Bravo as well as using the mouse to turn the virtual knob in the cockpit has this issue.
Sounds like you didn’t download the patch from the Windows Store. Make sure you go to downloads on the left hand side in the store and then click on get updates in the top right.