These are the Support Forums for FSUIPC and related products.
These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, but are now no longer available.
Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.
Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE
NumPad keys are always recognised as 'Num1' etc. even with NumLock off
Hi all. First of all I'm new to posting on the forum, so I hope I'm doing this correctly.
I am trying to replicate a control method that I used successfully in FSX/FSUIPC4 in MSFS2020 removed link To select the ATC window responses, eg '1' I had the Numpad keys assigned for this, but only when NumLock is off, eg when I strike key '1' the keycode sent is '35' as opposed to '97' when Numlock is on. This was achieved by setting up a yoke button as a 'PTT' the action of pressing it being to temporarily turn NumLock off whilst I held the button down & therefore change the code that was sent from the keyboard. When the 'PTT' button is released NumLock is turned back on for my usual use of the Numpad with the excellent 'NPCNumPadControl' LUA script functions & works fine. But try as I might, in MSFS2020 I cannot send anything other than keycode 97, whether NumLock is on or off! It always sends '97', never '35', so I cannot reproduce what I thought was quite an elegant method. If anyone can shed any light on this, or indeed offer any suggestions as to a way to achieve my goal, I'd love to hear from you as I'm tearing my hair out 🙂 Thanks.
Yes, I have checked this (in both MSFS2020 and MSFS2024) and you are correct. The only numpad key that is giving the correct key when numlock is off is the '5' key.
But FSUIPC receives the key presses from MSFS (via SimConnect), so it is MSFS that is sending the wrong key. I will raise this with Asobo. I will keep you updated.
Regards,
John
Thank you John. From your description I can appreciate now how it's MSFS returning the incorrect value, as opposed to me not programming FSUIPC properly (which is a relief). I had great success with the control panel that my late Father & I constructed when using FSX with FSUIPC4 & was somewhat surprised that I couldn't simply get it to work with MSFS2020 & FSUIPC7, as everything else moved across perfectly. Just for info., here's a couple of snippets from the logs that I took from FSUIPC4 & FSUIPC7 when troubleshooting the issue. Hopefully they will adequately show you how I'm using button 26 on my yoke to effect that temporary disablement of NumLock. That button 26, apart from PTT, also invokes a second level of button operation on the rest of the yoke using FSUIPC's 'Conditional Press' function. It'll be interesting to see what Asobo come back with. I'm just a little surprised that no-one else seems to have posted this as an issue already. I scoured the web, but found nothing. Thanks again for your prompt response. Philip
If you want to show me anything from the logs, please just attach you (complete) FSUIPC log file. Images (and videos) don't tell me anything, and with my bad eyesight are difficult to read. They also take up too much storage space. If I ever need to see an image, I will ask for it (which is extremely rare!).
And I understand the issue. and this is relatively new as I checked the difference with NumLock on/off just a few weeks ago. I suspect something has changed in the last update (or two/three - ...) . I have already reported several issues related to key reception which Asobo have acknowledged. I have added this issue to the same report - please see https://devsupport.flightsimulator.com/t/msfs2024-su6-valid-input-strings-for-key-input-reception-change-using-simconnect-mapinputeventtoclientevent-ex1/18357/23
Regards,
John
Posted by: @phlexx64I constructed when using FSX with FSUIPC4 & was somewhat surprised that I couldn't simply get it to work with MSFS2020 & FSUIPC7, as everything else moved across perfectly.
Thats quite a surprise really! MSFS is a verry different beast compared to FSX, especially in complex aircraft. Many assignments to standard FS controls don't work that well in MSFS2020, and even less in MSFS2024. There are many new control methods that replace the standard controls - lvars are heavily used, hvars, bvars and Input Events. And its always a good idea to check for any available 'presets', which can use all methods of control.
Posted by: @phlexx64Hopefully they will adequately show you how I'm using button 26 on my yoke to effect that temporary disablement of NumLock. That button 26, apart from PTT, also invokes a second level of button operation on the rest of the yoke using FSUIPC's 'Conditional Press' function.
But this is not relevent. The issue, as I see it, is that MSFS is always returning a key press code as if NumLock is activated, even when it isn't. I presume if it was returning the correct keypress code, your issue would be solved.
Regards,
John
