Would that be an automatic update for already installed G1099 NXi, or a superseding marketplace release, or a GitHub release? Will you announce it, and if so, where?
Anything installed through the marketplace that gets an update will show as “update available” in the content manager whenever the marketplace people push it through to distribution.
1 Like
Is the purpose of the hold at ZEBED to shed 1,900 ft. by MINCK? In other words, when you reach ZEBED on autopilot, you should set the AP for 1,700 ft. and commence descending at the start of the hold?
So when the sim loads and it checks for updates, will it detect the WT update or only the big MSFS updates?
MSFS only automatically installs updates for the core simulator packages. All Marketplace packages must be updated by manually checking in Content Manager at this time.
I don’t know that I was suggesting that it wouldn’t. I was just saying that if you felt like deleting it, as a user, you could.
-Matt | Working Title
Thanks.
When I fly across Monterey Bay from KWVI to KMRY for an ILS approach to RWY 10R, I set the autopilot for 2,600 ft., the minimum altitude at ZEBED. Otherwise, I descend to 2,600 by ZEBED. I then only need to shed 900 ft. between ZEBED and MINCK, so the hold is extraneous.
Hello all,
The next update of the NXi (v0.3.0) has been released in the Marketplace. The changelog in the original post has been updated to reflect the latest release changes. Please go to the Content Manager in the sim to update to the latest version.
Thanks!
-Matt | Working Title
7 Likes
After much trial & error, I have finally figured out why flight plans generated with custom WPs, are not being followed properly by the AutoPilot in NAV mode. Thanks again to @Fliggity1976 and others on his Twitch stream for helping me FINALLY get to the root of the issue. Perhaps this is a well known issue by the community…but if not, hopefully this can help raise the awareness, and prompt some sort of fix by the developers, or at least a work-around.
So here is an example of a flight plan created in Little Navmap 2.6.15, containing a lot of custom WPs, mixed in with a few airports for touch-and-go landings as we circle the wonderful island of Jamaica.
So we load this into MSFS, with the Working Title Garmin G1000 NXi application installed from the Marketplace. Notice how only the airport ICAOs appear in the flight plan. When AP NAV mode is activated, none of the custom WPs will be followed because they are not recognized…the aircraft will only go to the ICAOs listed. This is not expected behavior, as we want to follow all custom WPs:
So we remove the G1000 NXi application, and reload the exact same flight plan, and the result is as we would expect. All WPs plus all airport ICAOs are loaded into the flight plan:
I hope this helps those who may have been struggling to understand exactly what has been happening with AP-NAV mode, and reliably following flight plans containing custom WPs.
My question to the developers and community experts: is this a well known issue? Is there any planned fix to this? Or is there some other setting that would allow the G1000 NXi addon from the Marketplace to be able to recognize custom WPs?
Thanks!
Scott
I would direct you to the discord for Working Title. The developers are available for you to ask your questions and make suggestions. You will find a wealth of information. Remember it is a work in progress and features are being added and bugs being constantly tested and fixed. It is a very friendly group over there.
1 Like
Moved to the Master Thread. Please search for similar topics before creating new ones to avoid duplicates and splitting of valuable posts and replies. Thanks.
Thanks, I will do that!
It is a known limitation, yes, it had not yet been implemented. The latest release that just launched (0.3.0) will now import custom waypoints from the world map flight plan.
-Matt | Working Title
3 Likes
This is good to know!! I appreciate the follow up, and look forward to testing the latest release upon launch. Will this limitation also do away with the TIMECLIMB waypoint that gets introduced into flight plans? The current work-around is to generate flight plans (from LNM for example) as IFR flight plans:
Thanks again!!
Scott
Looking forward to trying it out, thank you for the update!
Worked great! I look forward to every release from you guys.
1 Like
Is there any way of getting altitudes assigned to waypoints (yet)? I’ve tried and failed but don’t know if I’m just not doing it right. I note the waypoint altitudes assigned in the default flight planner are not even imported into the G1000nxi, unless it’s an RNAV approach. What I’d like to do if possible is compile custom vnav descent profiles.
Also, can you get the TOD and BOD to appear in the MFD without altitudes assigned to waypoints? I.e., just for direct airport ->airport flights?
Finally, is there any way of determining destination airport altitudes within the NXI?
Many thanks for your excellent continued efforts WT team!
With both yesterday’s version and the new version from today, the autopilot will fly the route as programmed with correct indications on the PFD, but the HSI on the external view HUD is doing something else with wildly divergent tracks. After departure the PFD is saying “TERM” and the HUD HSI is saying “ENR”. Eventually both will say “ENR”. Whatever the HUD is doing, it’s staying closeby as the x-track distances remain relatively small.
Just me, setting error?
The NXi is working very well for me. It has improved the glass cockpit experience in “stock” aircraft.
Matt and Team WT: Thank you kindly. It is a MAJOR improvement.
OBS is the main thing that I miss with this mod
3 Likes