So, on a couple planes, I’ve found that Autopilot functions extremely well. Just hit a few buttons and the plane “follows the pink line”. Those planes being the default DA62 and the newly released VisionJet.
Yet, some 3P planes and most of the other Defaults, it barely functions or not at all.
I cant figure out if it’s something I’m doing wrong or if it just depends on the type of avionics suite.
The commands I usually initiate:
AP
Yaw Damper
Altitude Hold
NAV Mode
Flight Director
…and I’ll be on my merry way.
However, planes like the TBM930, Cessna Grand Caravan (Default) or 3P like the PC-12 (Carenado) or C414 (FlySimWare)…I might as well GFMS. They’ll either nosedive or just fly off into the abyss. This isn’t the “looping issue” either. I think that got fixed a bit ago.
Or am I doing something wrong?
EDIT: I wasn’t setting “Active NAV” to “GPS”. Figured it out with the TBM.
On the C-208 I usually set the desired altitude, then adjust the verical speed setting and heading.
I do all this while still on the ground.
Once I’m in the air I turn on the auto-pilot and away I go.
Same for me in the 208, I adjust altitude heading in the ap before leaving, once airborne I enable FD, then AP, the altitude and the v/s to get me to that altitude and control fuel flow prop pitch and speed manually.
For the default 208, Depending on what you mean by that statement (i.e. is it just flying off in some set direction not on the guidance line?). If that’s not the issue, please disregard everything below.
If it is just flying off in some direction, the issue may be with just hitting “NAV” on the default 208. With the NXi that is now standard on that plane, keep in mind that it won’t capture the GPS nav line until it’s within about one dot of the course line, meaning you may have to manually (or use heading control) turn toward the desired GPS course line. Note that both heading and NAV buttons are lit because I’m using heading control when I started the flight, and want to use the GPS nav selection. The “GPS” will show in white text (meaning it’s armed and will activate when within parameters), but you’ll continue to fly in accordance with whatever lateral guidance currently set (HDG, ROLL…) in green text, and you’ll just keep flying off in that direction without regard to your GPS line.
Once you’re within about one dot, the GPS box will flash green with “GPS” in black text for a few seconds and then go steady Green GPS text, and will begin automatically turning toward the GPS course and then lock on the course and fly the route you’ve selected.
I think to have Working Title’s G1000 NXi work for 3rd party planes (that use the default Asobo G1000), you have to install The new WT version from the Marketplace… if you have an old version installed, uninstall, then reinstall the current version.
The TBM 930 doesn’t have a G1000, it has G3000 (which will get a refresh from Working Title soon).
I’ve been using Xbox with MSFS since May, mostly in Beta testing, and at least for me until recently, there were bugs with the upgrade process itself which would lead to inexplicable behaviour, such as avionics not working as expected. I got in to the habit of: Deleting Rolling Cache (In Options > General > Data), deleting Settings, and if necessary, complete uninstall and reinstall (without saving settings). Whenever I do a re-install everything works better. I hope the update corruption has been fixed (as claimed in the SU10 update notes).
WorkingTitle wants us to manually intercept the route after takeoff. So, the aircraft touched by the WT does not automatically turn toward the course with only the AP button.
I realized that on some planes you can “pre-program” the autopilot with NAV mode and VS mode, but on some others it’s best to engage these only after engaging the AP itself in the air. Especially NAV mode. Sometimes it wouldn’t automatically initiate with the AP.
That said, I really never have issues with following the flight path. Flown a ton in the Caravan, quite a few hours in the TBM and no real problems. The airliners sometimes like to lose navigation but that’s a separate issue. I find Garmin aircraft especially reliable in this regard.
be careful here with clear infos what packages are installed. Your mentioned behavior (not ability to set HDG,NAV and VS prior t/o) are visible also to me but only if I have WT GNS530/430W installed. If I have this package uninstalled, all is ok, especially on my Carenado Seneca.
WorkingTitle wants us to manually intercept the route after takeoff
It’s not because WT wants to, it’s because the real life NXi is like that. You set the mode and have to intercept the path either by flying manually or using HDG. As soon as you intercept the path the GPS/VOR/LOC become active.
What I said applies to the GNS 430/530 not being installed. In case of the Caravan, I know it can be pre-set with NAV mode and it will follow it, but I’m not sure about the other planes. I have had some challenges with the Kodiak, for example, I know I never set NAV mode before I engage the AP itself. The default aircraft have generally been fine for me, to be honest, even after the G1000NXi upgrade.
so you don’t have WT GNS530/430W installed? Sry I was in idea that you have it installed now due your reported problem of forced instalation from sim. heh I think that with new default sim avionics versions it brings to us also new hard and sometimes not easy to solve situations
No, that was a separate issue. It did install itself this morning for some reason, but I removed it. And these autopilot behaviours were present way before that.
all 3-rd party aircraft will be in same situation because not updated to some new sim requirements. ooooh I’m lucky that Carenado Seneca I mostly fly is after last release still flyable, yes with some bugs as Landing lights no full intensity (in night sinmply hard to see something) and missing one landing light iluminate ground.
Well mine is working great, took a IFR flight in the TBM930 from LIML to EHBK. Before takeoff I set my SID, initial ALT, HDG and the ROUTE.
After takeoff I engaged the AP and NAV and she followed the Route as set.
Without any problems.
what avionics package you have that VNAV is working at your side? If I good remember, VNAV was not still implemented on WTT side or something has changed?
On other side, you’ve never post any news with missing navpoints in old Topic, do you remember? Hope you are that user when we talked about no possibility to set some waypoints in G1000NxI?
Sorry, my fault just seen that I typed VNAV I ment NAV. I don’t use VNAV in the DA62 or theTBM930 most of the time I fly them by hand. Again sorry for my mishap
Hope you are that user when we talked about no possibility to set some waypoints in G1000NxI?