https://virtualsky.ivao.aero/pilot-client-changelog/
Thanks for your patience and lobbying of IVAO developers. This will be implemented in the next update.
Just to be clear, this isn’t an XPilot, the Vatsim client, support forum.
The easiest way to keep X-Plane’s nav data updated is using Navigraph’s FMS Data Manager app: https://navigraph.com/products/navdata
Try removing all third party plugins, including those in scenery (e.g. GroundTraffic), to see if you can get a “clean” crash. Unfortunately there’s all manner of reasons X-Plane can cease to function, including many of its own making.
It should be populated below 15,000 ft. The safest choice is a manually set TGT (e.g. 90%) as it can never be invalidated, unlike the others which are based on finite lookup tables. The thrust limit only comes into play for a go-around.
Some kind of networking issue? Do you have a VPN you can use? Or not use as the case may be. Maybe @Cameron has other ideas for traceroutes or the such.
> Your secret Hoppie logon code goes into User Settings > Networking.
Hoppie functions are then available via the DATALINK page (for telex and pre-departure clearances) and FANS page (for en route CPDLC).
Using DEP CLX is how it’s been implemented in the CL-650 to match real world use, however the backend messages sent/received are primarily based on how Vatsim uses Hoppie (Hoppie “CPDLC” is totally non-standard and undocumented).
How does IVAO use Hoppie for clearances? Can you provide examples from http://www.hoppie.nl/acars/system/log.html?
Thanks.