John Dowson

What do you mean by 'it doesn't save'? You have to add some assignments to a profile otherwise there is nothing to save. John

Hi Annick, once you unzip the FSUIPC5.zip file you will get the 'Install FSUIPC5151.exe' (+ an install document), which is the latest (released) version. Run the installer and that will copy the dll to the correct folder, as well as installing the documents and updating the dll.xml (so that FSUIPC is started with P3D). Cheers, John

I see you are also assigning in P3D as well as in FSUIPC. It is advised to disable controllers in P3D when assigning in FSUIPC, especially if you do your axis assignment in FSUIPC as P3D has a habit of automatically re-assigning if controllers are not disabled. John.

Hi, you need to look into using 'profiles'. Take a look at the section 'User profiles for all control settings' on p18 of the User Guide in your 'Modules/Documents' folder. For your use case, you can just override the button assignment with a profile specific one for the jet in question. Cheers, John

Hi Annick, your browser is probably caching the original link/download - try clearing your cache and downloading again. Cheers, John P.D. Its 'www.schiratti.com/dowson.html' not 'www.schiratti.com/dawson.html'!

Hi Annick, sorry about that - I accidentally uploaded the dll only to the link pointed to by the SimMarket / Schiratti site. This has now been corrected - please try again. Regards, John

The thread you posted advises you to "...Remove any throttle axis calibration in FSUIPC...", so why do you want to calibrate?

Hi Alvaro, FSUIPC4 is the version you use with FSX. For P3Dv4, you need FSUIPC5 which requires a separate license, available from SimMarket. All FSUIPC products can be downloaded from here. Regards, John

Hi Dane, copying across your old files should be fine (presuming you installed FSUIPC first), with some caveats. However, if FSUIPC is not recognising your devices, we need to see the files (log, ini and joyscan.csv) from your current installation, the one with the issue, not your old system. Cheers, John

Hi again Peter, I just tried again with adding 'SendKeyPresses=Yes' option to the WideClient.ini '[User]' section and this does work, sending key presses from the WideClient pc to the sim pc when WideClient has the input focus. KeySend is used in WideClient, but for receiving KeySends from the sim PC and directing these as key strokes to other programs on the WideClient pc. Regards, John

Hi Max, from what you say, it certainly sounds like you have faulty hardware or a faulty connection. You also say: By 'cursor' do you mean 'lever'? Still, I suspect that your hardware is faulty. FSUIPC receives the axis values from Windows, so I'm afraid if Windows is not seeing that lever, then there's nothing that can be done in FSUIPC to resolve this problem. FSUIPC will only recognise the first axis movement/value it receives. Having two axis values for one lever movement sounds very suspicious - either a hardware problem or a driver issue would be the culprit. Btw, have you installed any Saitek driver software? If so, please remove this and re-test. If not, I think you have a hardware (or Windows) problem. Cheers, John P.S. Don't forget to try without LINDA, and also please post your ini file.

Hi Max, the third lever should be the U axis, and the axis is given in the details for that device. As I said, I think you have a hardware or connection problem if the axis can't be seen. Anything device/axis thats seen by windows should be available in FSUIPC. Maybe try temporarily enabling controls in your sim to see if the sim can see it (but I doubt it!). I also see you are using LINDA - try without this to see if that makes a difference (e.g. rename your ipcReady.lua to ipcReady.disabled), but again I doubt this will do anything either but quick and worth a try. Is this a new device? Have you ever been able to use/assign to this axis? Are you also using a VRInsight device? This error indicates that its either not connected or on the wrong com port: VRI port 1 "com0" failed to open Maybe you could also post your joyscan.csv file, also located in the Modules folder. Cheers, John

Hi Peter, I think you are misunderstanding the KeySend functionality. This is for transmitting key presses/releases from your primary sim pc to the client/WideClient PC. For transmitting keystrokes from WideClient to FSUIPC, You should really be looking at using the virtual button facilities (see 'ButtonKeys: making use of FSUIPC’s virtual buttons facilities' section in the WideFS Technical guide). The 'SendKeyPresses' option has limited capabilities to do this (again see Technical Guide) but is limited to certain systems - its not working for me on Windows 7/10 for example (I'll check with Pete but looks like its limited to Windows 98/ME/2000/XP). Regards, John

Usually you would send the brakes direct to FSUIPC for calibration and reverse them. You shouldn't need a center zone, as the axis goes from -16383 (off) to +16384 (full on).

Its in the Modules folder - if you go to the FSUIPC 'Logging' tab there's an 'Open Folder' button which will take you there. You may have to configure explorer to see system files/known extensions.

Hi Max, if you can't see it as an axis, but you can see the other two levers, then I suspect its either faulty or you have a dodgy connection somewhere. Can you see all 3 rocker switch buttons (6 buttons)? Can you check what axis the device is reported as having in your fsuipc log file, you should find something like this: 16813 Product= Saitek Pro Flight Yoke 16813 Manufacturer= Saitek 16813 Vendor=06A3, Product=0BAC (Version 3.4) 16813 GUIDs returned for product: VID_06A3&PID_0BAC: 16813 GUID= {327F7D90-F534-11E7-8005-444553540000} 16813 Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X1023,Y1023,Z255 Cheers, John

Yes, the SDK is available from here: You could also try Paul Henty's FSUIPC Client DLL for .NET: https://forum.simflight.com/forum/167-fsuipc-client-dll-for-net/

This is a problem which only exists since Windows 10, and only when you let P3D install in Windows\Program Files. That folder is protected unless you run "as administrator". Now, for most installations, this isn't a problem because provided you run the Installer "as administrator" it is able to change the permissions (just on the Modules folder) automatically. But on just a few systems it is prevented and gets that Error 1332. Sometimes this can cause issues as it can prevent files from being installed and the log and ini files being created. However, your as your docs were installed and you have log and ini files, I wouldn't worry about this too much, but if it you want to get rid of this and If you didn't run the installer as an admin, you could try that, otherwise you can manually edit the Modules folder permissions yourself (to allow full access by right clicking on the folder properties: Security-->Add Everyone as a user name, then check 'Full Control' access below). This won't be the cause of your issue with EFB2. Best to try their support forum for this. Cheers, John

Sorry, I have no idea. Please take a look at the provided documentation and look in the FAQ / user contributions sections to get an overview of what you can do with FSUIPC.

Sorry, but I have no idea what you want to achieve or what you want to do with FSUIPC. Please check the documents folder for information on the interfaces provided.

You can retrieve your codes from your SimMarket account, where you purchased FSUIPC.

Have you tried the 'Reload all assignments' button from the 'AxisAssignment' tab', or the 'Reload all settings' from the 'Joystick Calibration' tab. I'm sure one or the other (or both) will pick up the new lua... Cheers, John P.S. Just checked - its the latter!

Good to see someone solved there own problem - and posted the solution! A message box may be appropriate, but probably a note in the user manual more so. I'll have a look and think about this. Regards, John

What sim/fsuipc version are you using? And what aircraft - is it the FSLabs A320/A321? Maybe try with a default aircraft first, as it may be a a problem specific to this add-on. Presumably your button 'down' and 'up' are actually different buttons (or button numbers). Are you assigning to button press or release? Maybe switch to the other (or try on both). Could you also please post your FSUIPC5 (or 4) ini file. Thanks, John

Glad its now working - thanks for the update. Regards, John