Crashes On X-Plane 12.4.0

[Goran_M]

On 4/28/2026 at 11:34 AM, Jabari said:

Late reply... X-Plane is installed in a folder named Program Files on my D drive, not the C drive.  Removing the libradio.plugin folder allowed the plane to load, but the flaps issue in this post remains and now the mixture doesn't work with the Honeycomb Bravo Alpha.  It seems to be related to the flaps issue, as it "flutters" (for lack of better wording) the same way the flaps do.  I fix was featured in that same post over a year ago, it must be a real pain to deploy updates...

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

6 hours ago, CaptTJ said:

I also have the issue, XPlane crashes before plane loads. Waiting on a patch or information. Worked fine before the upgrade to 12.4

Did you try removing libradio?  

[CaptTJ]

I removed Libradio and everything works good. No flutter on mixture or flaps. 

[lawson-stone]

I hope the update will give us much brighter illumination of the instruments. Otherwise this is among my favorite planes on XP12.4

[Jabari]

On 4/29/2026 at 3:28 AM, Goran_M said:

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?  

Removing libradio fixed the crashing issue, but now I have no audio in the plane.  With all the issues, this plane has become unusable (none of them exist with other aircraft).  The list:

• Flaps issue as documented in the other post
• Mixture issue as mentioned above (and shown in the video) - most critical
• No audio
• Gizmo is being deprecated (not a huge deal at the moment)

 

 

Edited May 16 by Jabari

[lawson-stone]

Having to use Rosetta already more or less eliminated this plane from my sim flying. That's too bad, because I like the plane and it flies nicely. But too many boxes to check in order to run it.

[Goran_M]

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.