John Dowson

So you didn't have the WASM installed when you tried the presets? If not, this is why the presets didn't work. It is the WASM module that applies the preset calculator code to the aircraft. And presets will also not be loaded if the FSUIPC7 WASM module is not installed. So I am getting more confused.... And why are you installing the WASM manually? The WASM module is installed (by default) by the FSUIPC7 installer. That depends on what you want to do. The WASM menu entries are used for testing lvar/hvar/caculator code. Presets are far easier to use than lvars/hvars on there own, And (almost all) presets are aircraft specific - you need to use the presets defined for the aircraft that you are using. I suggest you try using presets again. And please familiarise yourself with the WASM section in the Advanced User guide, which will tell you how to use presets as well as lvars and hvars. If they are not working, then you are either using the wrong preset or have an issue with your assignments. I suggest that you double-check everything and try again. If it still doesn't work, activate logging for Events and WAPI->Debug and generate a short FSUIPC7.log file where you just load an aircraft and then press a button or key assigned to a preset (that isn't working) and then show me that file together with your FSUIPC7.ini file. Note also that I only supply the mechanism to implement presets, and do not control what the preset actually does. This is a community effort led by MobiFlight, and questions on specific presets should be directed to the MobiFlight discord channel. But you need to make sure that the preset mechanism is working for you first. John

If you have changed this you may need to delete some files manually. The files managed by FSUIPC will be listed under the [AutoSave] section in your FSUIPC4.ini file. You can use a free program called Everything that is very useful for finding files - available from https://www.voidtools.com/ They should be in the following folder, relative to your main Steam folder: steamapps\common\FSX\Modules John

I think you mean Mouse Look, not move. I thought this would set focus to the main FS window - it surprises me that the focus stays with a sub-window. I will check this at some point. Yes, sorry - looking further at this it seems that this restores the focus to the previous window that held the focus, after it has been moved to another window. Why don't you move it to a corner rather than the centre, i.e. use mouse.move(0, 0, 2). There should not be any switch in that position. I will do some tests on the focus movement in P3Dv5 later this week, when I have time, and will report back. John

Are you using the Advanced Mouse Controls option in P3D? So ext.focus(0) and ext.focus() do not set the focus back to the FS main window? If not, where does the focus go - does it change at all? You could also try using the key focus restore control (1125), i.e. ipc.control(1125). But you can still do/try this when controllers are enabled in P3D,,,I can't see what having controllers enabled in P3D has anything to do with this....

As I said, please tell me the name of these presets. If you open your events.txt file in an editor, do you see the presets in the file? All presets in this file will be loaded.

No, don't delete anything if you do not know what you are doing. The Missing joystick message is because you have an assignment to that letter. You need to change the letters if the GUIDs to match your assignments. If you show me your files, I can do this for you. You shouldn't disconnect and re-connect when FSUIPC is running. Moving devices to a different USB socket/hub can sometimes cause ids to change, but you should be ok with this as you are using joyletters for your assignments, not the ids. Best to show me your files for FSYUPC6 as well and I can update for you. You shouldn't need to redo your assignments.

They will be in your FSUIPC4 installation folder, which is the Modules folder under your FSX installation folder.

They are preset names, available in the assignmert drop-downs once you have checked the Select for Preset checkbox. Please see the WASM section in the Advanced User guide on how to use presets, as well as lvars and hvars. Again, please see the provided documentation. However, if you are unfamiliar with hvars (and lvars), it is easier to stick to using presets (as these can use both lvars and hvars, as well as other variable types).

Please first tun regedit and take a back-up of your registry. Then, disconnect all of your devices. Run the attached regedit script - just save it and then double-click it in windows Explorer to run it: removeDevices.reg Then reboot and re-connect your devices and try again. Any issues, please show me all 3 files - log, ini and JoyScan,csv.

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