Matchstick

Anyone else seeing problems the second time you load the plane in an X-Plane session ? When I do that I get the plane loading with all power switches off but with the AP and Radio Display numbers illuminated and turning on the actual power switches does nothing. (Also as a data point when the plane does load correctly I also see the issue with the engine coming up to speed almost instantly after start)

things are almost certainly still being prepared for the release. The LES DC-3 v2 wasn't released last week till after midnight GMT so there's plenty of time left before anyone can start complaining it's late.

The required datarefs are listed in the pinned post so if you have Spad.next it's pretty simple to set up - I've publish a code snippet for the HC Bravo for the that presses the paddle and moves the mixture when you move the corresponding lever and should be easy enough to do that with another joystick. It's probably also pretty simple to set up something in XLUA to do the same thing but that's outside my skillset so I can't really help with that.

The economic reality is the upgrade was complex and seems to have taken longer that IXEG hoped so they can't afford to have done all that work for free.

Thanks for those and I've used them to create a basic profile for Spad.Next that does the job pretty well. If anyone else with the HC Bravo and Spad wants to try it out it's been published as snippet #9368

I use a Alpha and Bravo for the Mu-2. It's a slightly odd setup for the throttle as I use the switch at the bottom of the throttle axis to switch between the forward and backwards sections of the in-cockpit throttle. In means when you are in the backwards section of the in-cockpit throttle the controls are reversed (pushing forward on the physical lever, pulls the in-cockpit lever back) but it wasn't difficult to adjust to that and it does mean I get to use the full range of the physical lever in each mode and there's no risk of a sudden shift of in-game throttle when switching "mode" In terms of what I set for controls, the Alpha has standard Roll and Pitch axis mappings, nothing out of the ordinary there at all. For the Bravo axis, I have Lever 1 & 2 set to Throttle 3 & 4 and Levers 3 & 4 set to Prop 1 & 2 respectively In the Throttle Buttons (GA) section I have Button 3 - Toggle thrust reversers Button 4 - Toggle thrust reversers #2 Button 5 - Move left condition lever to EMER STOP Button 6 - Move right condition lever to EMER STOP Finally in the Mu-2 preferences panel I have Auto-stop power levers at detent - OFF Power Level Upper Limit - 0.5 Power Level Lower Limit - 0.4 Hardware Power Detent Ratio - 0 Show Ghost Throttles - Always I can't guarantee this setting will work for you but maybe they'll be a starting point for you to work out your preferred config ?

Thanks for that. I use Spad.next for advanced control setups so I should certainly be able to assign hardware axis to a custom dataref with that.

Other planes have managed to do in cockpit levers where the level falls into the detent position that's the best match for the physical throttle position. At the very least we need some information on the correct Datarefs/commands to map to if we can't directly use an axis

I've mapped the standard X-Plane Mixture controls onto levers 5 and 6 of my Honeycomb Bravo throttle quadrant and while the engine's fuel flow seems to be changing in response to the physical levers being moved the controls in the cockpit aren't moving so it's pretty much impossible to tell if the lever is actually in right detent. Is this a bug or am I doing it wrong and there is a better way to map the levers ?

Can we also read into that that there's an official ARM friendly Gizmo release coming soon ? (The DC-3 doesn't seem to work with the experimental Gizmo64 23+ version that's been used to allow Apple Silicon support with some other X-Aviation planes)

Is there any way to customise the data sources that the G500 reads to get the data to display on screen ? (I'm thinking in particular of the slip indicator on the PFD)

Looks like this bug may have been fixed with the latest 12.06b6 release.

there is an experimental version here https://blog.x-plugins.com/2023/02/gizmo64-version-23.html But it's unsupported and if anything doesn't work and you need to revert back you'll potentially have to reinstall aircraft that use the Gizmo plugin to ensure they are running the expected version

With the pretty stark limitations of the Garmin G1000 in XP (even with custom extensions) has any consideration been put to creating an analogue version like the Da40 TDi in the future ? It could also be a great showcase for the G5 and G500 avionics options ?

I've noticed there's a really sharp drop of the nose when disconnecting the AP at decision height during an ILS approach. Is anyone else seeing this and if so is this deliberate (ie a "feature" of the real plane) ?

I'm very much enjoying the Da40 but I have noticed that the noise cancelling effect continues even after you disconnect the headphone from the centre console. A very minor bug of course but thought I would mention it.

I haven't found one yet and I'm desperate to know what the buttons on the armrests do !

Then maybe it's time to start talking to customers about when we'll start to see the results of the development ?

Unfortunately at the moment the devs attention is focused on the CL650 and the TBM900 isn't getting the attention it could do with right now.

One problem I'm spotting with this new version is I cannot get the FD/AP to engage. I've checked the AP Turn wheel is centred (to the extent of checking the dataref value in Spad is 0) but it nothing seems to work. Is there a trick I'm missing ?

If the plane is dependent on third party plug-ins that haven't been updated with Apple M1/M2 support then there's not much anyone other than the plug-in developers can do. However if the Mu-2 is only reliant on the Gizmo plugin there is now an experimental version of that that's supposed to now include native Apple ARM support https://blog.x-plugins.com/2023/02/gizmo64-version-23.html I've been using that for a couple of months on PC and it's worked with all the X-Aviation planes I've tried including the Mu-2 so stability seems to be OK on PC at least.

In the meantime has any consideration been given to a very basic patch to at least allow the plane to fly in XP12 ?

Thranda stopped working with Carenado back in 2019 and moved onto doing their own planes. https://forums.x-plane.org/index.php?/forums/topic/197780-thranda-and-xp11-carenado-c208/#comment-1803422 They do still work with Just Flight on their XP aircraft and just released on the first XP12 updates for the JF planes. As for Carenado themselves there's zero evidence they have any interest in X-plane at all at the moment.

Some of the XP Carenado planes had the distinct advantage that the conversions were done by Thranda who were able to improve on the originals (and also open them up to for Simcoders REP support).

I can definitely appreciate that with the stock aircraft but I personally lean towards a little more latitude when it comes to optional system and add-ons - allowing people the option to choose to some extent what feels right for them to fly, whether that exactly matches the real world or not