John Dowson

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

There have been a few other questions on Elite hardware, but from what I understand they will only work work with their own drivers. I do not supply any additional drivers for Elite devices. I will send you a trial key, but I do not know if FSYUPC will be able to see your buttons/axis. You will still need your Elite driver though, and I don't know how that works with MSFS (or any other FS!). John

To assign an axis to an lvar, you need to create a preset. First, you need to determine what the maximum and minimum values that the lvar takes, and you must also know the maximum and minimum values the axis sends. The preset, which you need to add to your myevents.txt file (create this if not present) will then take the form DA62 Aileron#@ <conversion> (>L:lvarname) where <conversion> - is the RPM code to convert the axis input value range to that expected by the lvar lvarname - is the name of the lvar that controls the aileron position You can then check the Select for Preset in the top-right of the axis assignment panel and assign your axis to the preset DA62 Aileron. To see how this works, take a look at this comment where I show how to assign an axis to an lvar for the ATR to control the condition lever: If you have difficulties with this, if you let me know your axis range and the range of values expected by the lvar as well as the lvar name, I can help you define the preset. John

Thanks for the update. John

All your settings are stored in the FSUIPC7.ini file located in your FSUIPC7 installation folder, and if using profiles-in-separate-files, then the individual profile files will be stored under a Profiles folder, also with extension .ini. Note that they may need adjusting due to a change in your devices GUIDs and/or IDs if transferred to a different PC. Files also worth backing up, if you use them, are: *.lua - lua script files *.mcro - macro files *.evt - custom event files myevents.txt - your user-defined/private presets myoffsets.txt - your user-defined/private populated offsets *.dll - drivers for certain devices loaded by FSUIPC FSUIPC7.key - your license/key file (although not needed as you can always recreate this if you know your license details)

License sent via PM. John

ok - let me know how it goes... John

If calibrating a throttle axis without reverses, you would normally do this by checking the No Reverse Zone checkbox in the top-left of the throttle calibration tab (page 3)...see the following post on setting up the throttle and reversers (in a button) for the PMDG 737: John

Can you please change the logging in your WideClient.ini under [User] to Log=KeySend and show me your files again please. Also make sure that the files are all from the same session - the last ones toy posted seem to be from different dates: WideClient.log: WideServer.log: Also, please make sure that WideClient is being ran with the same permissions as your WideClient clients - if any require being ran with admin privileges, then all must be ran with admin privileges. Better to run everything with standard privileges if possible.

First, you are trying to install version 7.2.16 which is quite old now. The latest (and only supported) version is 7.3.21. Please download the latest version and install that. Please uninstall your current version first by running this file: C:\FSUIPC7\uninstallFSUIPC7.exe This one: C:\Users\maros\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt That is the UserCfg.opt file for a steam install. Not sure why you have that in this location if you have not installed MSFS via steam... If you remove/rename that, the installer should detect your MS store version and install for that.

Licenses sent via PM. John

You are not running FSUIPC... The MSFS desktop icon is used to start MSFS, not FSUIPC. It looks like that when you installed FSUIPC7 the installer didn't detect your MS store version and so defaulted to a steam install. Could you please show me/attach your InstallFSUIPC7.log file (located in your FSUIPC7 installation folder), and let me know where your MSFS UserCfg.opt file is located. If one exists under <your user account>\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt then the installer will think you have an MSFS steam installation. If this is the case, remove or rename that file, manually run the FSUIPC7 uninstaller uninstallFSUIPC7.exe (in your FSUIPC7 installation folder) to remove FSUIPC7 from your system and then try to install again. After installation, check your installation log file to check that the MS store version of MSFS was detected. You can also try manually starting FSUIPC7, either before or after starting MSFS, by double-clicking the FSUIPC7.exe in windows explorer.

I don't have the 738/739, bur check the SDK for custom controls to control the fuel cut-off levers. For the 737, you would use the following: See the following FAQ entry on how to use custom controls with PMDG aircraft: Alternatively, you could try the following PMDG presets - these are for the 737 but may also work with the 738/9: PMDG_B737-7_FUEL_CUT_OFF_LEVER1_DN PMDG_B737-7_FUEL_CUT_OFF_LEVER1_UP PMDG_B737-7_FUEL_CUT_OFF_LEVER2_UP PMDG_B737-7_FUEL_CUT_OFF_LEVER2_DN Not sure why you would want to bind these controls to axes as they are standard events fir buttons/switches, not axes controls. However, you can assign them to an axis if you wish. You would normally do this using the right-hand side of the axis assignment panel, to send the desired control when entering or leaving an axis range. Yes. You need to create an FSUIPC profile for the v738/739 and make the assignment profile-specific. Please see the provided documentation on using profiles. John

From the websocket server online help (http://fsuipcwebsockets.paulhenty.com/😞 So it can be used, it is just not included or integrated into FSUIPC6 as it is with FSUIPC7. Those are questions for @Paul Henty... John

The standard controls do not work for the G1000 - you need to use Presets. The presets for the G1000 start with AS1000, so for the MFD zoom try AS1000 MFD Range Inc/Dec and the softkeys are AS1000 MFD SoftKeys x (where x is the number)

What aircraft are you using? So your encoders are button-based? This shouldn't be a problem, but the assignments can depends on the aircraft that you are using - please specify.

License sent via PM. John