John Dowson

@DakotaPilot and @aua668 there is definitely something strange going on with the run programs command with arguments. I will look into this and get back to you. However, this may take a while - I'll post back here when I find out anything useful. John

The code still exists. If you set that ini parameter to a control/event number, when FSUIPC sees that control it will automatically change to use the FSUIPC steering tiller control instead, As Pete says, its pretty much redundant these days. John

No problem. Just remember that by default, all general sections are loaded. Then, if there is a profile, buttons and key sections are loaded and replace/augmented the general sections (i.e. general section assignments apply unless changed in the profile). Axes and calibration sections work differently - if there is an axes profile section, the general section is dropped and the profile axes section is loaded and used exclusively, and the same with the calibration sections. If no profile axes (or calibration) section is present, then the default/general section will be used. Just FYI. John

Yes

This is a bit old now (sorry!), but did you mange to do this? You can use the Mixture Lean control (or Mixturen Lean for the engine specific versions) for cut-off, and Mixture Rich (or Mixturen Rich) for idle.

I'm sorry but I can't really support C#. If using C# and the WAPID.dll you should try with Paul Henty's dll for .NET (if not using already) which is also compatible with the WAPID - see Paul may also be able to help with FSUIPC access via C# if you post in his sub-forum: https://forum.simflight.com/forum/167-fsuipc-client-dll-for-net/ John

Ok. Thanks for the update.

Hmm/ Sounds a bit strange... Especially as the command works when you run it in a command window, which would suggest that the program is picking up the correct path. I think it may depend on which shell is being used to run/interpret the command. Did you try both with double quotes around the program location and the argument separately? And also around the whole command line command? And even if the command line argument is incorrect, doesn't the program start anyway and give some sort of error that the file can't be found? Or is the program closing and returning error code 267?

Ah, sorry - missed that! Then you should do as the manual suggests, quotes around the program start path and quotes around the parameter. You have no quotes, e.g. If that doesn't work, you can try quotes around the whole line, but try that, as documented, first...

But you have no parameters - at least not in what you posted, Quotes are only needed if the path contains spaces or if command line parameters are needed, as specified in the Advanced User manual, although it never does any harm to include them anyway. As (I presume) you replaced your actual name with the string NAME, we can't tell what the actual path is, but if it has spaces, it needs to be in quotes. As a test, you can also try running your run command from a terminal window, to see if it actually works outside of FSUIPC.

Does in work with GFDevFSX.exe? See https://www.avsim.com/forums/topic/578617-ms-2020-and-goflight/page/4/ Are you using FSUIPC7, and if so is the device recognised (i.e. is it a HID joystick type device)? Maybe worth looking/asking on the GoFlight forums.

Glad its all now working. Hope the GUIDs don't change again! You should be ok if the joystick IDs change, as you are now using JoyLetters. Ok. This makes me thing it was a driver/registry issue. Hopefully you should be ok now... Regards, John

Ok. But now everything is detected ok: This is good! Now you just need to change the [JoyNames] section in your FSUIPC5.ini. Change it to this (with P3S/FSUIPC not running): Then try starting P3D/FSUIPC, and hopefully things should be ok..... John

Are you connecting your devices to usb3 or usb2 ports? If using usb3, maybe try switching to usb2 ports instead...

There is no current beta for FSUIPC7 - that post is over a year old! For all FSUIPC products and related software, please use www.fsuipc.com. If click-to-download doesn't work, right-click and select 'Sava as...'.

Are those files from after you changed the ids or before? After I presume.... Can you again do the following: - unplug your devices - backup your registry - run the .reg file again - remove the drivers for your X55 using the windows device manager - reboot Once done, don't connect your devices, but go into regedit and search for any entries with a vendor id of 0738 and a product id of 2215 or A215. Do you see anything? If so, try removing those. You really want to remove all traces of these devices so that they are detected as new devices. Once those entries have been removed, reboot again and give the registry a last check. Then connect you devices, start P3D/FSUIPC, load an aircraft, shut down, and then show me those 3 files again.

Sorry, I'm probably posting too many messages and confusing you... If you have done anything yet, first try this: - unplug your devices - backup your registry - run the .reg file again - remove the drivers for your X55 using the windows device manager - reboot - connect your devices. Let windows install the default drivers - start P3D/FSUIPC, load an aircraft, then shut down - show me your 3 files, the .ini, .log and .JoyScan.csv files If you still don't get the devices recognised as individual devices after doing this, then you can try manually setting/changing the joystick using a program called JoyIds. See John

Maybe also try removing the installed drivers for the X55 after you have removed the registry entries (and before you plug in your controllers), and let windows re-install them again when you re-connect. I would do this before manually removing anything else with the same vendor and product ids.

I suspect that there may be other registry entires that need removing.... You could try running the.reg file again with devices unplugged (again, backup first), then reboot. Start regedit, backup again, and then search for 0738 (the VendorID for the X55). All entries you encounter that look related to your devices (i.e. if they also have a Product ID of 2215 or A215) should be removed. Then reboot again, connect you devices, start P3D/FSUIPC and see what is recognised. Show me you .log, .ini and .joyscan.csv files after doing this. Maybe show me your current JoyScan.csv file first before doing this though....

I don't understand why the registry cleaning seemed to do nothing this time. And I don't understand why it is again getting two GUIDs for your stick but none for your throttle. Could you show me your FSUIPC5.JoyScan.csv file please.

I don't know why it has done this again....are you unplugging your devices? Try cleaning the registry again. Once done, and you have ran P3D/FSUIPC once to update your ini, close P3D and then change this line in your FSUIPC5.ini: AutoAssignLetters=No to AutoAssignLetters=Yes And the run P3D/FSUIPC again. Close down P3D/FSUIPC and show me your updated FSUIPC5.ini and FSUIPC5.log files (the devices may need switching after doing this). I don't know why it has done this again. Are you sure you don't have the saitek/logitech drivers installed, or are running any saitek control software?

Sure. No, you can leave it running - it shouldn't take up too many resources. However, if you don't want to use it, you can also opt to not install it during the installation process. If you occasionally want to use it with FSUIPC7, you can just move it out of your Community folder (i.e. move it up one folder level) before you start MSFS, and when you want to use it just move it back, again before you start MSFS.

Because when you installed FSUIPC7 you selected the option to auto-start with MSFS. When this is selected, it creates or updates the MSFS EXE.xml file so that MSFS auto-starts FSUIPC7 at the appropriate time. If you don't want this to happen., re-install FSUIPC7 and deselect the auto-start component. After doing this, if you want to still have the ability to start FSUIPC7 with MSFS from the desktop MSFS link that is created, you can edit the MSFS.bat file, located in your FSUIPC7 installation folder, and located the following lines (although your path to the FSUIPC7.exe may be different): Then remove the two double colons which comment out the timeout and start lines, thus: If you do this, you can then use the MSFS desktop link to start MSFS and FSUIPC7, or the standard MSFS desktop link or start menu option to start MSFS without FSUIPC7. John

Yes - or you can remove them using the assignments UI panel, if they are single assignments to buttons.

Please see the README.txt file provided in the downloaded zip file. You need to uninstall and re-install your VC++ redistributables.