Similar to this previous Topic Topic g3x-pfd-autopilot-cannot-be-activated
Autopilot is unable to be activated through the avionics system. Working Title are no longer supporting their mod for the G3X system. They refer the user to use the Default MSFS G3X. Currently the only way to use AP is via hotkeys. I don’t believe this should be the main method of using an important aircraft system such as AP.
Please add/re-add the autopilot menu to the G3X. This small change would add a lot to current G3X planes, such as the VL3.
They stopped the support because they bringing a complete new true to life G3X (and other Garmin avionics) natively in the sim early next year with the first AAU (Aircraft and Avionics Update), so the mod will be soon obsolete and it makes no sense to put workforce to it …
I understand the reason why Working Title discontinued their work on the avionics system. The purpose of my topic is to highlight the missing AP feature in the current version of the system. Hopefully they can see this topic and work to include this feature in the AAU update later this year.
Regardless, thank you for the info about the next update. Do you have a link to/source for what they will be working on in the AAU update?
No they’re not. At least not at the current time. They’ve implicitly stated the G3X is NOT on their road map. They’ve been tasked by MS to do the G1000, G3000, and GNS 530/430 only. Unless they’ve announced something to the contrary in the last couple of weeks and I’m not aware of it, I consider the G3X pretty much abandoned by all parties at this point in time.
@CasualClick beat me to it. I was coming back with a screen shot as well. I just had to find it first.
No G3X updates are planned at this time. And it’s a shame. That’s why I consider the G3X abandoned by all parties until that position changes and is made official via an annoucement by either MS or WT. Until then, consider what we have all we get when it comes to the G3X.
EDIT: BTW, @CasualClick, that wishlist topic has my vote.
Working Title would be the only team that could enhance it. Asobo reached their limits shortly after the August '20 launch, that’s why Jorg brought Matt and the crew on to fix it all. Strategically I think MS-Asobo made a decision on an ROI - i.e., the G3X is “good enough.” Obviously parts of us in the user community disagree with that.
That’s what leads me to believe that at some point, the King Air 350i has to be an Aircraft & Avionics Update recipient. There’s just no way they’re going to let the KA linger in the unrealistic configuration it’s in. But that does mean Asobo will have to unlock or redo the interior cockpit model. It’s just improperly configured today to even take an STC G3000, never mind the ProLine 21 that it should be.
Just caught up with this thread this morning. Setup here is Windows 11, MSFS Windows Store version 1.30.12.0 , GotGravel Vertigo, SU11 beta with AAU1. I also own the HJet and VisionJet from FlightFX and have a premium license to the PMS50 GTN 750 product. After recent MSFS updates, the autopilot controls in the Vertigo no longer came up. So, I reinstalled the WT G3X add-on even though WT calls them obsolete. That restored the autopilot control panel functionality in the Vertigo but, after reading your comments, I am concerned that by doing that, I may have damaged the Asobo G3X. Do you have any thoughts on how would I test that? Should I remove the “obsolete” WT G3X code and use only the PMS50 instrument autopilot for the Vertigo?
You can’t. The AP won’t work without the G3X from WT. The base VL-3 Asobo built is in real life not equipped with an AP.
You could edit one of the CFG files to enable AP and FD if you insist on only having the Asobo G3X. These posts were made available a few years back and can be found through a search.
