All Activity

The missing key is related to the plugin I told you earlier. Everything else is just a warning. No big deal.

After checking my Log.txt, I also noticed a few warnings related to the DA40NG plugin and sound configuration. For example, the log shows: WARNING: A plugin has called X-Plane SDK functions before the simulation was fully loaded PLUGIN: rsg_da40ng.xpl There are also FMOD sound warnings such as: snd error in file DA40NG.snd (around line 744) invalid command trigger Additionally, I saw warnings like: Warning: unknown line BEGIN_SOUND_ATTACHMENT I’m not sure if these are related to the missing ignition key issue, but they appear every time the aircraft is loaded.

Oh no Thank you for telling me what the issue is. Have to see, how to workaround it. At least we know what the issue is.

This plugin is likely causing issues: Loaded: D:\Xplane12/X-Plane 12/Resources/plugins/GndHandling/

A lot of errors in the log! Log.txt

If it were possible, I would insist on a refund. I uninstalled and restored this mod a lot of times. After uninstalling, it works for some time. One day i start it and key is not there, and its not working. Sorry guys, this sucks. I have a lot of aircraft, i had never ever any issues, some are updated 3-4 years ago and still working like charm. Thats simply bad. Not going to buy any other aircraft from this dev. Sorry. This is the 4th or 5th time i uninstall it...

Hi, I am using X-Camera and noticed that the views go through the aircraft and do not look acceptable. This happens only with this aircraft and X-Camera. Unfortunately, X-Camera seems to be the only application that works with TrackIR vs. using the X-Plane views. This is very annoying and it distorts the views. I tried to adjust, recalibrate, and then readjust the views several times but this is the result. I am using a 34-inch monitor, not sure the monitor has anything to do with this b/c no other aircraft has this bizarre behavior. Thoughts?

The fact it’s 15° (ISA temp) makes me believe it’s not simulated, as you suspected.

Hi all, Late adopter to the Challenger 650 here and really enjoying it so far. I did notice something that really makes me wonder if I have something turned off. All the temperature simulations are working great in the study panels. Except for the ones on the batteries. They seem to be stuck at 15.0°C. I realize there’s a lot of thermal mass in these batteries, but I actually abused the airplane by soaking it in -60°C and also starting the APU several times in a row. Both the main and the API battery stayed at a solid 15.0°C throughout. Is battery temperature not simulated right now or is there something on my end? Thanks in advance and kind regards

Another weird issue.. All power is off but the Red tail lights remain on and show double.

Not working for me.

Hi team, It's been a while since a response in this forum.. I have the latest version of the BN-2B and have found that the Headset doesn't work. Any one else with that issue.. Note I'm in the latest version of XP12.4.0 and is applicable with all the BN series.

That's great to hear. You guys are doing an amazing job.

OK, thanks for information. Would love to see it as improvement in the future.

His last on this was 7 months ago, unless you found a later one

To the people that is too anxious: As former developer of biological simulations, I can tell that the computer programer can´t answer nothing about dates, because himself ignore when the work will be ready to release. Unexpected problems and new improvements are items that can alter the schedule. I prefer a developer that delay the release to set the best product possible, than other that release a program undone to catch the money early. Be patient, I'm sure that the CL650 will have the best weather radar.

The installer is designed in a way to be as least intrusive as possible, so no registration keys or configs. What dictates that prompt being shown is if the installer detects Gizmo being installed at all. Why it can't search and see it on your setup is beyond me at the moment.

It's a fair observation as I am a software engineer. I am equally as stumped with this one. The installer is able to see Gizmo to the extent of being able to delete it but without the prompt. I've recorded a video of the installation process. The part I don't show is the license check for obvious security reasons. GIzmo is deleted almost immediately. The rest of the video is largely boring as it shows the rest of the install but I wanted to leave it there to show that no additional steps were being performed. This video was recorded with the TorqueSim CitationJet 525 1.1.0 Windows installer. Does this installer retain configuration files or registry keys that might bypass the option or are there possibly some edge cases baked into the code that would short-circuit the logic around displaying the prompt?

I have just had several people on Windows test this. All of these people confirm the dialog appears. You are also the first person I have ever had mention this doesn't work in over a year of this being implemented, so I'm not really sure what's unique to your system to prevent it. Perhaps some kind of unique casing paths, or anything else I'm not considering. It would not shock me considering you're in tune enough to fixate on the profiler in X-Plane.

Please, take a look at this:

Correct... It crashes before the cockpit loads.

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