November 20, 20205 yr Hi guys, I still have issues with the TBMs AP. When i manipulate the VS Knob i get an immediate response of the AP which annoys me alot. For example when i turn it from 0 to lets say 2000+ i get 20 single little bumps up until it reaches 2000+ instead of delaying the reaction to the input and generate one smooth motion. Same with GS capture. It smashes the nose down instead of a soft transition. Roll speed in NAV mode too are a PITA. I have modified the CFG file but this only affects the HDG mode. My passengers get shaken around alot i can say. Any tipps appreciated! Best Intel i9-13900K | Gigabyte Z790 Aorus Master | RTX4090 | 2x16GB Corsair Vengeance DDR5-6000 | Be quiet! Pure Loop 2 FX AiO | Win 11
November 20, 20205 yr Just now, ThomseN_inc said: Hi guys, I still have issues with the TBMs AP. When i manipulate the VS Knob i get an immediate response of the AP which annoys me alot. For example when i turn it from 0 to lets say 2000+ i get 20 single little bumps up until it reaches 2000+ instead of delaying the reaction to the input and generate one smooth motion. Same with GS capture. It smashes the nose down instead of a soft transition. Roll speed in NAV mode too are a PITA. I have modified the CFG file but this only affects the HDG mode. My passengers get shaken around alot i can say. Any tipps appreciated! Best If the AP is on and I am either flying level or on a stable climb/descent using VS I get a fairly quick but appropriate response when I change VS value and it's not abrupt at all. What is abrupt is if you turn off AP, then choose VS and set a 2000' climb, then engage AP. The GS capture is rather abrupt so what I've been doing is adding flaps right at the same time GS captures and this can offset the lurch a bit if timed just right. Or any time you engage AP when you are way off what AP is set to for climb rate you will get a violent engagement. So as you're climbing to your preferred climb rate set using VS you can engage AP exactly then. Hold off on selecting NAV until you are very close to aligned w/ your planned route. Noel System: 9900X3D Noctua NH-D15 G2, MSI Pro 650-P WiFi, G.SKILL 64GB (2 x 32GB) 288-Pin PC RAM DDR5 6000, WD NVMe 2Tb x 1, Sabrent NVMe 2Tb x 1, RTX 4090 FE, Corsair RM1000W PSU, Win11 Home, LG Ultra Curved Gsync Ultimate 3440x1440, Phanteks Enthoo Pro Case, TCA Boeing Edition Yoke & TQ, Cessna Trim Wheel, RTSS Framerate Limiter w/ Front Edge Sync. Aircraft used in MSFS 2024: Fenix A320, Aerosoft CRJ, FBW, WT 787X, I-Fly 737 MAX 8, Citation Longitude.
November 20, 20205 yr Try hitting the TOGA button to do a go around when close to landing! That's a bit of a stomach turner too. Cheers, Ross i910900KF | ASUS ROG Maximus XIII Extreme Z590 | ASUS ROG STRIX RTX3070 OC 8Gb | 32Gb G.Skill Ripjaws DDR4 3200 I Thermaltake Water 3.0 Riing | Samsung SSD 870 1TB GB HD | WIN 10 64 Bit
November 21, 20205 yr The VS in FS2020 is not correct. You should be able to switch on VS with the autopilot on and it should not suddenly climb. It should be within 100 fpm of your current attitude. The default autopilot doesn't do that. It auto switches to the last climb rate you selected. This results in a sudden climb or descent.. In effect VS mode should be in attitude hold mode (not ALTitude mode) until you select a new climb rate. At the moment the only workaround is to briefly switch off the autopilot, then switch on VS mode. It will then show as zero fpm. You can then set it to somewhere near your attitude, then switch it on, then select your new climb rate. Another workaround (actually a good habit) is to climb with Flight Level Change mode (FLC). Unlike VS it does not suddenly climb and is also safer as it does not cause loss of critical airspeed if you forget you are in VS mode. Robert Young - retired full time developer - see my Nexus Mod Page and my GitHub Mod page
December 1, 20205 yr I set the VS speed I want before engaging that AP. I then climb and get near the climb or descent rate then turn on the AP.
Archived
This topic is now archived and is closed to further replies.