Goran_M

We can't INSTANTLY come out with an update when a new version of X-Plane comes out. As much as we want to, it's unreasonable to expect that from anyone. In the X-Plane world, many developers always recommend to keep 2 installations of X-Plane. A stable version and a beta. Regarding the Challenger update...we're currently on beta 3 within 1 week. That beta is in the hands of our testers. 3 beta's in 1 week is quite fast. There are only 2 of us on the Hot Start team. We can't work on two products at the same time, so while the Challenger is getting updated, we're going to ask people to continue to be patient for the TBM. If you expect an update in the next week or two, all I can tell you is the update will be out when it's done. We want it out as much as you do. But it doesn't make sense to put out an update that isn't ready. Whatever you think about the situation is entirely your opinion. It will have no influence on how fast the updates get done.

That's a new one. We'll look into it.

I saw your previous post when you posted it, but I assumed you were just letting us know. Did you check the link I posted in the post above yours? It's a temporary solution, until libradio gets an update. Wrong forum. We're not IXEG. Here's where you can submit bug reports for the IXEG 737. https://forums.x-pilot.com/forums/forum/202-bug-reports/

V1.9 was just released to testers yesterday.

Use the last stable version of X-Plane. An update on the CL650 is being worked on that will fix this problem.

Can you attach a complete log file?

It's being worked on. An update is in the works.

You're allowed 3 activations on 3 separate PC's belonging to you. If you have a blocked CL650, it means you've shared your account details with someone else, or someone else has shared their account details with you. This is not allowed.

Check your junk mail folder.

@lawson-stone No reason to feel bad. There is another forum post in here that is directly related to this, that I have spent the last few hours diagnosing. The crash is caused by the libradio.plugin that ships with the aircraft. It makes a threading call that X-Plane 12.4 now strictly enforces, and the sim kills it on the spot. (I'm assuming this began after one of the last few 12.4 updates?) To fix the crash: 1. Navigate to your C23 installation folder: X-Plane 12/Aircraft/X-Aviation/Beech Sundowner C23 v2/plugins/ 2. Remove the libradio.plugin folder entirely and store it somewhere completely outside of the X-Pane folder. That should get you past the crash. Once you're loaded in and flying, let me know if the sound and fuel selector issues persist. Those may be separate problems I'm already tracking. This will be addressed properly in the next update so you won't have to do this manually going forward.

@Jabari Can you confirm or deny that you get a crash on loading the aircraft. That it doesn't even get to the cockpit. This may be a 12.4 issue that we need to look at and work around.

It looks like an easy fix, but it would require testing, and I want to bundle it with your other forum post fix. I'll discuss this with Ilias and Cameron and we'll organize something.

The very first thing I noticed is you have X-Plane 12 installed in your Program Files folder. This will cause unpredictable problems. Even Laminar recommend you install X-Plane anywhere outside of Program Files, like the root of a hard drive/partition. The reason being, Windows restricts writing to the Program Files folder. This is why the G5 can't save its config file, and it lets me know in the log (Access is denied). As for the crash, I'll investigate this, but as far as what I can see, the crash is caused by a threading violation in the bundled libradio plugin. It's calling XPLMRegisterFlightLoopCallback from a background thread, which the latest release of X-Plane now enforces more strictly. I'll take a look and see what I can do with it. It may be worth trying the C23 again, after it's moved. I've seen X-Plane do some weird corrections when moved out of the Program Files folder.

Honestly, I have no idea. But I have a feeling the new log file will tell us. Can you post another one and I'll take another look. Make sure it's a fresh one from the crash.