I'm using a small programmable keypad (koolertron) to make extra keybindings in MSFS that I can quickly apply (change views, pause, un-pause, toggle head tracking, etc.). The keypad uses a version Bootmapper Client to program.

Problem: Microsoft doesn't consistently recognize my keybindings which are macros -- meaning, if I've created a macro in Bootmapper to trigger "Shift + E" (toggles head tracking on/off) in MSFS, MSFS recognizes it only about half the time and that seemingly haphazardly.

The binding is set up correctly in the Koolertron and it should work. But doesn't. This makes me think that it's a timing issue or something within MSFS receiving the signal.

By testing out the macro in notepad, I can see that if I press the Koollertron key triggering the macro, it does indeed trigger it and a capital E is typed in notepad. This is consistent.

So, the Koolertron is working correctly, the bootmapper software is working correctly. It's MSFS that is not interpreting the information correctly.

Does anyone have experience with this sort of thing? I've tried adding a delay after the "Shift", and also used a "Shift-down - E - Shift-up command", but as I say, it's just not reliable. Sometimes it works, sometimes it don't.

Any advice would be appreciated.

Do I need to add more time delay or create the string in a different way?

Thanks!

M.

I had a similar experience with a steel series keyboard. I found a 15ms delay worked most of the time. But complex or longer series ones needed longer delays. Shift e is not complex and a 5ms should work.

Edited September 14, 20232 yr by Maladoror

Maladoror,

Thanks for the help. I didn't check back on this thread, so sorry for the delay.

Where do you add the delay? Say, in a CONTROL (down) + Q + CONTROL (up)?

Do you add it after the Q or after the CONTROL (up)? Or after both of them?

Not where in the string the delay is supposed to go. I've been experimenting and getting close, but can't quite get it.

What I'm trying to do is assign this macro to turning follow drone mode off and on.

Thanks again for your help.

M.

Okay. I figured out what I was doing wrong. Just in case anyone else needs this info.

I'm using a Koolertron keyboard with AMAkeyboard Client (which is very similar to Bootmapper Client if your keyboard uses that).

When you want to program a macro key to, say, send "Control + Q" to MSFS, you have to put it in AMAKeyboard as:

• CONTROL (down)
• Q (down with .1 sec delay)
• Q (up)
• CONTROL (up)

My error was that I left out the "Q (up)" step.

Hope this helps if someone else is having issues getting macros to register in MSFS.

M.