Goran_M

This is definitely a false positive. Windows Defender sometimes flags X-Plane add-on files, especially plugin files, because they're unsigned or uncommon rather than because they're actually harmful. When Defender quarantines one of them, the aircraft ends up incomplete, which is why X-Plane is reporting it as corrupted. To fix it: 1. Make sure your download came directly from your X-Aviation account, not a third-party site. 2. Delete the partial SR22 folder from X-Plane 12. 3. Open Windows Security > Virus & threat protection > Protection history, find the SR22 item, and choose Restore (or allow it). 4. Add an exclusion for your X-Plane 12 folder under Virus & threat protection settings > Manage settings > Exclusions. 5. Re-run the installer. If it still fails, contact X-Aviation support directly. They can confirm the file and help sort it out.

MacOS 27 introduced a stricter check in its library loader, and it's rejecting the TBM 900's main systems plugin before it can start. That's why the aircraft appears but nothing works. The other plugins in the package load fine, so your install and license are both OK, and reinstalling won't help. This needs a fix on our end in the form of an updated Mac build. We're working on it for the upcoming update. In the meantime, the aircraft runs normally on macOS 26 and earlier if rolling back is an option for you. Sorry for the hassle, and thanks for being the one to flag it.

In the last 8 months, the DC3 has undergone a major upgrade and this problem no longer exists. More information will be posted in the coming weeks.

I almost forgot about this. In all honesty, it's quite low on the list of priorities at the moment. It still needs to be researched, and at what severity the wing flex happens and under what conditions. Once all the important updates are out of the way, and there are a few, we'll take a look at some cosmetic improvements, including the wingflex.

I can't tell you with any certainty. Activation is fully handled by support. If it's the same problem, my guess is yes, it's an activation issue.

The DC3 is not activated. We don't handle activations. You'll need to contact X-Aviation customer support for this one. https://support.x-aviation.com

Thanks. It was actually my very first add on that I made. To be honest, I cringe when I see that model, but it was XP9 standards back then.

Nie mogę powiedzieć tego na pewno, ale jesteśmy zobowiązani do opublikowania aktualizacji w ciągu najbliższych kilku miesięcy.

The C23 is going to be updated to address all the problems you're mentioning. Unfortunately, it's not going to be a quick fix, as it will require a code rewrite. I rarely give out hard ETA's, but realistically, given what we have lined up at the moment, we should have an update out before the end of the year.

Trwają prace nad aktualizacją, która sprawi, że TBM będzie kompatybilny z X-Plane 12. Wszelkie problemy powinny zostać rozwiązane w aktualizacji.

Thanks for the report and for attaching the log. The cause is almost certainly a dataref that recent X-Plane 12.4.x updates renamed or removed. Your log has a couple of those rename warnings logged at startup, unrelated to the DC-3. The v2 of the DC3 code predate those renames, and we have not patched the legacy version against the latest sim changes. We do have a new DC-3 in the works. Right now our engineering effort is going there rather than back into legacy v2. Apologies for the inconvenience in the meantime.

An update is being worked on. Are you having the flaps and mixture problems when not using the honeycomb controller? Did you try removing libradio?

V1.9 of the Challenger was just released, so the TBM will slowly start getting some attention.

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.