Flight-Tracker-StreamDeck VS AutoHotInterception

https://flightsim.to/file/3178/flight-tracker-streamdeck-plugin plugin is great and allows you to control default values like radio and sqk through a numpad, as well as displaying and controlling simvars like throttle position, throttle outputs and other switches. These would control most things on most planes that uses default variables, but not planes with custom variables like fenix. Controlling fenix requires another plugin on top of that.

I used this plugin. Then I download a profile for aircraft I fly most. https://flightsim.to/file/3178/flight-tracker-streamdeck-plugin

And some day you'll decide you want TrackId, a StreamDeck, buton boxes... Here, i'll give you a teaser to stir the pot.

Is using something like https://github.com/nguyenquyhy/Flight-Tracker-StreamDeck to read icon states or just ingame keyboard shortcuts?

This guy is doing great work.

For example: I am playing MS Flight Simulator on Shadow, and have installed this StreamDeck plugin to see real-time stats (ex: FPS) of my game. However, the Stream Deck's indicators will lag by 30-60 secs or more.

You can achieve that with Autohotkey and AutoHotInterception, which allows you to capture keypresses at a driver level from a specific input-device. I used that for turning a bluetooth numpad into a little macro pad.

I've had some good experiences with using Luamacros to intercept a second keyboard and forward the keypresses to autohotkey like this: https://miquelvir.medium.com/secondkeyboard-1c39e52e023b

Apparently there is also this: https://github.com/evilC/AutoHotInterception

AutoHotInterception might be a workaround for this. The docs cover how to do everything.

This may be what you're looking for: https://github.com/evilC/AutoHotInterception

I believe this is what you're looking for. Sorry, I haven't tried it yet.

I haven't used it yet, but I found AutoHotInterception which uses an "interception" driver to get you hotkeys with a lower level of keyboard interception - this will likely work for Dosbox, though it might be a bit excessive. I'll play around with it tomorrow and see how it works.

I would suggest using an alternative shortcut as CTRL+ALT+DEL is not something you generally want to mess with - but this library https://github.com/evilC/AutoHotInterception may help you achieve your goals, it is capable of blocking the input of ctrl+alt+del...

AHK can't differentiate between keyboards by itself. You need to use AutoHotInterception to find out which keyboard sent the data.

I used AutoHotInterception for making a cheap little bluetooth numpad into a macropad.