Hi!
It appears that somehow I managed to have some keybinds, despite being set to the default layer, be on a bewildering "Layer 0" - distinctly not layer "Default" where there is no layer number visible.

In my screenshot "AP_APR_HOLD" wont fire if not on default layer. "VR RESET" will as per design. Interestingly all the Layer 0 commands are on the Honeycomb Bravo.

If I create a new assignment with the Bravo the command is assigned "Layer 0". If I create it with Midi or Yoke it is working with the default layer not showing this ominous "0" and firing at all set layers. If I edit the keybind and change the layer (either in the overview or edit popup) it doesn't change appearance nor behavior. If I reassign a working "default" keybind created for the Midi and reassign it to the Bravo it also suddenly is a "Layer 0" keybind.

When I make a new Config in Offline Mode the problems seems to disappear, but would not know how to get this humongous Config into a new file (apply template or config will just keep on doing the Layer "0" thing).

I even checked in the ConfigDatabase (a copy 😄 ) - it says "<ControlLayer>0</ControlLayer>" in those tho example assignments. Also there is no out of place layer visible under in the file or in the GUI under Templates>Manage Control Layers.

Have you got a guess as how to resolve this conundrum? 🙂 Many thanks in advance!

 

 

 

Short Addendum: It only concerns the AP Panel Buttons on the Bravo interestingly. If I reassign anything with the Flap Lever everything is fine.

I don't think that the problem is actually with the layers. Do you have the exact same button assignment on other layers too?

Looking at your screenshots it seems like somehow you managed to set a Joystick device, but the dialog is picking up Keyboard events. That is very wrong.

Personally, I would just delete these two assignments and create them again from scratch. Did you try that? 

3 minutes ago, Lorby_SI said:

I don't think that the problem is actually with the layers. Do you have the exact same button assignment on other layers too?

Looking at your screenshots it seems like somehow you managed to set a Joystick device, but the dialog is picking up Keyboard events. That is very wrong.

Personally, I would just delete these two assignments and create them again from scratch. Did you try that? 

Yes, one of the the two is a button on the Yoke, the other on the Bravo.

I have just realized that, while fiddling with getting a screenshot done, I has temporarily assigned the keyboard keys (Prt Scr), a mishap of the moment. Usually it is POV 180 on the Yoke or something like that. Hence the confusion in the screenshot, sry.

I have tried to reassign the Bravo ones, with no luck - except if I do it in a completely new config.

29 minutes ago, JulezHaze said:

I have tried to reassign the Bravo ones, with no luck - except if I do it in a completely new config.

"Reassign" meaning that you've deleted them and then created new assignments?

42 minutes ago, JulezHaze said:

Hence the confusion in the screenshot, sry.

That's as may be - but this cannot happen. When a joystick is selected in the Device box, the dialog can't be picking up keyboard input. Something is not right with these two, which is why they must be deleted.

Edited December 10, 20241 yr by Lorby_SI

1 hour ago, JulezHaze said:

Short Addendum: It only concerns the AP Panel Buttons on the Bravo interestingly. If I reassign anything with the Flap Lever everything is fine.

That doesn't make any sense, sorry. I don't know what to tell you. Conflicting assignments anywhere else? In AAO, in the sim, in other software (MobiFlight, SPAD, FSUIPC, device driver ---?

1 hour ago, JulezHaze said:

be on a bewildering "Layer 0" - distinctly not layer "Default" where there is no layer number visible.

The reason is this: 

The layer a button is on is only "default", when you don't have anything else assigned to the same button on another layer. OK? As long as this button is alone and on layer 0, no "0" is shown and it is "default". The moment you assign the same button on another layer, the "0" appears with the one assignment and "1/2/3" for the other one. This is done to remind you that the button assignment is no longer "alone", and that it will only trigger when the layer 0 (= "Default Layer" at the bottom) is set explicitly.

Edited December 10, 20241 yr by Lorby_SI

Btw, when you are using virtual keys a lot, consider scripts that set the focus on the flightsim process first.

Example:

(FOCUS:flightsimulator2024) (SPLIT:100) (VKD:42-170-160) (VKD:46-174-67) (SPLIT:100) (VKU:46-174-67) (VKU:42-170-160)

This script sends Shift-C to the sim. After typing in the first part, you can get the VK codes using the "Insert vKey" button. The (SPLIT:100) parts are important, because MSFS doesn't understand this virtual keyboard strokes when they happen too fast.

That way you make sure that the keystrokes don't end up in Nirvana.

3 hours ago, Lorby_SI said:

The reason is this: 

The layer a button is on is only "default", when you don't have anything else assigned to the same button on another layer. OK? As long as this button is alone and on layer 0, no "0" is shown and it is "default". The moment you assign the same button on another layer, the "0" appears with the one assignment and "1/2/3" for the other one. This is done to remind you that the button assignment is no longer "alone", and that it will only trigger when the layer 0 (= "Default Layer" at the bottom) is set explicitly.

Oh i feel humbled, yes that makes all the sense, explains everything and I consider my issue null and void, thank you! I couldn't see the forest for all the trees.

 

2 hours ago, Lorby_SI said:

Btw, when you are using virtual keys a lot, consider scripts that set the focus on the flightsim process first.

Example:

(FOCUS:flightsimulator2024) (SPLIT:100) (VKD:42-170-160) (VKD:46-174-67) (SPLIT:100) (VKU:46-174-67) (VKU:42-170-160)

This script sends Shift-C to the sim. After typing in the first part, you can get the VK codes using the "Insert vKey" button. The (SPLIT:100) parts are important, because MSFS doesn't understand this virtual keyboard strokes when they happen too fast.

That way you make sure that the keystrokes don't end up in Nirvana.

Thank you very much for pointing that out, I do have some usecases for that, namely Statesaving and SkyDolly. Luckily I did figure the FOCUS command is what it needs 🙂 But i did did change some SPLIT commands to WAIT, because with SPLIT I experienced that the script would skip over parts that followed the VKD part (where SPLIT is automatically inserted). It does work all the same, but maybe I did something unwise here.