Sounds like X-Plane doing X-Plane things… it can struggle at dynamically loading high fidelity objects and textures. Plus the Vulkan texture management algorithm is not perfect, and can get itself in a muddle all by itself.
I’m sorry you’re having trouble, unfortunately this forum has no association with xPilot the Vatsim client. You’ll need to look for support via their Discord. The link is available on their website: https://beta.xpilot-project.org/#/
I believe X-Plane doesn’t count its main thread in this value so that should be considered if necessary to free up additional processors for other uses, including an aircraft’s multi-threaded plugins.
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.