C172 and 208B Caravan avionics binding not operational

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

3 tags are required - add them in the tag section next to the title above:

Feel free to delete this quote section after adding your appropriate tags.


ISSUE DESCRIPTION

Avionics switches for Avionics 1 and Avionics 2 cannot be keybound

If applicable, which aircraft is experiencing this issue:
Tested C172 and 208B Caravan default versions G1000

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

FREQUENCY OF ISSUE

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

REPRODUCTION STEPS

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

  1. Start C172 and/or 208B Caravan
  2. Try switches or keyboard bound to Avionics 1 and Avionics 2
  3. No cockpit reaction

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:
Keyboard, TB Yoke, Mouse

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

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

[PC Only] What GPU (Graphics Card) do you use?

[PC Only] What other relevant PC specs can you share?

MEDIA

Please add a screenshot or video of the issue occurring.

[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:

I believe this only affects the steampunk 172, G1000 I’ve been able to bind the keys, but they are under a different name than just the Avionics Master Switch, it’s under a really long name with Avionics Bus 1 and Avionics Bus 2

EDIT Not home right now to confirm, but I’ll be home in about an hour and can confirm the actual binding name.

I only have tried the C172 default G1000 and the 208B Caravan default G1000.
In 2020 I had them bound to Avionics Master 1 On and Avionics Master 1 Off and Avionics Master 2 On and Avionics Master 2 Off. Doesn’t seem to work in 2024. If there is a different keybind I would appreciate help,

This topic title doesn’t tell the true story. The switches are operational but the switch code has changed so your existing bindings have broke. You just need to map them to the correct ones.

This is just the tip of the iceberg so to speak. The issue is wide spread throughout MSFS2024 because Asobo have changed lots of the switch logic code. It’s of course fine and desirable to progress the platform but things like this can be made to still work as they were for the existing user base of several million pilots they just don’t seem to understand what backwards compatibility really means.

Don’t get me started on why Asobo thought this was a good idea but it’s the reality.

From another similar post…
Electrical Bus 1 to Avionics Bus 1 set - Button 17 (flip av 1 on)
Electrical Bus 1 to Avionics Bus 1 off - Button 18 (flip av 1 off)

Electrical Bus 2 to Avionics Bus 2 set - Button 19 (flip av 2 on)
Electrical Bus 2 to Avionics Bus 2 off - Button 20 (flip av 2 off)

Problem… I can’t find these bindings in the Xbox X bindings.

1 Like

Moved to USH since a solution has been marked.

Were you able to find the correct bindings? It would be appreciated.

Um, where has a solution been marked? I don’t see any solution.

I’ve got a switch box for the caravan and I’ve been trying to find a way to bind the avionics switches (and many other things on the panel I can’t find any bindings for). I’ve even delved into developer mode and as far I can can see there are no keybind events for them. I’ve been trying to use add-ons like mobiflight or axis and ohs and use the event names that are listed in developer mode for the switches but so far I have no luck.

If you are claiming this is a solved problem please point to the solution.

Post that was marked as the solution: C172 and 208B Caravan switches not operational - #5 by BinaryFiddle, but I guess OP removed it since they added that comment “can’t find these bindings in the Xbox X bindings.”. @BinaryFiddle : could you confirm ?

I did not find a solution. Although suggestions had been posted in another part of the forum. These did not exist or work for me. I could not find the suggested bindings in either the Xbox nor the PC. No solution yet.

Thanks for confirming, moved back to Bug Reporting Hub .

I don’t use the standard binding for switches really much at all. I’m a third party software guy and have the C172 ones working. I haven’t got round to ding the Caravan yet but I think it will be much the same.

I suspect the answer will be you need a third party app to bind them now. It’s called progress apparently. Even the sim default aircraft don’t always use the sims traditional K events in 2024.

One should not need to use a third party application for bindings and many third party applications are not available on the XBox. The correct bindings are in the ‘settings’…they just don’t work.

That may be so but it’s the reality. If you want to build any kind of serious home cockpit you’ll need to be on PC simply because the built in bindings only go a small way to controlling what you will need. This is more relevant for add ons but also applies to default aircraft.

The correct bindings are not in the “settings” menu contrary to what you believe. The plane is programmed differently. Go into dev mode and you can look at the variables yourself. You can argue about it all you want, however, you are wrong.

The bindings were in 2020 as Avionics Master 1 On/Off and Avionics Master 2 On/Off. They worked well in 2020. These same commands exist in the 2024 settings. I’ve noticed also that there are one or two bugs in 2024… perhaps this is an example of a bug.

I will wait to see if others agree and not rely solely on your opinion, but thank you for the reply.

It is not an example of a bug. The aircraft were redone and they were programmed differently. It is that simple.

This is the variable that is used for Avionics Bus 1 on the Caravan.

Unfortunately things were changed all over the place from 2020 to 2024 and on most of the aircraft.

Thank you. The variable is available…good. Once that variable is bound to the settings it will no longer be a bug. Not everyone has access to dev mode…i.e. Xbox X.

It’s not a bug. The current in sim binding operates the default k event and the new programming now doesn’t use that anymore. The only way for this to work the way it’s programmed is for the new ones to be added as new bindings which based on past history is unlikely. Please take it up with Asobo as to why and don’t shoot the messengers.

Oh, hey, it looks like you’ve identified the problem.

It seems the item in the control settings menu points to a variable that’s no longer valid. The key-binds/switch-binds are trying to adjust a value that no longer exists. I’d bet the other “impossible to bind” functions have the same issue.

We just need Asobo to have a look at these control binds and adjust them so they change the correct variable when the assigned key/switch is activated.

That doesn’t sound like an unreasonable ask, although I’m sure it’s low on the list of issues they are dealing with for this launch.

Until that happens, we are forced to use mouse interactions, looks like.