Matchstick

The issue isn't the time that's being taken. The issue is the refusal to talk to customers about what stage the project has got to (and I use "refusal" deliberately there).

I'm honestly at a stage where I would like more information on how the development progressing than a bland assertion. I'm not asking for a release, I'm not asking for a release date but I would like some actual idea of where in the development process the project is.

Patience is not an infinite virtue, especially if someone feels it is being taken advantage of.

There quite a lot to be said for something that can actually be flown now, not some utterly indeterminate time in the future (if ever).

Are you still getting the Level 2 authentication failure message in the Log ?

Have you tried opening a different plane first then opening the DC-3 ?

What I did was start a flight with the 737 which worked fine, then went back to the main menu and started the flight from a different location, which then fails to load the aircraft properly because of the Level 2 authentication failure. On my system at least, even with no plugins enabled this error appears 100% reproducible.

Just retested the problem with the plane failing the Level 2 license check the second time it's loaded within an XP session but this time with no plug-ins installed and it's failed again. So at least for me this issue doesn't seem to be a plug-in conflict. Zipped copy of the log file attached. Log - 737 no plugins.zip

That's exactly what I see. First time I load the plane it's fine if i go back to main menu and start a new flight in it and systems are broken. Checking the log I can see that first time I load the plane the license check is fine, but when I reload I fail the level 2 check. 1st load 0:04:02.116 G64: warn: We have received:[lss.xa.validation] msg:[8599407] param:[-1701809504] 0:04:02.117 G64: debug: IXEG: ----Beginning License Check Sequence---- 0:04:02.117 G64: debug: IXEG: defaulting IXEG license to OFF before activation checks 0:04:02.117 G64: debug: IXEG: Staging kill functions in case license invalid.... 0:04:02.117 G64: debug: IXEG: Verifying Level 2 backup before initiating checks..... 0:04:02.117 G64: debug: IXEG: Level 2 backup ready and standing by, Beginning license checks 0:04:02.117 G64: debug: IXEG: --------------------------------------------------------------- 0:04:02.117 G64: debug: IXEG: Checking for valid license via Level 1..... 0:04:02.117 G64: debug: IXEG: Level-1 license check good. Requesting Level-2 check.... 0:04:02.117 G64: debug: IXEG: Performing Level-2 check 0:04:02.118 G64: debug: IXEG: Level-2 check good 0:04:02.118 G64: debug: IXEG: Level-1 and Level-2 two-factor authentication good. License is valid 0:04:02.118 G64: debug: GK: Auto license update is on. 0:04:02.118 G64: debug: GK: License days remaining: 14.97 - No update required. 0:04:02.118 G64: debug: GK: Update required when <= 2.00 days. 2nd load 0:34:25.186 G64: warn: We have received:[lss.xa.validation] msg:[8599407] param:[1167274512] 0:34:25.187 G64: debug: IXEG: ----Beginning License Check Sequence---- 0:34:25.187 G64: debug: IXEG: defaulting IXEG license to OFF before activation checks 0:34:25.187 G64: debug: IXEG: Staging kill functions in case license invalid.... 0:34:25.187 G64: debug: IXEG: Verifying Level 2 backup before initiating checks..... 0:34:25.187 G64: debug: IXEG: Level 2 backup ready and standing by, Beginning license checks 0:34:25.187 G64: debug: IXEG: --------------------------------------------------------------- 0:34:25.187 G64: debug: IXEG: Checking for valid license via Level 1..... 0:34:25.187 G64: debug: IXEG: Level-1 license check good. Requesting Level-2 check.... 0:34:25.187 G64: debug: IXEG: Performing Level-2 check 0:34:25.188 G64: debug: IXEG: Level-2 check FAILED 0:34:25.188 G64: debug: IXEG: Killing critical functions, kill set [1] 0:34:25.188 G64: debug: IXEG: Killing critical functions, kill set [2] 0:34:25.188 G64: debug: IXEG: Level-1 PASS / Level-2 FAIL. License invalid A zipped copy of the log is attached Log - 737 reload.zip --Edit-- I need to do some tests see in that's a plug-in conflict behind the issue but it's getting on for midnight here so that'll need to wait till tomorrow.

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.