davidinbasel

I'll do as you suggest and force the non-repeat. Note however that I didn't specify any repeat in the UI when setting up the ,mapping.

Thanks for following that up John. As you suggest I'll use keys that MSFS2024 recognises, until ASOBO restores F13...F19. As for the odd treatment of line 90 in the [Button.aircraft] sections, I don't see what I've done to have it seen by FSUIPC as a command or instruction, rather than a comment line. (The comment is simply a reminder to myself that B,0 in the following lines references button 1 on the Honeycomb Alpha yoke) As previously, I really appreciate the rapid responses to my questions! New .INI and a matching (!) .log file attached ... I've now qualified for 4.88MB of attachments, so no need to fiddle with file sharing platforms 🙂 FSUIPC7.ini FSUIPC7.log

Addendum: I tried again without any profiles defined in the .ini and with key defined only for one preset (the G1000 presets, as it happens, but that's presumably not relevant). Same result. So my concern that I was screwing up the construction of profiles and causing this oddball problem thereby seems unfounded.

Files are here: https://limewire.com/d/e6e0bce0-bf92-4d70-820b-ab749829c8df#D6OT5IAAqPohu2d1tDvBy66C2KUACryZcDJP07QjdoQ The log here now without Input Events. You'll see towards the end of the log that key presses are registered for 2 of the 7 keys. At 294047 I press VK=106. I then press in sequence 127, 128, 129, 130, 12, 111 and 106 again. Only VK=111 and VK=106 are received by MSFS. So it's not a case of keys being pressed but assignments not triggered -- the key press is not seen by MSFS, even though it was seen by the FSUIPC UI when creating the mapping. (Not surprisingly, the Console shows the same behaviour: pressing keys 111 and 106 creates log entries, as expected, but nothing at all happens when pressing 127, 128, 129, 130 or 12. By the way, I tried again after removing from .INI all the lines created by the UI for these key presses. Same result, except that this time the log shows key presses for 111 and 106 "but not programmed" with no entries for the other keys. Thanks for looking into this John

I thought I would post the .INI and .log file separately, as both individually exceed a 3.25kB limit on attached files (even when compressed). But I see that using a followup post does not relax that limit. (Why is the limit so constraining?) How do I post the files? Cheers, David

Further to my project to control the GPS using keys and buttons, I am trying to map several keys to GPS actions, using FSUIPC's preset options. I do this separately for a GNS530 (as optionally installed in the A2A Comanche) and the NXi G1000 (as installed in the Asobo C172SP Cargo), using Profiles. My problem is that while the keys I use are trapped by the UI, and successfully associated with the correct presets in a new .INI file (with one possible exception, see below), after closing MSFS and FSUIPC then starting a new session, keydowns/ups are only received by MSFS for two of the seven keys I had mapped. I will send a FSUIPC.ini.new file to show the result of the mapping. All looks good (to my eyes) except that the key number used for the Clear key above the numpad is "12" which, according to the Advanced User Guide, is the NumPad 5 key (with NumLock Off). Yet the key label shown in the UI for that key is "Clr" which matches with the graphic on the key face and with what is received by the Keyboard utility in Microsoft PowerToys. The other six keys I am using are registered in the UI and in the resulting .INI file with key labels and numbers that match the Advanced User Guide's list, so apart from the oddball 12/Clear/NumPad 5 confusion it does not seem that my German Apple extended keyboard layout is preventing the proper behaviour of the other keys. Note that there are no conflicts with MSFS key assignments. None of these key are assigned in MSFS. The log file I will send separately (logging InputEvents, Extra actions as well as Buttons and Keys) shows the result of the test from around 236110. At that timestamp a VK=111 is received by MSFS, and at 237688 VK=106 is received. No other key strokes are received, despite me cycling through all seven keys (in the order 127, 128, 129, 130, 12, 111, 106). As an aside (I presume), the log file reports (at the start of the file) numerous duplicates of present names and some incorrect Calcodes for presets. This is new, and suggests I need to fix something. But none of the presets reported as being duplicated or having incorrect Calcodes are presets that I am trying to use. Anyway, my problem is that keystrokes are not being detected, not that presets are not functioning correctly. I note that I have seen discussion (around December) of keystrokes not being received by MSFS. Initially it was thought to be related to a startup timing sequencing problem, but the last I saw was that John had discovered another issue with the way different components were communicating. I am presuming that Version 7.5.1, which I am using, has the necessary fix? Another thought I had is that I may not be setting up profiles correctly. This is my first use of profiles, and the first time I have had problems with keystrokes not being received by MSFS. Any connection? Grateful for any suggestions. Thanks hugely, David

Thanks so much John, those adjustments fixed my problem. Works as intended now (after fixing some joystick button numbering errors the relevant part of the .ini file, errors that were producing unintended results). If anyone wants to follow my approach, please look at the .ini file below--especially lines 91-94 in the [Buttons] section--and not the one attached to my original post. Thanks again, including for the fantastically quick response. David FSUIPC7.ini

I am trying to control the NXi G1000 MFD FMS knob with a rotary encoder from Desktop Aviator. (I'm testing on the Asobo C172, but want this to be generic across G1000 equipped planes.) The Desktop Aviator unit has 6 encoders, 5 of which map successfully to OBI1, OBI2, Heading bug, AP Altitude select, and radio frequency virtual avionics control knobs. All the virtual avionics knobs I want to control are concentric dual action with an outer ring for whole unit or faster index changes and an inner ring for decimal or slower index changes. To achieve this with single action encoders I condition (via FSUIPC.ini) the respective FSUPIC controls on a flag state maintained in a virtual joystick button, where the flag state is switched by holding down (or not) a button on my flight yoke. This works fine on the first 5 encoders mapped to the OBI1...radio avionics control knobs. The G1000 MFD FMS virtual knob also has a concentric dual action arrangement, with the addition of a push button action on the inner ring/knob. FSUIPC 7.5.1 (paid, registered) seems to have the relevant presets for controlling the G1000 MFD FMS virtual knob (AS1000_MFD_FMS_Lower and _Upper for _DEC, _INC and _PUSH), and various forum posts indicate that these G1000 presets are also valid for the NXi version of the G1000 (if I'm reading the posts correctly). Moreover, assigning a key to the MFD_FMS_Upper_PUSH,1 preset via FSUIPC works properly in making the cursor active/inactive in the Flight Plan page of the G1000, indicating that (a) at least the _PUSH preset is correct and (b) the fsuipc-lvar-module is present (in the Community folder along the ...Limitless... path) and correct. BUT while the key-based push of the FMS knob works, I cannot get the rotary encoder right/left inputs to actuate the MFD_FMS inner and outer knobs. The relevant commands were inserted in FSUIPC.ini via the user interface, so the syntax should be correct (?) -- see attached. And while the log (a) shows no faults in loading up the WASM module (17585 Calculator Coder presets loaded and available for use) (b) shows that the rotary encoder "button presses" are received (see lines 789797-795469 of the log, reporting joy 3 and button 10 and 11 changes) it also shows (c) nothing triggered. Any ideas what I could be doing wrong? Thanks, David For correspondence with PeteDowson.7z