All Activity

That did it. All's well now. I still am not a fan of needing to run Rosetta, but I do love this airplane and your sim is fun to fly, so I will wait eagerly for the update. For now, I'm happy and glad things are working. Thank you for hanging in there with me and resolving the issue.

@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.

Here's a fresh log.txt I feel badly about the amount of time this is requiring. Thank you for the effort and support.I Log.txt

@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.

Hi Cameron, thanks for getting back to me. Somebody in the HotStart Discord mentioned this, but this isn't the case on Windows - at least not for the installer that I downloaded for the TorqueSim CitationJet 525. That explicitly removes Gizmo without any prompt. I double and triple checked to make sure I wasn't haphazardly clicking "Next". Is there another installer that I should be using?

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.

Hi Bodo, yes, this is a shortcoming of the current model, the wings are "mirrored"...not ideal. It is on the list for improvements, but no ETA on those. For now it is what it is .

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.

@Goran_M It seems like you are offering support for this plane now. Can the fix mentioned above be deployed?

Here is the complete log file... Log.txt

This has always been the case since day one of the transition.

I believe there's new youtube video from Q8 Pilot discussing any progress on the IXEG, enjoy.

Hello, after changing PCs and using a new Windows activation key, my Challenger 65 is locked. Can you do anything about it? THANKS. roberto67

Pils is correct, this seems to be a Zink internal bug: 2026-02-28 20:54:19 CL650[xplane.c:3010]: BOOT: fscu_init 0:01:56.101 E/Zink: Plugin Challenger 650 by Hot Start tried to allocate 64.00 b but failed because the system is out of memory. Detailed memory diagnostics [...] 0:01:56.101 I/GFX/VK: Budget information: 0:01:56.101 I/GFX/VK: Heap 0: budget: 10.02 gb (10757341184 bytes), usage: 822.84 mb (862810112 bytes) 0:01:56.101 I/GFX/VK: Heap 1: budget: 15.21 gb (16335620096 bytes), usage: 259.52 mb (272125952 bytes) 0:01:56.101 I/GFX/VK: Heap 2: budget: 171.20 mb (179516211 bytes), usage: 214.00 mb (224395264 bytes) We asked X-Plane for 64 bytes of memory on the GPU during fuel system computer unit (fscu) initialization - probably to create some small scratch buffer, idk - and X-Plane, despite having literal gigabytes free, told us no. That's not on us, that's on X-Plane. It then initiated sim shutdown and finally blamed us for its own screwup. Classy...

Ok, no more answers. I can't redownlaod the product (I won't receive the confirmation email, or get it too late, for the two factor authentication). Opened a support ticket, but don't get any answer. Absolutely no support, plus the unabilitly to have access to the products you've paid for, I guess I won't spend any single cent anymore on products offered on this platform. Good bye.

To me it looks like a sim VRAM allocation bug. Maybe worth reporting to Laminar. Try running without Zink enabled.

Log.txt

Hello, Recently my sim started crashing when loading CL650. It's saying that is because XPLM_PLUGIN_XPLANE. It did not happened before. Thanks for the help

I have no earthly idea why it decided to work this morning. thanks for your efforts to help!

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.

Rosetta install was successful but XP12 still crashes to the desktop.

Thank you, I'll try it. What I don't understand is why it has run just fine for so long before now.

Hello there, I noticed that some available repaints unsing two wing textures similar to the left and right engine. As I wanted to paint a different left wing texture because of the reg on botton I noticed that there is only a common 733-wing.xxx texture which will be used. Is this a bug or intented? I cheched the objects folder and saw that there is a "B733_rightwing.dds" next to "B733_Wings.dds". Is there a possibility to differ the wing textures due to painting a reg on the left one?

Hi there, I've owned several products from the X-Aviation store for a few years and have recently installed some again since Gizmo is now on the way out. I have some observations and feedback regarding the user experience of the newer plugin. With the IXEG having not received an update in a number of years, it's understandable that it still depends on Gizmo. However, the installer of the CitationJet 525 (downloaded the latest installer as of 27th Feb 2026) automatically removes Gizmo which isn't a great user experience as any updates that run through the installer will knock out Gizmo, requiring manual intervention every time. Process: Install IXEG 737 Verify that Gizmo64.plugin exists under Resources\plugins Install C525 Observe that Resources\plugins\Gizmo64.plugin is automatically removed (no prompt or confirmation) Can this behaviour be removed from the installer or at least have the user prompted as to whether they wish to remove Gizmo64? The second point around the X-Aviation plugin is that it comes with a massive performance hit when the activation window is opened. Here's a screenshot from X-Plane's microprofiler which shows that an overwhelming majority of the frame time is spent on XPDDrawSingleWindowHook. This reduces my FPS from 120FPS to a whopping ~25FPS The obvious solution is to close the activation window once all is activated. However, as Gizmo64 was quite a problematic plugin in that it would cause problems for many SASL and XLua based aircraft, I thought it best to raise this too in case there's any downstream impact later into the flight. I've never seen a plugin cause such a reduction in FPS by drawing a UI.