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.

@Jabari Checking in to see if you still want this resolved.

Your log confirms what Cameron mentioned. The Sundowner C23 v2 uses Gizmo for its systems. Gizmo64 is an x86_64 binary, and your M2 Mac needs Rosetta to run it. Without it, Gizmo64 fails to load entirely, and that's why you're getting no sound and non-functional cockpit controls like the fuel selector. The aircraft shell loads, but none of the underlying logic is running. Regarding the crash when trying to run X-Plane under Rosetta, try the following: 1. Open Terminal (Applications > Utilities > Terminal) 2. Paste this command and hit Enter: softwareupdate --install-rosetta 3. Let it complete, even if your Mac says Rosetta is already installed. This forces a clean install. 4. Right-click on X-Plane 12.app, select "Get Info", and check the box for "Open using Rosetta" 5. Launch X-Plane That's the cleanest solution I can suggest for the time being. Running X-Plane under Rosetta has no negative effect on X-Plane itself or any other add-ons. If X-Plane still crashes under Rosetta after that, the crash would be on Laminar's end rather than ours, and I'd recommend reporting it to them through their bug reporter. But in most cases, step 1 resolves the issue when Rosetta wasn't properly installed to begin with. I'll be looking at converting the code to run natively under ARM in the near future, which will eliminate the Rosetta requirement altogether.

I'll be happy to help you, but you'll need to upload a log file. What you attached is a MacOS alias/bookmark file.

You obviously haven't been to our discord where we answer countless questions. The 2 most common ones? When is the 650 update coming out and when is the TBM update coming out. Both questions are always politely answered. Your comment is out of line and not true.

Hi Jabari, Thanks for the report. We're looking into this. To diagnose the crash properly, we need a complete Log.txt from the session where the crash occurred. The one posted appears to be a partial capture. To get a clean log: 1. Start X-Plane 2. Load the Beech Sundowner C23 G5 3. Attempt to load a new flight until the crash occurs 4. Immediately after the crash (or on restart), grab Log.txt from your X-Plane root folder before loading anything else Please either attach it directly to this thread or paste it in full. The more complete the log, the faster we can track this down. Thanks for your patience.

Correct. Challenger is top priority. Saso has done some amazing work on it.

Model is finished. Textures are finished. Saso is doing his best to take care of minor issues with the 650, one of which is getting the weather radar added to it. Once he finishes those, he'll send me a new TBM build so I can start initial testing in X-Plane 12 with animations and making sure textures look good. To sum up, as of this post, all artwork is considered done.

Your log shows the CL650 plugin is loading without issues. The problem is on the X-Aviation/Gizmo licensing side. The relevant lines from your log: GK: 404: license database GK: Empty license file. Defaulting to login page. GK-IPC: No license: (hotstart.challenger650) GK: No valid auth token, manual login required. Gizmo is unable to locate a valid license and is failing to present the login prompt. Activation and licensing are handled entirely by X-Aviation, so please contact support directly for further assistance. You can reach them here: https://www.x-aviation.com/catalog/contact_us.php

Please post a log file when it happens again. It needs to be a log file from the actual crashed session.

@Max2307 Just a heads up. Confirmed. This is a bug. When the "Rudder Controls Differential Brakes" option is enabled in DC-3 Settings, the code overwrites the toe brake axis values every frame, even when the rudder is centered. That zeroes out any input from your brake pedals, which is why the axes appear completely dead while button-bound commands still work. As a workaround until the update: Open DC-3 Settings, go to the Options tab, and uncheck "Rudder Controls Differential Brakes." Your toe brake pedals should work normally after that. You'll lose the rudder-to-brake taxi assist, but you'll have full differential braking through your hardware. The fix is already in for the next release. The differential braking option will no longer interfere with toe brake axes. When the rudder is centered, your pedal input passes through untouched, and when the rudder is deflected, the two inputs are blended rather than one replacing the other.