wulybugger

Thank you. With that information, I was able to get it to work as expected.

I've included the full .ini and .log files. I did update to try the AS1000 presets, but I see the same results. HOWEVER, if I assign these controls or presets to separate keys or dials such that I DON'T use compound statements, then everything works as expected. I ONLY see the issue when I try to combine these commands using compound statements. FSUIPC7.ini FSUIPC7.log

Here's what is in the .ini file for these controls: 46=PG,1,C65893,0 -{AP_ALT_VAR_DEC}- 47=CP(+G,2)G,1,C1016,0 -{ap alt var dec fast}- 48=PG,0,C65892,0 -{AP_ALT_VAR_INC}- 49=CP(+G,2)G,0,C1017,0 -{ap alt var inc fast}- Here's the log file showing me exercise the left/right turn of the knob, as well as pressing and holding the button and turning the knob, which should execute the fast events, but in BOTH cases where the condition is False and True, the altitude changes only be 100 feet, NOT 1000 feet for the case of the FAST events. In addition it can be seen that the Ctrl= switches from 1016/1017 to C65892/C65893 which represent the FAST and regular control events: 253985 Button changed: bRef=0, Joy=0 (G), Btn=1, Released 254953 Button changed: bRef=0, Joy=0 (G), Btn=0, Pressed 254953 [Buttons] 48=PG,0,C65892,0 254953 FS Control Sent: Ctrl=65892, Param=0 AP_ALT_VAR_INC 254953 [Buttons] 49=CP(+G,2)G,0,C1017,0 254953 .... Condition (+G,2) = FALSE 255031 Button changed: bRef=0, Joy=0 (G), Btn=0, Released 255438 Button changed: bRef=0, Joy=0 (G), Btn=0, Pressed 255438 [Buttons] 48=PG,0,C65892,0 255438 FS Control Sent: Ctrl=65892, Param=0 AP_ALT_VAR_INC 255438 [Buttons] 49=CP(+G,2)G,0,C1017,0 255438 .... Condition (+G,2) = FALSE 255516 Button changed: bRef=0, Joy=0 (G), Btn=0, Released 256125 Button changed: bRef=0, Joy=0 (G), Btn=1, Pressed 256125 [Buttons] 46=PG,1,C65893,0 256141 FS Control Sent: Ctrl=65893, Param=0 AP_ALT_VAR_DEC 256141 [Buttons] 47=CP(+G,2)G,1,C1016,0 256141 .... Condition (+G,2) = FALSE 256203 Button changed: bRef=0, Joy=0 (G), Btn=1, Released 256422 Button changed: bRef=0, Joy=0 (G), Btn=1, Pressed 256422 [Buttons] 46=PG,1,C65893,0 256422 FS Control Sent: Ctrl=65893, Param=0 AP_ALT_VAR_DEC 256422 [Buttons] 47=CP(+G,2)G,1,C1016,0 256422 .... Condition (+G,2) = FALSE 256500 Button changed: bRef=0, Joy=0 (G), Btn=1, Released 266719 Button changed: bRef=0, Joy=0 (G), Btn=0, Pressed 266719 [Buttons] 48=PG,0,C65892,0 266719 FS Control Sent: Ctrl=65892, Param=0 AP_ALT_VAR_INC 266719 [Buttons] 49=CP(+G,2)G,0,C1017,0 266719 .... Condition (+G,2) = FALSE 266797 Button changed: bRef=0, Joy=0 (G), Btn=0, Released 267297 Button changed: bRef=0, Joy=0 (G), Btn=0, Pressed 267297 [Buttons] 48=PG,0,C65892,0 267297 FS Control Sent: Ctrl=65892, Param=0 AP_ALT_VAR_INC 267297 [Buttons] 49=CP(+G,2)G,0,C1017,0 267297 .... Condition (+G,2) = FALSE 267375 Button changed: bRef=0, Joy=0 (G), Btn=0, Released 268328 Button changed: bRef=0, Joy=0 (G), Btn=1, Pressed 268328 [Buttons] 46=PG,1,C65893,0 268328 FS Control Sent: Ctrl=65893, Param=0 AP_ALT_VAR_DEC 268328 [Buttons] 47=CP(+G,2)G,1,C1016,0 268328 .... Condition (+G,2) = FALSE 268406 Button changed: bRef=0, Joy=0 (G), Btn=1, Released 268703 Button changed: bRef=0, Joy=0 (G), Btn=1, Pressed 268703 [Buttons] 46=PG,1,C65893,0 268703 FS Control Sent: Ctrl=65893, Param=0 AP_ALT_VAR_DEC 268703 [Buttons] 47=CP(+G,2)G,1,C1016,0 268703 .... Condition (+G,2) = FALSE 268781 Button changed: bRef=0, Joy=0 (G), Btn=1, Released 269688 Button changed: bRef=0, Joy=0 (G), Btn=0, Pressed 269688 [Buttons] 48=PG,0,C65892,0 269688 FS Control Sent: Ctrl=65892, Param=0 AP_ALT_VAR_INC 269688 [Buttons] 49=CP(+G,2)G,0,C1017,0 269688 .... Condition (+G,2) = TRUE 269688 FSUIPC Control Action: Ctrl=1017, Param=0 269766 Button changed: bRef=0, Joy=0 (G), Btn=0, Released 270141 Button changed: bRef=0, Joy=0 (G), Btn=0, Pressed 270141 [Buttons] 48=PG,0,C65892,0 270141 FS Control Sent: Ctrl=65892, Param=0 AP_ALT_VAR_INC 270141 [Buttons] 49=CP(+G,2)G,0,C1017,0 270141 .... Condition (+G,2) = TRUE 270141 FSUIPC Control Action: Ctrl=1017, Param=0 270219 Button changed: bRef=0, Joy=0 (G), Btn=0, Released 271016 Button changed: bRef=0, Joy=0 (G), Btn=1, Pressed 271016 [Buttons] 46=PG,1,C65893,0 271016 FS Control Sent: Ctrl=65893, Param=0 AP_ALT_VAR_DEC 271016 [Buttons] 47=CP(+G,2)G,1,C1016,0 271016 .... Condition (+G,2) = TRUE 271016 FSUIPC Control Action: Ctrl=1016, Param=0

System information: MSFS 2020 NXi G1000 aircraft I'm trying to setup control over using the autopilot altitude selection. I'm using the following simulator commands, 2 of which are provided via FSUIPC7: AP ALT VAR DEC AP ALT VAR DEC FAST AP ALT VAR INC AP ALT VAR INC FAST I using a dial encoder that has a push button function. I would like to set the DEC/INC commands on a regular twist of the dial and the DEC FAST/INC FAST as a compound command when I press the push button and turn the dial. I HAVE been successful configuring this type of setup using the HEADING/VOR1/VOR2 commands (DEC/INC on a regular twist of the dial and DEC FAST/INC FAST when the button is pressed in). HOWEVER, when I try to setup the AP ALT, I get a response of whatever is set to the regular twist of the dial, even when the button is pressed down. For example, if I program DEC/INC on the regular dial and the FAST functions on the press and turn of the dial, I only see a response of DEC/INC in the sim. If I program DEC FAST/INC FAST on the regular turn of the and the regular DEC/INC on the press and turn, I only see a response of DEC FAST/INC FAST in the sim. YET, if I program four key presses or buttons with these four methods, I get the proper response. If I program two rotary encoders with these four responses, I get the proper response. I only see the issue when I use a compound programming of these 4 actions. As mentioned above, I am familiar with programming compound actions and can successfully get this to work with the heading and VOR events. Any insight/information/thoughts about how I might could get this to work with the AP ALT events? Thanks!

John, Thanks for the information. I was able to get it working when using just one accelerator key.

Hello, I'm trying to configure FSUIPC7 to send a control to MSFS using the "Key Presses" under the "Assignments" tab. I can properly setup the key press to control assignment in FSUIPC7. However, what I've discovered is that when I run MSFS the following happens: 1. If my key assignment is a single, regular key (such as 'a', 'b', 'c', etc), then the assignment works properly in MSFS. 2. If my key assignment involves an accelerator key (ctrl, shift, alt or any combination of these), the key assignment does not work. 3. If FSUIPC7 has the focus, then the key assignment even with the accelerator keys DOES work. 4. But if MSFS has the focus, then it does not pass through any of the accelerator keys. I can see this behavior in FSUIPC7's log. When FSUIPC7 has the focus, then it properly picks up any accelerator keys in combination with the regular key (e.g. ctrl + shift + a). It displays the keydown/keyup for each of these keys, detects the key combination and sends the appropriate control to MSFS. MSFS reacts appropriately. HOWEVER, if MSFS has the focus, when I press any accelerator key, it does NOT appear in FSUIPC7's log. Only the 'a' in the sequence ctrl + shift + a gets sent to FSUIPC7 and shows in its log. Therefore FSUIPC7 does not detect the full key press sequence and so does not send the assigned control. I'm sorry if this is a known issue, but I've tried a number of searches to find previously reported issues and looked through FSUIPC7's documentation. I realize this may be an issue with MSFS and not resolvable by FSUIPC7. But my experience with MSFS support has been abysmal to put it nicely so I thought I'd ask here to see if anyone had any insight into this? Thanks.

I'm using FSUIPC 4.934 with Prepar3d 2.2.10437. I can get lua files to run (such as ipcReady.lua as well as gfdDisplay.lua). However, I can't get any of the ipc.lineDisplay or ipc.display functions to show (or open) a window within Prepar3d. Any ideas why? I can get gfdDisplay.lua to run as indicated by the display lights on my GFD modules as well as logging information to the log file, but there is no text output appearing within the Prepar3d simulator. This worked fine for me without any modification in FSX. Am I missing something? Thanks

Hello, I have a few questions about using FSUIPC and LUA: 1. What is the difference between manipulating controls using FSUIPC offsets (ipc.writeUB()) versus sending the FSX control directly (ipc.control())? Which is more efficient? 2. What is more optimized, assigning FSX controls to buttons through the FSUIPC interface or setting controls via FSUIPC offsets (ipc.writeUB()) from lua scripts or sending FSX controls directly from lua scripts (ipc.control()). I've been doing quite a bit of programming using LUA and have discovered there are multiple different ways to interact with FSX. I'm just trying to determine what ways are better, simpler, more optimized, etc. Thanks for any input or insight into the inner workings of FSUIPC.