ark1320

The key codes that FSUIPC7 'sees' through SimConnect for the Page Dn, Page Up, End, Home and Insert keys seem to be incorrect. For example, the log file shows FSUIPC7 sees a key code of 99 for the Page Dn key, but it should be 34. Key code 99 is the Num3 key code. I discovered this because the keys listed above have been triggering a Lua script even though the FSUIPC7 key assignment window, and the FSUIPC7.ini file, show these keys are not assigned. Al

From what I can tell, the ipc.ask() lua function does not currently work in MSFS. Is there another way with MSFS to get a multi-digit numerical variable value entered by the user into a Lua script at script run time? I'm trying to write a script that asks the user to input a number value of their choice between 1 and 999. Best wishes for the holidays! Thanks, Al

Ron, If this is a default aircraft and you switch on the strobes just using the default Asobo control, I assume a mouse click, does the battery still get turned off? If not, I would guess you have a FSUIPC setup conflict somewhere. Al

Yes, I saw they were not listed. I can certainly get by without them. Al

In case you missed my late edit above, two keys that don't work are the stand alone <, and >. keys. Al

BTW, although the current SDK shows the Shift, Ctrl, and Alt keys as 'fail', they all seem to work as part of a key combination, which is good news. Two keys that don't work are the stand alone < and > keys. Just FYI. Really appreciate the super support! Al

YES-- arrow keys work!! Thank you Thomas and John! Al

Agree, makes good sense. Al

OK, I see, thanks for the explanation. Seems strange and unfortunate to me that they would not make all the keys commonly found on a keyboard available via SimConnect. They certainly make use of the arrow keys in the MSFS default key bindings, so why they would not think these keys would also be useful to third party applications via SimConnect is baffling. Making it clear certain common keys won't work with FSUIPC7 will likely help prevent users from spending a lot of time trying to figure out why something doesn't work. And hopefully save you time by eliminating the need to respond to posts like this one! 🙂 Maybe some kind of popup " Key not available" message when a user tries to assign a non-useable key would be good. Thanks for the help, Al

BTW John, this issue with the arrow keys seems to be the same problem as we had with the Numpad number keys in that arrow key (or the arrow keys in combination with Shift, etc) control assignments work IF FSUIPC7 has focus. Al

John, In the FSUIPC6 Key presses drop down controls list I have the stand alone Left and Right arrow keys assigned to Heading Bug Dec and Heading Bug Inc, and the stand alone Up and Down arrow keys assigned to Ap Alt Var Inc and Ap Alt Var Dec, and all works fine. That is what I wanted to do in FSUIPC7, but no luck. If when convenient you could let Asobo know maybe they will eventually fix this. I would expect the arrow keys are used by many with FSUIPC. Thanks for the feedback, Al

John, As best as I can tell, the Up, Down, Left and Right arrow keys still do not work correctly in FSUIPC7. I assume this is a continuing Simconnect problem -- can you confirm this? As a test, I wrote a very simple Lua script that does nothing but display a few words on the screen, and assigned the Up arrow key to activate the script -- doesn't work. However, if I assign a non-arrow key, it works. Thanks, Al

I now understand where the Right Shift + Num6 as described above likely comes from. On the Numpad, Num6 and Right Arrow are the same physical key, what you 'get' depends on whether NumLock is on or off. But I was not using that key at all as described above, but rather the stand-alone Right Arrow key. So it is not clear to me why MSFS identified the stand-alone RIght Arrow key as Num6 based on the timing of the Right Shift+Right Arrow combination. Al

When I want to enter the key combination Right Shift+Right Arrow under FSUIPC7 key assignments, I've noticed that I have to make sure I hit the Shift Right key a 'split second' before Right Arrow, or else FSUIPC7 only see the Right Arrow key. Conversely, in MSFS under the Keyboard Controls setup, when entering that same key combination into the Search by Input field, if I hit the Shift Right key a split second before Right Arrow, what gets entered into the search field is Right Shift+ Num6 ?? I don't know if this is a MSFS bug, or 'my' bug somehow., or what. However, if I hit the Right Arrow key a split second before Right Shift in MSFS, then the correct Right Shift + Right Arrow combination shows up in the search field. So MSFS and FSUIPC7 respond differently to this key combination depending on the split second timing when hitting the two keys. I'm posting here hoping someone might be able to help me understand all this. Thanks, Al

I check regularly but somehow missed the update to FSUIPC7 v7.02 -- just tried it, WORKS!! 😀 Thanks very much, Al

Hi John, Since a couple of months have passed now, I wondering if you have ever received any acknowledgement from Asobo that they are aware of the Simconnect/Numpad keys problem, and maybe some indication of when it might be fixed? Thanks, Al

Reinhard, Thanks for the detailed info -- very nice. Al

An interesting thread -- thanks! Al

Thanks to both of you for the great support once again!! Al

I do need to make more use of macros. Can a Name.mcro file have more than one Lvar listed in it, for example: [Macros] 1=L:PITOT_L=Toggle 2=L:PITOT_R=Toggle For some reason I only see the first Lvar listed in the P3Dv4.5+ FSUIPC6 keys drop down list. Thanks, Al

I try to avoid having to use the mouse and have lots of scripts for controlling switches and buttons in different airplanes and of course they all use different Lvars, and scripts for calling up different checklists which are aircraft specific, and also more general scripts (like moving an aircraft to a new location in the air) that apply to multiple aircraft. And yes, there are ways to consolidate. Typically what I do now if necessary is to convert the separate scripts into functions which are then then combined into a single script and selected based on an assigned parameter ( ipcPARAM, flag, etc) value. So, for example , I now have a controls script for the Lear35 that has 47 different functions in it. Given the difficulties of making a change in the Lua scripts limit as outlined above, I agree it does not seem like a reasonable course of action at this point, especially since apparently no one else has raised the issue. The idea of tying scripts to an aircraft profile seemed like a nice organizational feature so I decided to ask to see what might be involved. As I said, it was just a thought. Thanks very much for the responses and explanations. Al

Yes, I have run into the 128 Lua limit a number of times. When you have scripts for multiple planes the total can add up quickly. If something like I described was to be implemented, you could add a prefix or postfix to the Lua scipt name to identify the profile. For example, Lear35_checklist.lua might become [L35]Lear35_checklist.lua where the profile name is L35, etc. Or perhaps profiles could be numbered or lettered with a single character, and you would prefix the script name with the associated number or letter. Just a thought. Thanks, Al

I understand that currently the number of Lua files is limited to 128 (0 to 127). I was wondering if in a future version of FSUIPC this limit could be extended by designating certain Lua files to be aircraft (profile) specific Lua files. Such files would then be listed under something like [LuaFiles.profile_name] in the FSUIPC ini file. Thanks, Al

Good idea, thanks! Al

Does the ipcPARAM parameter value supplied with a key or button assignment have to be an integer, or can it also be a decimal value? Can it be a string? Thanks, Al EDIT: From what I can tell, ipcPARAM has to be an integer.