John Dowson

No, thats fine. Bit lets stick to one FSUIPC version - if you are testing with FSUIPC7, stick with that and please show me your FSUIPC7 files. not your FSUIPC6 ones. You can always zip the, before attaching... Please do not keep switching between P3F/FSUIPC6 and MSFS/FSUIPC7. Choose one and lets stick to that one please... Please show me an FSUIPC6.JoyScan.csv file and I can prepare a script to clean your registry. John

Please double-check your settings in FSUIPC's AutoSave/GPSOut panel. If you think FSUIPC is not respecting your settings,(which I doubt very much!), then please activate logging for autosave activity by adding the following to the [General] section of your FSUIPC4.ini file: Debug=Please LogExtras=x4 Then show me your FSUIPC4.ini and FSUIPC4.log files, John

What version of the FBW A320 are you using - stable or dev? According to the MF preset list, the following presets should be available: stable: A320_Neo_FCU_ALT_PULL, A320_Neo_FCU_ALT_PUSH dev: A32NX.FCU_ALT_PULL, A32NX.FCU_ALT_PUSH Alternatively, you can use hvars in the stable version and the FBW custom events in the dev version. What does this mean? What instruction? What have you tried? Neither do I! What is it? Please see the MF HubHop site (https://hubhop.mobiflight.com/presets/) for a list of available presets for the FBW A320.

There are no engine 1,2,3,4 assignments and never have been. I am not sure what such assignments would even do....The throttle axis is always assigned to the throttle controls to control the engine power/rpm.. There are two distinct controls lists for axes assignments - one which goes directly to FSUIPC calibration (available when checking Send direct to FSUIPC Calibration), and the other containing the remaining FS axis controls and lua and macro entries (available when selecting Send to FS as normal axis.

Sorry, bur what do you mean? All presets in an events.txt file in the correct location (the FSUIPC7 installation folder) will be loaded and available after checking the Select for Preset checkbox. If you replace/install the file when FSUIPC7 is running, you will need to restart it. Any issues, please let me know what presets are defined in the events.txt file that are not available and I will take a look. But if the preset is defined in the correct format, I really cannot see how it cannot be available for assignment, so please double-check that the preset is in the file and that the file is in the correct location. John

Offset 0x341E was disabled in an early version of FSUIPC7 as requesting the simvar HYDRAULIC SWITCH was giving errors when being requested as indexed (1-4). I have re-enabled this and tested and it now seems to be working, so please try the attached version. John FSUIPC7.exe

Please give a relevant title to your support requests, not just your user name, as this can attract other users who may be able to help. I have updated the title for you. I am sorry but I do not understand your problem. You can assign any lever to individual or multiple throttles. It is up to you how you want to assign your different levers. You can assign one axis to control multiple engines, or use individual axis for each throttle, it is up to you. What do you want to assign, and why is this not possible? This doesn't make any sense to me. Do you mean using one axis to control (throttle on) engines 1 and 2? This doesn't make sense either. You can assign an axis to throttle on engines 1 & 2, or assign them on individual axes. Can you please clarify what your issue is please. John

This is usually caused by the device going to sleep. Check your USB hub device properties and make sure that the allow to sleep option is disabled. This refers to duplicate registry entries for your devices, probably caused by you unplugging and reconnecting - you shouldn't do this. They are only warnings, but to remove these you would need to clean your registry. You should change this entry, from No to Yes, in the [JoyNames] section of your FSUIPC6.ini file: this will prevent issues if your joystick ids change. Also, you are using version 6.1.6, which us quite old. Please update to 6.2.0 which is the latest and only supported version. John

It looks like FSX crashes in the API.DLL are due to a recent windows update - please see and on avsim: https://www.avsim.com/forums/topic/635654-fsx-apidll-crash-no-fixes-in-other-threads/ I have also just asked the OP of these threads for a reference to the confirmation of this issue. Hopefully this will be fixed in another windows update. John

Do you have a reference/link for this confirmation? Thanks, John

Not sure what this means, but I have send you a trial license. John

Didn't you already try the trial license back in June 2022? Why do you want to try a trial license again?

But why do you think this? If you are clicking a button in the VC, what has this got to do with FSUIPC? The command will be sent by the VC, not FSUIPC - FSUIPC will receive this, for logging purposes, but it does not send the command. It only sends commands from hardware buttons/axes that you have assigned. If FSUIPC isn't seeing the command, then it is not being sent to the FS. ok. You too - cheers, John

License sent via PM. It is an FSUIPC7 license that you would need. WideFS7 is an additional utility that is ran on client PCs (i.e. not the PC running the simulator) to allow FSUIPC client applications to be ran on a separate PC to the simulator. Note that the SimConnect SDK function that FSUIPC7 uses to save a flight is still documented as " The current status of this function is NO ERROR, NO RESPONSE.", which is Asobo's way of saying that this function is still nor working 100%. However, many people are using this without issues, but problems have been reported in certain things not being restored correctly or not working after loading a saved flight in some aircraft - mainly complex add-ons. So best to try this first with the aircraft that you fly if only considering for this function. John

Only one hat switch is recognised in the axis assignment tab - the hat switch that has button numbers 32-39. The other 2 hat switches must be assigned in the button assignment tab. Check in the button assignment tab to see which button numbers your hat switches use, and find the one that uses button numbers in the 32-39 range. Then go to the axis assignment tab and move that hat switch. What axes letter do you see? If it is not P, then click Ignore Axis and try again. If the hat-switch is using buttons 32-39, it will be recognised in the axes assignment tab. John

Why define these twice? As the preset/calc.code is the same, you should just define once and use for both versions of the aircraft. This is how it currently works - I will correct this at some point, when I get time... First, check that you are using the latest (and only supported) version of FSUIPC7, which is 7.3.21. If not, please update and try again. Of it is still not working, it will be due to one of 3 things: 1. The lvars are not updateable. To check this, use the Add-ins->WASM->Set Lvar menu oprion to manually set the lvar values, and see if the aileron/rudder position changes when you do this. 2. The calculator code/assignment is not correct. To check this, activate logging for Axes Controls, and WAPI -> Debug logging. Open the logging console (Log -> Open console) and move your assigned axis, and see if you can see the correct preset/calculator code being sent. 3. The code is not being applied by the WASM. To check this, activate debug level logging in the WASM and see what calculator code is logged in the WASM log file. Any issues, you can post/attach your log files and ini file here and I can take a look. John

Ok, sorry - of course a hat assignment to Pan View must be done in the axis assignment tab, as Pan View is an axis event. But my questions still stand: You do a rescan by pressing the Rescan button in the axis assignment dialog box, then you press/move your hat switch to see the assignment... When you assign to Pan View on one hat-switch button, it may not be registered on the other hat switch buttons until you confirm the assignment, i.e. click the Ok button. Have you tried just assigning and then using the hat switch? Otherwise, as I said, please explain your issue, and also attach your FSUIPC ini file so that I can see your assignments. At the moment, I do not know what version of FSUIPC you are using or even the FS that you are using... John

What do you mean by this? There is no "re-scan" in button assignments, and pressing a joystick button will just register that button ready for assignment, and show any current assignments on that button. Can you please explain more clearly what your issue is?

I don't understand why these would interfere with each other. Each is sending controls/events to the FS, which would then act on these requests updating the sim data, and then this data should be reflected back in FSUIPC. If you set logging for Events and open the FSUIPC7 logging console window, you should see the events sent both from the PFC and RSG APs. Maybe try this and see what is logged. You can try this, but I am not sure if this will help, as this only changes what is sent when you activate the AP buttons on the PFC device - just not using them should suffice... To do this, You would have to add an empty macro for each of the AP buttons (or a macro that does nothing) to the PFC.mcro file. However, better to try and understand why they are interfering first. John

First, you are using an old and unsupported version of FSUIPC7, v7.3..15. The latest and only supported version is 7.3.21 - please update. But your Sting S4 is currently assigned to your C172 profile. In this profile, you have multiple throttle and mixture assignments:: This is always a bad idea as the assignments can interfere causing the axis to jump. You also have dual mixture assignments in the Kodiak and Antonov AN-2 profiles. I see no such problem in your Piper Arrow profile, so I am surprised that you get this issue in that aircraft... One of your [LvarOffsets.KODIAK] entries is also invalid as it contains no size/type specifier: You should also consider using sub-strings for your aircraft profile names, e.g. change to Once you have corrected this, please try again. Any issues, please re-attach your FSUIPC7.ini and also your FSUIPC7.log file,.

Please also see

They are separate files. Please consult the documentation for such questions (Advanced User manual, in WASM section). The events.txt file contains the MobiFlight presets. You can add presets there but they will be removed the next time you install/update FSUIPC7 as this file will get overwritten/re-installed. This is why the myevents.txt file is also needed, for user-specific presets, and why I said to add this to the myevents.txt file, and not the evemts.txt file. Please follow my instructions, as well as consulting the provided documentation. I am not going to repeat everything in the documentation when answering support requests... This doesn't make sense. How can this be available before you check Select for Preset - you should only see standard FS controls/events before this is checked and no presets, and one you check Select for Preset why are you clicking OK? Add the preset definition to the myevents.txt file as I said (and remove it from your ecents.txt file). Then start MSFS and FSUIPC7. Load your aircraft and open the axis assignment panel. Move the axis control you want to assign, If the axis is already assigned, click the Clear button. Then check Select for Preset (top-tight) and also Send to FS as normal axis. Then click the checkbox next to the first assignment drop-down on the left hand side, click the drop-down menu and you should see a list of presets (the drop-down may take a second or two to load so be patient). Then select your preset from the the drop-down, and then click Ok. When assigning presets to an axis, you must always also check Send to FS as normal axis. I will make this clearer or maybe mandatory...

You do this by manually editing/adding the compound conditions to the assignments in your FSUIPC7.ini file. Please see the section COMPOUND BUTTON CONDITIONS on page 21 of the Advanced User guide. Also see the example I gave/referenced for GA aircraft in my previous post. John

First, you don't assign these buttons, but you use them for adding compound button assignments to the inc/dec buttons: 20 alt 19 vs 18 hdg 17 crs 16 ias I have shown how to do this for the standard (GA aircraft) in this post: I suggest that you first read that and install the provide Rotaties.lua script to allow fast/slow button programming in the rotaries (and trim). For use with the Fenix A320, you would need to assign the in/dec buttons to the appropriate MF preset. So, for example, for the heading you would probably need to assign to the presets: FNX320_FCU_HEADING_KNOB_INC FNX320_FCU_HEADING_KNOB_DEC and then add a compound button expression so the assignment is only triggered when button 18 (HDG) is set. You can also find appropriate presets for Alt, VS. IAS (Speed), I am not sure what you would assign to the CRS position, or if this is needed. There are no "fast" versions of these presets, but you can overload the assignments so that 4 or 5 of the standard controls are sent on each fast (virtual) button presses. For the remaining buttons, you need to decide what AP function these should map to in the Fenix A320, and then select the appropriate control or preset. See the MF HubHob site for available presets for the Fenix: https://hubhop.mobiflight.com/presets/. I don't have the Fenix. John

Ok - as the lvar value range is -100 -+100, and your axis has the standard axis range of -16384 - +16384, then the preset would be: DA62 Aileron#@ 163.84 / (>L:INPUT_AILERON) i.e. divide the axis value by 163.84 to get a range between -100 - +100. You can also use a similar preset for the rudder: DA62 Rudder#@ 163.84 / (>L:INPUT_RUDDER_S) John