khwsommer

Yes, version 2 of the FlightFX HJet was released about 3 weeks ago. It's a great improvement and is compatible with AAU1. Here are the key bindings for version 2: https://docs.google.com/document/d/1VRvjF4Tt90XmvKy2bpPn96S5TPyFAokm/edit Thank you. Klaus

Great. Thank you. Klaus

Thank you, John, for your detailed comments. Yesterday, I found a solution. Using UCR (see below) one can reassign any key from any keyboard (or any control device for that matter) to any key combination (or any control device action) you want. If you want to use it, you will probably need to use "blocking" in UCR for the input keyboard, or you will get both outputs (from the second keyboard and the UCR assignment). https://github.com/Snoothy/UCR I have used free key combination for MSFS and within FSUIPC I then assign these to any available presets, in my case for the FlightFX HJET. Works without a flaw. I think this is a really efficient (= cheap) way of using extra numpads or keyboard for controls in MSFS. Thank you for your patience and support. Klaus P.S.: The FlightFX HJET HA420 presets in events.txt are no longer up-to-date for version 2 of the FlightFX HJET HA420. To help a little bit, I intend to put all the new ones into my myevents.txt and then send it to you. You may then consider including them in a future update.

I just wanted to confirm what Al found. The attached version from John fixes the problem that after editing events.txt or myevents.txt, FSUIPC will not start, depending on some random character constellations in the files. Like Al, I spent the better part of a day to think that it cannot be possible that a program (FSUIPC) will no longer start right at the beginning of the log file, after it worked for more than 10 years. But the attached FSUIPC.exe fixes it. I think this change would be very good to include in the next version of FSUIPC. Thank you John for your support and Al for spending time as the "detective" 😉. Klaus

Thank you, John. I know you are very busy and I feel bad about bothering you. But there is no one else 😉. Here my findings: HidMacros alone generates "z" in Browser, Text Editors, etc., but "Num1" in MSFS and FSUIPC. (I am not surprised about FSUIPC, since I understand FSUIPC gets the key from MSFS via Simconnect). HidMacros plus UseKeyboardHook=Yes still only gives "Num1" in MSFS and FSUIPC (and "z" in editor etc.). To me that means that either FSUIPC gets the keystroke before HidMacros or on another way than HidMacros or UseKeyboardHook=Yes is not doing anything in this situation. I believe this is the end of the road or do you have any other suggestions? Thank you. Klaus (P.S.: NumLock=Off on the main keyboard (no HidMacros) generates strange behavior on the second numpad. Some keys come through but there is always a NumLock=On on keypress and NumLock=Off on key release in addition. With HidMacros, the key is converted with KeyLock=On on the main keyboard and without that it's again pretty strange. So this will not help. P.P.S.: Since HidMacros is no longer supported for MSFS, it cannot use Simconnect to connect to MSFS, but otherwise works just fine with other programs. But Simconnect should not be needed anyway, since the hooked and reassigned keypresses from HidMacros worked just fine in FSX (and now also in editors/browsers, but not in MSFS.)

Thank you, John, for your reply. It took me a moment since I was travelling. I think I failed to describe the issue properly. I think in Windows, MSFS and FSUIPC only one Keyboard is recognized. If you plug in a second one, it just acts the same as the normal first one and cannot be distinguished from it. HidMacros is a program that does something very similar to FSUIPC with UseKeyboardHook=Yes, namely it catches all keypresses before they go to Windows (hooking). But in contrast to FSUIPC, HidMacros can identify the keyboard the keypress is coming from and it can convert the keypress to whatever you want, in my above example convert "Num1" from the second keyboard/numpad to "z". So "Num1" on the second keyboard (or numpad) is different from "Num1" on the the first normal keyboard and generates e.g. a "z" through HidMacros while the normal keyboard still returns only "Num1". This can be successfully confirmed in any text editing program. The problem is that when using MSFS with or without FSUIPC, this hooking action of HidMacros does not seem to work like in a text editor. Both keyboards only generate the "Num1". (I assume without knowing enough that Simconnect catches the keypress before HidMacros does) So I wonder whether a) FSUIPC could also distinguish between the two keyboards (source code of HidMacros is available at Github: https://github.com/me2d13/hidmacros ) or b) FSUIPC could read the output from HidMacros instead of the keystream that just generates a "Num1". I tried UseKeyboardHook=Yes for that reason but it does not do that I hope this is a better description of the issue. It would be so nice to use cheap additional keyboards or numpads like the one in the link below to have many additional keys available for MSFS functions. I hope you can help. Klaus https://www.amazon.de/dp/B01N7WOXLU?psc=1&ref=ppx_yo2ov_dt_b_product_details https://www.hidmacros.eu/whatisit.php

I am trying to use an extra keypad to control some MSFS functions, e.g. Autopilot normally toggled by "z" on the keyboard. I have set UseKeyboardHook=Yes in my FSUIPC.INI Also, I am using HidMacros to send a "z" when I am pressing the "1" key on my extra numpad. In MS Word, it all works well (i.e. it shows "z" when I press "1" on the extra numpad), but in MSFS and in FSUIPC I only get "Num1". So, I assume, the keystroke still goes through SimConnect as "Num1" and not through HidMacros and UseKeyboardHook as "z". What is my mistake? Thank you in advance Klaus