IronCroptop

I haven't had a chance for an extensive flight but I did a quick test with the latest X-Plane beta (12.1.2b1) and the crash to desktop when popping out the G1000 PFD/MFD on this aircraft appears to be fixed. I didn't see anything in the XP release notes that specifically matched this issue but there were a couple of crash fixes listed so I'm hopeful. Will do an extended test after work today to see if the crash is truly gone. EDIT: Nope. I was wrong. The crash still happens. Guess I just got lucky on that first, short test.

If you're using MobiFlight to control your X-Touch Minis, then you need to merge the config files for the DCP/CCP and the X-Touch Minis together. If you look on Avionique's Installation page for the DCP/CCP, there are instructions on how to do so in the "Supplementals Procedures" section (expand the "Multiple Panels" section). https://avioniquesimulation.com/dcp-ccp-panel/

Here's another log.txt. Submitted the crash report to LR as well. Not that this information will be meaningful or useful in any way but this is _only_ happening with this DA40NG. My TorqueSim SR22TN can pop out the PFD and MFD without issue as can all of my Aerobask aircraft. Log.txt

I did, indeed cancel that particular crash upload -- this log.txt was from the fourth or fifth time that XP crashed. I did submit crash reports to LR on the first three crashes though.

Just upgraded my DA40NG to the 1.1.0 release. Aircraft activation went off without a hitch and I can load into a new flight. But as soon as I attempt to popout either the G1000 PFD or MFD, X-Plane crashes pretty much immediately. I've disabled all plugins (except for Gizmo) to no avail. Log.txt attached Log.txt

Message received. I won't be making the mistake of trying to install future versions. Thank you for the lessons.

Uh... No it's not. I did NOT drag _anything_ from my X-Plane 11 install. I downloaded the Beta release and (attempted) to install it into my X-Plane 12 folder. I'll cop to not having seen the "known issues" list on the Discord post (since I wasn't on Discord) but I refuse to be made an example of for something that I absolutely *didn't* do.

Thank you both. I was able to get the activation error cleared up by following @Pils advice. I've also joined the Discord so that I can keep on top of further beta announcements. Thank you for the help.

Good morning. I downloaded the SR-22 G1000 Beta for X-Plane 12 from my X-Aviation account last night and attempted to install it. My first attempt failed after the installer had downloaded the core files and was attempting to unzip the package. It reported that the destination folder (in my case "D:/Gaming/X-Plane 12/Aircraft/X-Aviation") didn't exist or was not writable. The Airplane directory in my X-Plane 12 has correct permissions (and other aircraft have installed without issue). So I manually created the "X-Aviation" directory and tried again. This time, the installer was able to finish the install. So I fired up X-Plane and attempted to finish activating the aircraft so I could take it for a short test flight. When I load the SR22 I get two errors. One reporting a missing file (".../TorqueSim SR22TN/objects/EFFECTS/SR22_IVS_IN.obj") and one reporting an issue with the sound bank (".../TorqueSim SR22TN/fmod/SR22TN.snd sim/flightmodel/failures/prop_ice"). Soldiering on, I dismissed these errors and attempted to activate my license but was met with the final error (which I concede is a Gizmo error): In case the red text gets munged by the jpg compression, it reads: "251 .580 http API call_back: function handle:: 6: [string "core/utils_api.lua.gfys"]:113: stat(x) failed: (D:/Gaming/X-Plane 12/X-Aviation)" I've tried deleting the install and re-installing to no avail. Any suggestions on additional steps to try would be appreciated.

To be fair, you could skip that 7 hour video. There are 6 more videos in that playlist that are only about 30 minutes each that walk you through the various stages of getting off the ground. In addition to Graeme's excellent videos. you could check out the videos posted by Foxtrot Alpha Aviation who is a real-world Challenger pilot. Here's the playlist for his excellent tutorial series of videos:

In SPAD.next, you need to configure the button to have a "Button pressed" and a "Button released" event. Map the same command to both events and in the "Configure Simulation Event" popup, set the "X-Plane Special Value" field to "Begin Command" for the button press event and "End Command" for the button released event.

Latest video in the Foxtrot Alpha Aviation series has been posted: Definitely recommended viewing.

SPAD.next can definitely set dataref values rather than send commands and when it's the only option, I do just that. However, I've learnt that sometimes changing a dataref isn't necessarily enough since there may be other datarefs that are triggered when a command toggles on and I didn't manage to find them all -- or the right one). That may just be a case of me doing it wrong. As for triggering on load, I don't know offhand if SPAD.next will set datarefs based on switch position when it loads or only when the switch moves. The programming is tied to "events" but I'm not sure what actually triggers those events. I'll ask about that on the SPAD.next support Discord.

@AtlasI'm in pretty much the very same boat (plane?) as you. All of my flying until now has been in various GA aircraft with the TBM900 being the most "complicated". The CL650 is a whole new, intimidating beast for me. I, too, found large parts of the checklists to be largely confusing given my lack of knowledge and understanding. In addition to the great advice and references that have been posted above, I'd recommend looking at the videos posted on YouTube by "Foxtrot Alpha Aviation". He's a real CL650 pilot and is posting some very in-depth looks at various procedures and walkarounds. He hasn't posted a full startup video yet. His latest walked us through up to and including the start of the APU. But the level of detail he's providing is excellent and I've learnt so much from him already. I'm eagerly awaiting his next video.

I'd like to chime in on this thread in support of discreet ON and OFF commands although I'd like to see them be supported _in addition to_ rather than _instead of_ TOGGLE. Having a discreet set of commands definitely makes it easier to implement control mappings in SPAD.next and other control devices. You don't have to worry about checking additional datarefs for the current state of a switch in order to keep your hardware and software switches in sync. But I'd hate to see the TOGGLE option go away since for each of us that want a discreet command, I'm sure that there is someone else who would prefer to have a TOGGLE. Choice is good!