Velocity One Trim Wheel is fixed! Thanks to SU13 Beta. I can now enjoy long flights and use the trim wheel on my Turtle Beach Velocity One flight yoke without having to worry about those crazy nose dives to the dirt. The trim wheel was one of the things that lured me to purchasing this yoke in the first place. Now I can fine tune my aircraft during the final stages of an approach to an airport. Now I’m having fun with FS2020!
I’ve a similar issue so happy to hear it’s fixed.
During any point in flight, if I trim up or down I get an abrupt movement in whatever Direction I set the trim.
For instance today I was flying the Carenado PA28-181. I took and trimed for power climb at 76kts, when at cruise altitude I leveled off, reduced power and when I went to trim down it dropped nose down like brick, this happens on all aircraft.
It does not result in loss of control but it’s annoying, especially on Approach
Looking forward to the update
I’m still downloading the latest public build (1.34.16.0) available on XBOX, and all the WU updates that come with it, but I wanted to know if we all collectively believe this issue has been resolved in SU13.
I would like to get back to using the trim wheel again
I didn’t see any mention of this issue or a fix in the official SU13 release notes, which is why I ask here.
Cheers!
Fixed in Sim Update 13.
According to a user, this bug may have returned, so re-opening this for user reports!
On October 25th 2023 I was flying the Default Cessna 152. I flew at 3000 ft for about 25 minutes. Suddenly the plane tried to nosedive. I use the Velocity One Yoke with Rudder Pedals. I have FS2020 on XBOX X and use firmware 1.4.0. I have the SU13 beta installed. I was able to fly from the beginning of September until October 13th with no trim wheel issues. Now the trim suddenly going to a -100% issue has returned. This has nothing to do with the Autopilot as the Cessna 152 does not have autopilot. I hope this gets resolved soon.
Definitely not fixed for me. I’m getting better at recovering from it, but if it happens on landing, then it’s a guaranteed crater. It used to pin the elevator trim full down and full up about equally, but now when it happens, it’s almost always full down.
Yes….it is annoying. Until a fix appears for it I have disabled the trim wheel on the V1 Yoke and use the old brake paddles on the rear of the yoke for trim up and down commands. Someone told me that Microsoft is not going to bother with this trim wheel issue until FS2024 comes out.
Not fixed for me either
Definitely NOT fixed. Running latest FW and Sim update. V1 yoke + rudders. The trim wheel is what made me decide to purchase the yoke and it is unusable. An expensive mistake purchasing the product.
At this point I would like to ask TB for a refund since it is basically a defective product.
I was experiencing the same bug on Xbox, but I noticed that if I setting the trim wheel to neutral before taxi it didn’t happen, since then I do it and it hasn’t happened again.
It is generally believed that this issue isn’t just TB but an elusive interaction between the sim and hardware.
That may be true, but I have to believe TB, Microsoft and Asobo engineers know exactly what causes the issue and choose to not discuss it publicly. They should at the very least publish the cause, list temporary workarounds and offer customers that spent a considerable amount of money with the expectation that the product operates as advertised some sort of remuneration. If MS2024 is being rearchitected partly to address the robustness between the core simulator software and 3rd party HW and SW extensions that is great, but I would appreciate knowing what is going to happen so I can decide whether to hang on and wait for the fix or spend a lot more money on the honeycomb HW. If the issue cannot be fixed then TB should stop selling the product. Rant over…
I will try your suggestion and see if the Trim behaves itself. I will let you know.
Quick question for you. When you fly a small general aviation aircraft, how long a flight do you normally take? Is it 15 minutes or do you fly for an hour or so. Let me know please.
Has anyone had this recently ? as it’s been a while since it’s happened to me, so I was thinking maybe it’s been resolved.
I still see it very randomly… running on Xbox X and the latest updates.
Is this something that could be asked about in the next Dev Stream? Even just an explanation of why it’s happening would be helpful to know since it only appeared after SU12, meaning the system was working properly in the original code, and remains unresolved.
Both… certainly in the longest flights the altitude it’s more adjusted