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?
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.
We are sorry y’all’s logs are being filled but these errors are due to an X-Plane bug and there’s nothing the developer can do about it. They can be safely ignored.
This only applies to new airframes.
The command works as expected with my hardware. Might need to be held down for a moment or two? I forget. Manipulating the buttons via dataref… that may need more fanagling. The corresponding float datarefs are for button animation, the integer datarefs are for the logical position of the buttons. Maybe that helps? What exactly is OP doing to actuate the FCU buttons?
Ok, well a screenshot to confirm that would be nice, please, thanks.
Does the IVAO client populate these datarefs properly? https://developer.x-plane.com/article/overriding-tcas-and-providing-traffic-information/
You have your PFD range set to 5 nm, but that target is 20 nm away, so it’s obviously not going to show up.
I assume you just took a bad screenshot as an example?
If this is one under the CL650 tree then it’s probably identical in function. The software design of the product means that basically everything has a custom command first and foremost. And then a subset of things have the default commands translated back to the custom commands automatically.
While this request is being considered it’s fairly trivial to program these kind of custom commands that interface with the switches’ datarefs in a FlyWithLua script.
One possible issue I can see, not that I’ve seen this cause the crash you’ve seen specifically, is the VRAM heap allocated to X-Plane is being exhausted. If you’re running Maximum texture quality then then it down to High.
We are all convinced this is an Laminar crash, and there’s nothing in the data provided for the developer to investigate, so I’m not sure what else we can do, unfortunately.