All Activity

Here we are. For this test I used the same FSUIPC installation as I use for MSFS 2020, Karl FSUIPC751.zip

I have checked this here now and it looks like in both cases (i.e. when using FS Controls and when using presets) what is happening is that both controls are being sent, but the FS is only responding to the first control. I am not sure why this is happening, but really you shouldn't be sending the slow/small inc/.dec control when sending the fast one. To prevent this, add another preset condition in the slow control to be only sent when the trigger button is off, i.e. change: to John

Cam you please attach your FSUIPC7.ini and FSUIPC7.log file, the latter with logging for Events and Buttons & Keys activated and showing your issue, i.e. load an aircraft, activate the flaps Increment and then exit. Also check that the button is not assigned in MSFS2024..

I use the binding in the screenshot. This works in 2020, but in 2024 it extends and retracts the flaps completely. Anyone also sees this? Tested with empty Community folder and with 2024-native aircraft as well as with 3rd party aircraft. Not sure what I'm doing wrong here. Karl

Thank you very much,i will try . Merry Christams and happy New Year

Better to disable controllers in P3D completely, otherwise it has a habit of silently re-assigning them. So please first try with controllers disabled. If you still get the same issue, please activate logging for Axes Controls and show me / attach both your FSUIPC6.ini and FSUIPC6.log files and I will take a look. Note that I have now finished for the holiday season, but I will take a look at your files over the weekend when I find some spare time. Regards, John

I have finished now for the day (and year really!), but will take a look over the weekend when I have some spare time...

Hello I have installed fsuipc 6.2.1 on P3D v4.5 and Fslabs A319/320/321 i have deleted all axis from p3d and all is set up through fsuipc,the problem is that i have some random axis and throtle problem ,some times all is working fine but some times i have the problem when using throtle aileron axis is moving to the left too all unstable. i use the same setting for all 3 airplanes Any idea Thank you

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

Please attach files rather than posting extracts... It is strange that I cannot see a button 2 press event logged, but the condition does change from false to true, and the control is being activated. The fast controls use offset 0x07D4 and set the AUTOPILOT ALTITUDE LOCK VAR simvar. If this is not working, then the aircraft doesn't use that simvar (or uses it in conjunction with something else) . Try assigning to the AS1000 presets instead, i.e. AS1000_AP_ALT_INC_100 AS1000_AP_ALT_INC_1000 AS1000_AP_ALT_DEC_100 AS1000_AP_ALT_DEC_1000

Try/start with the User manual. I provide extensive documentation do I don't have to answer such questions, and there are many on-line resources. And please don't hijack unrelated topics for your question - if there is no appropriate topic, pleas start a new one. John

Hello John, As I could not find a previous version of fsuipc older then 7.4.16 I have no means to test fsuipc 7.4.18 regarding this issue. I will however add AIAboveGroundLimit=100 to fsuipc.ini to see if that resolves the issue in fsuipc 7.50 Thanks for your reply, I'll keep you informed, Regards, Marinus Bergsma.

Hello, I am very sorry to ask that trivial question but I am completely new to this. I run msfs 2024 and I have FSUIPC7 installed, latest version. I know it is running every time I run msfs 2024. My question is, where I can find some very simple explanation on how it works, why is it needed etc. I do not need a deep knowledge , just basics. Thank you very much! Andrzej

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

The standard way to have both slow and fast inc/dec on a rotary is to use fast/slow buttons in each direction. Some rotaries do have two buttons in each direction for this, one for a fast turn and one for a slow turn. For rotaries that only have one button in each direction, you can use a lua script that can turn this one button into two virtual buttons, one for the fast action and one for the slow action. Such a lua script is included in the lua examples zip file (in your FSUIPC Documents folder) called Rotaries.lua. But you should also be able to do this using a button. If this isn't working, try using logging to work out what is happening - activate logging for Buttons & Switches and see what is logged (use Log -> Open Console to see the log in real-time). If you want further help with this, show me / attach your FSUIPC7.ini file, and an FSUIPC7.log file generated with logging for Buttons & Switches activated and showing both the slow and fast assignments. Well, you will still get the regular assignments unless you add another compound condition to these to only send when the activation button is not pressed. But what is probably happening is that you are using a momentary button and not a switch, so when you press it it is instantaneous, so when the rotary assignment is triggered it doesn't recognise the activation button as being pressed. If this is the case, then you should switch to using the button flag instead. See the section on using button flags in compound conditions in the Advanced User guide - here is an extract: John

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!

What about in 7.4.18, the previous version to 7.5.0? There was a change introduced in 7.4.18 that could cause this: So, if using a 3rd party traffic injector, you need to set that ini parameter. This is the documentation for this parameter (from the Advanced User guide: John

Hello, I recently upgraded to fsuipc 7.50 because of msfs2024. However using Prosim B738( Homecockpit software ) flying in msfs2024 is not possible. Ever since the upgrade to fsuipc 7.50 when flying on Vatsim in msfs2020 I don't get any traffic ( TCAS ) to show on my ND several other pilots using Prosim B738/A320 experienced similar behaviour. Downgrading to fsuipc 7.4.16 resolves this issue. Are there known problems with fsuipc7.50 regarding this issue ? Thanks in advance for any reply, Marinus Bergsma.

Yes, very strange... I will be releasing 7.5.1 later today, and I am going to switch to using version numbers on the downloadable file which should help with this cache issue. Cheers, John

Ok, sorry I cant be of more help. And a Merry Christmas and Happy New Year to you! Regards, John

Okay John, I want to see what can be done. I have already consulted Prosim, but they are still considering it. I will use FSUIPC 6.2.1. First of all, thank you very much. I wish you a merry Christmas and a happy new year. Best wishes Peter

Well, I downloaded it again with a different browser that I've never used, in incognito mode as well just to be certain, and I still got the same file hash and the same -15. So I dunno, maybe there's some CDN regional caching going on for my location? Doesn't really matter, mostly just curiosity at this point. ;-)

I analyzed the Install_FSUIPC7.zip file I downloaded about 40 minutes ago. The date/time on it says today at 1:20PM when I downloaded it. The SHA1 hash for it is EBAA0FAF4DB41A7E0EA25C2B9A453C647F8A6942. I suspect it's a browser cache of an older file though, because when I poke around a bit in it with 7-zip and I go to the Install_FSUIPC7.zip\Install_FSUIPC7\Install_FSUIPC7.exe\29.zip\fsuipc-lvar-module.zip\fsuipc-lvar-module\ folder and look at FSUIPC_WASM.ini it still says -15. But the LogLevel=Debug didn't change back to =Info either, nor did the date/time of my file change when uninstalling and reinstalling FSUIPC7 either. For what any of that is worth...

...and I will be releasing 7.5.1 tomorrow (only minor updates to help users with 3rd-party software using FSUIPC that hasn't been updated for MSFS2024) so maybe try that once released.

Yes, I used the top link on the home page of fsuipc.com.