@aceridgey for the GNS - AUX - SETUP 2 - COM Configuration.

Assuming you're on MSFS 2020, and everything is installed correctly, I think all of your remarks can be attributed to the complexity of the aircraft. Are you familiar with the triple-fed bus system, and turboprop engine limitations?

There are many configuration issues that could cause what you're seeing. For instance, many of the aircraft lights will not work unless the left and right generator buses are online. You will also have to disengage the starters manually for the starter-generators to produce power (usually what closes those bus ties). If it's just the electronics that shut down after several minutes, that comports with the generators not being online too, since the battery will eventually give out, or overheat. If it's the engines that shut down after a few minutes, you are probably exceeding the engine's torque or ITT limits.

Long story short: The current version of the Analog King Air has been in the hands of thousands of happy users for a couple years now, so these are almost certainly not bugs. There could be an installation issue, or an incompatible freeware addon, but most likely it's just the learning curve required for one of the most complex general aviation aircraft in service.

If you continue to have questions, I am always here to help! Feel free to share any videos or screenshots of your situation too. Helping people learn complex systems is my favorite part of creating these aircraft, so I'm always to take a look.

It doesn’t work when started on the runway with engines running either. Also, the autopilot on my RJ doesn’t work either now. I’ll check my F28 and 146 also, but I am seeing a pattern here. the autopilot and 530 do work in non-JF planes. This is happening in both 2020 and 2024

Then why was F28 V1 coded to level off at the selected altitude if it is just an alert system...

Sorry that's happening to you. Nothing is more infuriating than a CTD at the end of a flight. Luckily, I can't recall a single reported case of CTD's with the Dukes that wasn't a one-time thing, or wasn't eventually attributed to something else. The method that I have chosen for programming my aircraft makes them delightfully resistant to CTD's, unlike aircraft that use a lot of WASM instruments.

From what I've seen in my own coding, I always suspect the GPS unit in the case of CTD's, because the simulator's native flight planning system seems to be one of its least stable aspects. For the sake of testing, I would recommend using another GPS unit on a couple flights to see if the CTD can be attributed to the GTN 750/650.

Feel free to report back here, but I might also recommend contacting Just Flight support. They have a knowledgebase for general simulator issues, while I specialize in the aircraft specific knowledge. They will also have access to an XBOX for testing, if that's needed. Please let me know what you discover!