Matchstick

Any progress on this in the last couple of months ?

Support for the SteamDeck + is currently being added to Spad.Next to allow you to not just read the switches and dial but to dynamically update the button display including simple gauges. (The Loupedeck will hopefully be getting support for setting labels and images as well at some point)

I was hoping that the RC5 fix to scenery data might be related to the CTD problem and have resolved it but that doesn't look to the the case - just tried with a fresh XP12 RC5 copy with only the G500 installed and I'm still getting the crash. Is there any progress identifying what might be causing the issues coming at the problem from the RSG side ? (included a copy of log.txt from the clean instance just in case there's something useful there) Log.txt

No problem, if you need any more information or logs please let me know.

That's odd as a number of people have found the G500 started CTDing when it's powered from XP12b5 (?) onwards. I've just tried a fresh install of G500 with an empty mod Plugins, just default files in Custom Scenery folder and only the LR aircraft and C172-G500 in the Aircraft folder and it crashed with the attached log.txt generated when the battery was turned on. Is there any additional logging for the G500 (or possibly OpenGPWS plugin) that can be enabled to see what's happening ? Log.txt

That's very odd as it's causing a CTD on mine and a number of other user's PCs very shortly after powering on - seemingly at the point the left display would start showing the map.

I notice the XP12 screenshots include the G500 but it seems that the current G500 version isn't compatible with recent XP12 beta releases - does this suggest there's a XP12 G500 release on the near horizon ?

Is there any news on the G500 rework ? The XP12 specific version of the Beech Sundowner is apparently about to release with a G500 cockpit so it'll be a pity if we don't have the working avionics to go with that.

I understand that but the v2.0.2 release is usable in XP12 so I'm trying to find out if there's any information on whether this patch changes that.

There's nothing in the patch notes on XP12 compatibility for this patch, so should be assume it's kinda working in a similar manner to v2.0.2 ?

I'm seeing problems with the G500 stalling then crashing the sim after it's powered on in an aircraft with the latest beta 0.3 release.

That's great - if it's a paid update that's fine to keep the Saab going on for another generation.

Is it safe to assume the Gizmo licensing system is working XP12 as well then ?

That's great - there are options in the GTN config to allow use of the redundant space on the screen to show extra data blocks instead so no display real estate need be wasted

That's sounds very cool Do you have a feel for a timescales for the changes yet ?

The Mu-2 does have support for the RealsimGear G500 software so if you've got that you can use it to control the VS speed as you'd expect.

Hi, is there a way to select which NAV radio feeds the AP/FD when using the OEM version ? Cheers

I'm doing a first high level flight and I'm finding I can't come close to the torque numbers specified in the PoH. I'm at FL240 at -30C which is approximately +2 ISA and according to the ISA Recommended Cruise power table (PoH 4-32) at 96% Prop RPM I should hit the 650deg EGT limit at about 72% Torque and with 11,500lb hits airspeeds of 1939 KIAS and 270 KTAS. Obviously I'm going to get something a bit less than those figure because temp is slight above ISA, but in reality I can only get 54% Torque before hitting the EGT limit which corresponds to 170 KIAS and 247 KTAS. Even if I ignore the EGT and push the throttle all the way forward I can still only get to 58% Torque - well short of the PoH value. Has anyone else tested their performance against the PoH and had better luck, in which case do you have suggestions for what I'm doing wrong with the engine or maybe how I'm misreading the PoH ?

Honestly I'm quite happy now with the way the throttle is at the moment

Personally I use the switch at the bottom of the left throttle axis as the beta toggle and finds that works take well for me, not least because I always know what the position is the physical throttle lever is when switching. The reversed direction in beta mode is a little odd but didn't take much practice to get used to it.

If I may be entirely selfish for a moment what I'd personally like to see are Emergency Stop On/Off events (or a Toggle with a dataref to show current state) that can be use to move the Prop levers from Taxi to Emergency Stop and vice versa. That way on my Honeycomb Bravo I can set the Prop levers with the curve starting at 10% as suggested in the documentation and then use the switch below the bottom of the lever arc to trigger the Emergency Stop events. Now, I've no idea if this is a) practical from a coding position or b) any use to anyone else who isn't using this specific throttle quadrant, but I though I would throw the idea out there just on the off-chance it is

No problem - this plane is well worth a bit of effort helping to test and identify any issues

I've tried it with 1 and I'm still seeing the same thing. As you suspect I am using the standard hardware toe brake mappings - is there a different mapping to be used instead ?

It appears that using the mouse wheel on the AP Pitch Wheel rotates it to full deflection with a single click in either direction which is a bit of an extreme reaction and the only way to recentre it (or just move it less than full deflection( is to drag it with the mouse.

Always a relief to know other people are seeing an issue rather than it just turning out I'm doing something wrong I see what you mean about the starting and stopping or jerking motion.