Cessna C172 Avionics Master Switch Not Working With Logitech Switch Panel, Logitech Driver

Bug Reporting Hub Aircraft & Systems
, , , , ,
1

ISSUE DESCRIPTION

Description of the issue:
Avionics switch inop in C172 when using Logitech switch panel with Logitech driver

If applicable, which aircraft is experiencing this issue:
Cessna C172

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
Not using any mods

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Issue occurs every time.

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Ensured the latest Logitech driver is installed and started; no other mods present
  2. Operated the Avionics Master switch on the Logitech panel - inop. Clicked on the Avionics Master switch with the mouse – it works.
  3. Tried above in both the C172 “Basic” and G1000 – Same results
  4. Removed Logitech driver from loading and experimented with Lorby Axis and Ohs using the software’s built-in implementation of the Logitech driver enabled. Results were exactly the same.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:
Logitech Switch Panel and Autopilot (“Multi-Control”) Panel
Saitek Cyborg 3D USB joystick
Thrustmaster T-Flight rudder pedals
Logitech throttle quadrant
TrackIR

[PC Only] Are you using Developer Mode or have you made any changes to it?
No

[PC, MSFS 2020 Only] Are you using DX11 or DX12?
N/A

[PC Only] What GPU (Graphics Card) do you use?
Nvidia RTX 2080 Super

[PC Only] What other relevant PC specs can you share?
32 GB RAM
M.2 NVMe SSD
AMD Ryzen 9 5900X CPU

[END OF FIRST USER REPORT]

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?
•

Provide extra information to complete the original description of the issue:
•

If relevant, provide additional screenshots/video:
•

2

I don’t have any Logitech devices but have had extensive experience with them.

You didn’t mentioned which MSFS24 device profile you are using or what controller event the Logitech Switch Panel buttons are assigned to. I suspect the buttons aren’t assigned to the control event you want them to have.

Actually, thinking about it and I understand the Logitech Switch Panel isn’t recognised by FS24. Check the Controller device screen and see if it’s listed. If not then you need to use a 3rd party app like SPAD.neXt or Lorbys Axis And Ohs.

3

Logitech hasn’t really updated their plugin in years. That’s not necessarily bad; the code has been stable and functional (if limited in customizability) and represents a known quantity. A plugin that’s effectively frozen in development makes implementation a bit simpler. It will always send the same outputs; they can be handled without fear of an update breaking things. If something breaks, then it’s on the end of the software that’s leveraging the plugin functions – that is, MSFS.

Each switch has a discrete output via the plugin; those need to be mapped to the correct inputs in MSFS and the aircraft. (From there, fancy things can happen, like triggering sound effects and animating controls in the virtual cockpit, and these are necessary for a complete implementation.)

It was all successfully achieved in 2020. Not at first release, but it was put on the list of things to do, and the implementation reached a feature-complete state. In 2024, the sim accepts the plugin’s outputs, but they’re not mapped the same as they should be in aircraft which are effectively carryovers from 2020. 2024 is supposed to be an upgrade to what we have in 2020; this is a regression.

Logitech panels, unfortunately, don’t appear in the sim’s control profiles like driver-based input devices, such as joystiks, pedals, and even the Logitech/Saitek throttle quadrant. Neither 2020 nor 2024 put the plugin-based panels into the control profiles to allow in-sim mappings. That’s always been a shortcoming, but at least 2020 and its aircraft could consistently handle the basic one-to-one mapping of the panels’ plugin outputs to their respective control inputs in the sim. Without AAO or Spad.next intervening, the expected behavior is for a given switch to actuate the corresponding control in the cockpit, if it exists – nothing more, nothing less.

The Logitech panels’ plugin is recognized by 2024 in the same way as in 2020 – if its executable is launched, then the sim can, and will, recognize its inputs. (Whether it does anything with them is up to programming and configuration of the aircraft files.) The autopilot/multi-panel is a good indicator of correct plugin loading – its display should turn on and several of its control buttons should illuminate partway through the loading screens; then the button lights should go off, leaving the display lit up showing zeros until it’s active once you start a flight. And it will reliably do this, at least, in 2024. The sim does "see’ the plugin. It’s further confirmed when you can actuate a common switch, like the Master switch(es) for battery/alternator power. That seems to work. So we’re left with incorrect mapping of the finer points of the individual switch outputs via the plugin being linked to correct actions in the virtual cockpit.

There’s always been an issue of reliably auto-starting the plugin; the exe.xml file (or lack thereof) is a perennial headache in the sim since 2020 and still with us in 2024. It can be bypassed by simply firing off a shortcut to launch LogiMicrosoftFlightSimulator.exe before launching the sim, or having the MSFS Addons Linker do it for you in its startup options, and there are probably other ways too. But that’s a solvable, and effectively solved, problem.

The main thing is that the plugin is either running or not, and if it’s running, then the sim is able to process the plugin’s outputs. 2024 is taking them as inputs but it’s not implementing them all correctly. Certainly, AAO or Spad.next can be used to intercept the panels and then produce customized scripted outputs – but the baseline complete 1:1 function of matching physical to sim controls is missing or irregular in 2024, while it manages to exist reliably in 2020, and has for most of 2020’s run.

4

Not having read the complete thread… a hint from my side:
there are different ways to trigger the avionics, depending on how the aircraft is programmed.
You might have to set up additional bindings.

Here are mine, and they work fine in the C172 and other planes so far.
(oh man…this binding menu is so screwed up… can’t even read the assigned button on my screenshot…)

Edit: but using Virpil equipment, so if that does not work out for you, it might really be a Logitech issue

C172 avionics
C172 avionics2098×874 238 KB
5

Since the switches work as-labeled, consistently ever since Logitech support was added in 2020, and 2024 does have Logitech plugin support, then it’s worth reporting as a bug.

And the 172 is kind of mild compared to what’s happening in the 152. The 172 just has a non-functioning switch. The 152 has a switch for the pitot heat that doesn’t work – but if left “on” then that switch (pitot heat) gets flipped off or on in the cockpit by flipping other light switches on the Logitech panel! That’s a separate reported bug.

You can leave the plugin out of the picture and use AAO or Spad.next to turn the panel into a scriptable/configurable device that directly interacts with variables in the sim – although the guys writing Stream Deck plugins might have a few things to say about inconsistencies in variable handling and running changes that break stuff that would be applicable here, too.

Unfortunately, the plugin doesn’t present the panel as a device that can have keymappings assigned. That’s limited to devices that use USB input drivers – like joysticks and throttles and rudders, like the Virpil gear.

6

Ok, there’s far to much to read and it sounds like an AI wrote it. No offence ment if not!
Anyhow, I think the main issue is that FS24 is incompatible with the Logitech plugin.

Perhaps, the bug report title should state that. It’s not affecting just the aircraft you identified, so generalise the title and mention the specifics in the content.

7

This is not only a Logitech problem but a MSFS24 behavior problem.

1- The default keyboard assignment CTR+X, is not working in many aircraft. The Logi Avionics master does the same. I have assigned keys to master 1 and 2 and not work.

2-In C172 classic and G1000, the CTRL+X or Logi Avionics master disconnects the Logitech radio and autopilot panels. In the C208, switchs on/off the main G1000 but not the central and copilot

3- In the Apache or Pipistrel works ok, same in Carenado Mooney (example of not default aircraft)

IMO, the problem is in aircraft with two Avionics switches/buses

Taking into account that the King Air has either no Speed reading nor engine data let´s wait a solution from Asobo.

Sent a Ticket to Zendesk

8

Do you have the same issue if you follow the OP’s steps to reproduce it?
•

Provide extra information to complete the original description of the issue:
•When I press the Avionics Bus 1 switch in the cockpit of the Cessna 172 Skyhawk (G1000 nxi) the switch moves but it does nothing, neither does the AV 1 breaker. The Avionics Bus 2 switch works and actually turns off the second Garmin.

If relevant, provide additional screenshots/video:
•

9

Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes, identical issue, OP described it better than I possibly could

Provide extra information to complete the original description of the issue:
•

If relevant, provide additional screenshots/video:
•

10

Hopefully that post can help: C172 and 208B Caravan avionics binding not operational - #23 by BinaryFiddle