Pils

Thanks to some dogged investigation by @oisin650 it seems that the FAA only retain charts for the current and previous AIRAC cycle, e.g. at time of writing, 2201 and 2113. The CL-650’s digital charts function uses the AIRAC cycle associated with installed custom nav data (if present), or default nav data otherwise, to fetch the charts from the FAA. (Which makes sense, one would want charts to match one’s nav data.) However, this means that if one only has default nav data then the FAA chart function is unavailable, because X-Plane ships with nav data from 2018 and these charts have long ago been removed from the FAA’s digital chart service. The solution right now is to have up to date nav data, this is available to purchase from Aerosoft or Navigraph. (I highly recommend the Navigraph Ultimate subscription that gets one access to global Jeppesen charts in the avionics instead! #notsponsored)

The latest version accidentally triggered unexpected behaviour in Rosetta that really does a number on the aircraft systems. A fix is in the works. Appreciate the understanding and patience.

Are you on an M1 Mac running Monterey?

Yes, it can be landed with ATS engaged if you desire, and is done in real world ops regularly.

Try in non-persistent mode for greatest reproducibility, please.

Thanks for expressing your support, the more people we hear from the more it helps prioritise. In the meantime, can you set datarefs with that tool? Because if so just use those and force the switches to match your hardware on load? Or does it not change the value until the switch is moved for the first time?

CL650.lua Throw this into your FlyWithLua scripts directory. With DataRefTool one should be able to implement basically any switch one would like based on these examples.

It was changed to be more universally applicable, feel free to edit the checklist.xml and do your own SOP.

Interesting. I’ll have to try that.

In general, that’s correct, default avionics (G1000, FMS, etc.) will use Custom Data if it’s present, replacing the default data; or, the default data if that’s all one has. Some third party addons with custom navigation systems will make the same selection, however will be reading the data directly from the disk (rather than through X-Plane’s programming interfaces, which are quite crude). However, the CL-650 is the only addon (that I know of) that lets you select either the default data or custom data while in the cockpit. That’s the key differentiator here. In theory it could be implemented so that the two databases could be read from arbitrary locations, including outside the X-Plane directory, however that’s not the design choice that has been made at this time.

Just to be clear; you’re talking about the command CL650/FCP/ap_eng, yes? There’s a difference between commands and datarefs.

Thank you for the additional information, and for your patience.

I guess this is just a consequence of the ATS being somewhat independent from the FMS due to its “aftermarket” origins on the type.

Definitely r3? Did you ever install r2?

Can you say whether it was r2 or r3 definitively?

Sorry, of course, High Sierra is a long time before M1 existed. I can’t keep track of all the California names! What exact version of macOS were you running when you first had the issue? Have you done any upgrades since?

What exact version of macOS were you running when you first had the issue? Have you done any upgrades since?

It is.

SVS is on? Try with it off and do another cold and dark.

On another M1?

Yes. Usually with money. https://navigraph.com/products/navdata https://www.aerosoft.com/en/flight-simulation/flight-simulator-2004/tools-missions/1750/navdatapro-one-year-subscription-13-datasets?c=309

It should work exactly as you expected, but possibly there are edge cases. I haven’t personally used the 3D popups. Have you tried hand editing the windows.cfg file and replacing it before each sim start?

Yes, it’s automatic after you check the box to enable FAA charts in user settings. However you may need up to date nav data for this to function at this time.

Hint: It’s not in the cockpit.