Pils

Sadly, the issue at NOAA has returned.

There are several buttons in the real aircraft that need to be helm down to activate, I assume as a safety measure, and these are replicated in the simulation. Personally I wouldn’t touch this software, it’s a hack and known to cause issues in XP. I don’t know those other tools. The developer of other fine CL650 hardware had a similar issue with their DCP/CCP, and was able to work around it with this script https://www.avioniquesimulation.com/wp-content/uploads/products/DCP_CCP/DCP-CCP_panel_lua_script.zip, you can look at it for inspiration.

Its very simple, as I’ve explained elsewhere, the “AP engage” command must be held “active” for multiple frames, however MobiFlight is incapable of doing this as long as it uses X-Plane’s UDP interface.

From the dev: So, I'm afraid the XP11 just flat out broke because of that bad GFS data and there's no trivial workaround. The only way is to use the XP12 version. The XP11 version always pokes at the GFS data and NOAA is returning some bunk that's crashing the plane. You will need to use XP12 until either NOAA fix their data service, or we get a new beta build out with a fix.

This error specifically is a bug in XP’s flight model. You’ll need to report to Laminar. Please post Log.txt from XP regardless.

https://discord.gg/hXM9HzWt

I look forward to the fruits of this labour, because the current set of documentation is woeful.

https://discord.gg/csypV2JR

No.

Negative.

Define “work”.

What driver?

Arc GPUs are not officially supported by XP, and unlikely to be supported by TBM any time soon.

Please post Log.txt

I recommend 11 on 8-core HT/SMT processors as there’s resources to spare. The original advice was more for processors with 8 or less threads.

Which script?

Not been reported by others. Can you record and publish your own video of the issue by chance?

As Ben hinted at, make sure you start X-Plane with --num_workers=11. Also, look at the frame profiler, it'll help point at a particular part of the frame rendering that's being slow.

Download the installer again?

These are not related. Your problem is elsewhere.

https://discord.gg/y8aNf6kg

Check the circuit breakers. Or create a new airframe.

https://www.macworld.com/article/338843/how-to-force-a-native-m1-mac-app-to-run-as-an-intel-app-instead.html

You have throttle 1 and 2 assigned twice, once to the Bravo, once to the Yoke. Fix that first.