John Dowson

Sounds like your DLL.xml file is corrupt - can you please post it and I'll take a look. It should be in C:\Users\kai-r\AppData\Roaming\Lockheed Martin\Prepar3D v4\DLL.XML. You also posted in the wrong place - I've moved your post to the support forum.

Your dll.xml looks fine. Could you post or attach your FSUIPC install log please.

The SDK is the 'Software Development Kit', which allows you to write programs (in various languages) that communicate with FSUIPC (i.e. read/write offsets). The changes did not allow you to see the throttles! They only put back your previous assignments/calibration to that device. If that worked, then you must have been able to see this before, they just weren't assigned. Well, what you have now is all your old assignments back from your old ini, or thats what I thought! Looking at your ini, it looks like you have your flaps and toe brakes calibrated: LeftBrake=-16380,16380/16 RightBrake=-16380,16380/16 FlapStarts=-16384,-13765,-9239,-6209,-2020,336,6755,10375,11868 Flaps=-16384,16380 FlapEnds=-14027,-10025,-7032,-3553,75,4292,10226,11607,13137 But no calibration for your ailerons, elevator, throttle, etc, so you will need to calibrate them (especially if you are sending to FSUIPC for calibration). Then again, if you are going to upgrade ProSim, you will probably be better off assigning and calibrating there, as Pete suggested. It is recommended to run on the flight sim pc to avoid delays caused by network latency, although it should still work running on the slave.

Your joyscan.csv file shows the device BU0836A Interface is recognised and matches you log and ini, so this must be your throttle device - please go ahead and make the suggested changes. I'm not sure if this will work though, as you cannot see the axis value change (in the axis assignment tab) when this is unassigned, which is strange. You could also try downloading the HiDScanner utility - from Run this and move the throttle to see if any axis values are changed (and post the log).

As you can see if you read this thread, we do not support XPlane / XPUIPC - that is a different product to FSUIPC and by a different author. Please use their support. John

3 weeks? You should have posted earlier!! Basically your problem is that you installed P3D in the default 'Program Files' directory, which is restricted by windows. Always better to install in a different (and unrestricted) folder/directory. Installing FSUIPC does try to set the permissions to allow this, but for some reason this sometimes fails on Windows 10 - you may find that you have an error in your install log for this. Rather than running as n admin, you can manually give permissions to 'Everyone' to the Modules folder. I will be releasing a new installer at some point this year which will allow you to choose the xml add-on install method instead and so allow installation of FSUIPC outside of the main P3D folder. John

Are you using external USB hubs, and if so the same ones the different PCs?

Hi, could you download and run the HidScanner utility, available from and post your log file when done. Also please attach your log and joyscan.csv files. It sounds like you may have an incompatible USB hub/device somewhere which can cause such issues. John

Hi Peter, ...and the log indicates that it connected when P3D started. Was this not the case? I need to see the log generated when you get the message that message that WideClient has stopped working, or when it fails to connect to P3D when you start it. The log files you have posted so far don't show any issues! Regards, John

The same folder as your log an ini files - a file called FSUIPC5.Joyscan.csv. Which PC is your throttle connected to? Both your ini and log files don't show this device connected. It looks like you do have issues with WideFS. Error 10013 indicates that there is a socket connection error, most probably caused by a firewall or antivirus software. You need either to stop the firewall/anti0virus software or configure to allow access form your client to server PCs and vica-versa. I am not familiar with ProSim. Pete should be back tomorrow and will be able to advise further with this. Do you see anything in the axis assignment tab when you move your throttle? I am slightly confused...if the BU0836A Interface card IS your throttle, but just renamed, then the update I previously posted will restore your previous assignments, i.e. change these lines T=G-Throttles << MISSING JOYSTICK >>T.GUID={048B2C90-D690-11E1-8001-444553540000} to T=BU0836A InterfaceT.GUID={8C6FD830-FE13-11E2-8001-444553540000} and now also remove this: A=BU0836A InterfaceA.GUID={8C6FD830-FE13-11E2-8001-444553540000} John

As I said, I need to see your joyscan.csv and log files, as well as your current ini - could you please attach all 3. If your devices are recognised by windows as joystick/HID devices then they should be recognised by FSUIPC.

Ok, if the throttle is distinct from the BUO836A interface ignore my last comment. So just the throttle not being seen now? Can you post your log and joyscan.csv files.

Log files 1 and 3 are as expected. Log file 2 shows it did connect but took quite a while. Could it have been waiting for P3D to start, or was it already fully up and running when you started WideClient? Did you get the '...no longer works' message?

If the throttle is now registered as Buo836a, then change these lines T=G-Throttles << MISSING JOYSTICK >>T.GUID={048B2C90-D690-11E1-8001-444553540000} to T=BU0836A InterfaceT.GUID={8C6FD830-FE13-11E2-8001-444553540000}

The text between the '-{..}-' characters are comments to make the ini file more readable. As you are not changing the controls, the comment is being re-written to the specified control. You just need to change the actual controls, so it would be: 24=P1,15,C70600,0 -{Custom control: <70600>}-25=U1,15,C70600,1 -{Custom control: <70600>}-26=P1,15,C70601,0 -{Custom control: <70601>}-27=U1,15,C70601,1 -{Custom control: <70601>}-28=P1,16,C70602,0 -{Custom control: <70602>}-29=U1,16,C70602,1 -{Custom control: <70602>}-30=P1,16,C70603,0 -{Custom control: <70603>}-31=U1,16,C70603,1 -{Custom control: <70603>}-

Click your start menu, in the search box, type 'command' - the top option will be 'Command Prompt' (or something similar, depends on Windows version and what you have installed). Select the 'Command Prompt' option. A window should open. In that window, type 'cd <your install directory>', whatever your install directory fore WideClient is, use that (is it 'C:\Users\Peter\Downloads\WideFS'? Are you running from your download directory?). When you are in the directory, type 'dir' to get the folder contents. Anyway, its really a lot easier using Windows Explorer. Did you try changing your folder options to see hidden file types? Google is your friend in these matters! John

That strange - are you using a text editor/viewer rather than a pdf viewer? Try opening it in your web browser (as that should have support for viewing pdfs). If you ares till having issues with this, I can post you another copy, but I doubt very much your files have been corrupted... I guess you solved this as your FSUIPC5.ini has the following: First, try and sort out your problem with the user manuals - you really need these! For axis assignments, you need to decide whether to assign in P3D or FSUIPC. If you assign in P3D, you can still calibrate in FSUIPC. But if you decide to assign in FSUIPC, it is better to disable controllers completely in P3D. Anyway, I see you are using ProSim which I believe has its own calibration system - probably best to wait for Pete to return and help you with this (as he is a ProSim user). Your FSUIPC ini file shows that your previously assigned devices are no longer used, due to the change in GUIDs. You therefore need to update your ini file to correct this. As you have two sets of yoke/pedals, I'm not sure which way around your assignments go, but as the assignments to each seem to be similar, it shouldn't matter too much. You do have one device missing - your throttle (G-Throttles) - is this not connected? Try replacing this section: [JoyNames] AutoAssignLetters=No T=G-Throttles << MISSING JOYSTICK >> T.GUID={048B2C90-D690-11E1-8001-444553540000} B=BU0836X Interface << MISSING JOYSTICK >> B.GUID={2A723950-D706-11E1-8001-444553540000} R=Saitek Pro Flight Rudder Pedals << MISSING JOYSTICK >> R.GUID={7007B920-BD3B-11E1-8001-444553540000} S=Saitek Pro Flight Rudder Pedals << MISSING JOYSTICK >> S.GUID={75984520-D704-11E1-8001-444553540000} Z=737YOKE-LE by ACE << MISSING JOYSTICK >> Z.GUID={5EA0F8E0-D70D-11E1-8001-444553540000} Y=737YOKE-LE by ACE << MISSING JOYSTICK >> Y.GUID={B7B896E0-D70D-11E1-8002-444553540000} 1=Saitek Pro Flight Rudder Pedals 1.GUID={E98E5CA0-5C91-11E1-8006-444553540000} 2=737YOKE-LE by ACE 2.GUID={6368B4F0-476D-11E2-8001-444553540000} 3=737YOKE-LE by ACE 3.GUID={E98E5CA0-5C91-11E1-8009-444553540000} 4=Saitek Pro Flight Rudder Pedals 4.GUID={E98E5CA0-5C91-11E1-8005-444553540000} 0=BU0836A Interface 0.GUID={8C6FD830-FE13-11E2-8001-444553540000} with the following [JoyNames] AutoAssignLetters=No T=G-Throttles << MISSING JOYSTICK >> T.GUID={048B2C90-D690-11E1-8001-444553540000} B=BU0836X Interface B.GUID={8C6FD830-FE13-11E2-8001-444553540000} R=Saitek Pro Flight Rudder Pedals R.GUID={E98E5CA0-5C91-11E1-8006-444553540000} S=Saitek Pro Flight Rudder Pedals S.GUID={E98E5CA0-5C91-11E1-8005-444553540000} Z=737YOKE-LE by ACE Z.GUID={6368B4F0-476D-11E2-8001-444553540000} Y=737YOKE-LE by ACE Y.GUID={E98E5CA0-5C91-11E1-8009-444553540000} 1=Saitek Pro Flight Rudder Pedals 1.GUID={E98E5CA0-5C91-11E1-8006-444553540000} 2=737YOKE-LE by ACE 2.GUID={6368B4F0-476D-11E2-8001-444553540000} 3=737YOKE-LE by ACE 3.GUID={E98E5CA0-5C91-11E1-8009-444553540000} 4=Saitek Pro Flight Rudder Pedals 4.GUID={E98E5CA0-5C91-11E1-8005-444553540000} 0=BU0836A Interface 0.GUID={8C6FD830-FE13-11E2-8001-444553540000} Let me know how you get on. John

No, choose WideFS and use your WideFS registration details!

Hi Tasso, knob's usually send controls. In this case, its the 'Attitude Pitch Trim' which *should* (I guess) send controls for 'Attitude Bars Move Down' and 'Attitude Bars Move Up'. However, whether and how these work or not is completely dependent upon the aircraft implementation. For example, in A2A's Cherokee, you can get/set this value (i.e. the trim value itself) using the Lvar 'AttitudePlane', e.g from https://www.avsim.com/forums/topic/443151-a2a-piper-pa-28-cherokee-180-module-version-11/ , here's a couple of lua function that controls this knob for this aircraft: function A2A_Pitch_Att_inc () local PAtt = ipc.readLvar('AttitudePlane') PAtt = PAtt + 1 if PAtt > 7 then PAtt = 7 end ipc.writeLvar('AttitudePlane', PAtt) end function A2A_Pitch_Att_dec () local PAtt = ipc.readLvar('AttitudePlane') PAtt = PAtt - 1 if PAtt < -7 then PAtt = -7 end ipc.writeLvar('AttitudePlane', PAtt) end Depending upon which aircraft you are using, something similar may be available. There is no offset for actual attitude pitch trim value itself, and there is no simulator variable for this. The offsets for the Attitude Indicator are: 2F70= Attitude indicator pitch value ( in degrees) 2F78=Attitude indicator bank value ( in degrees ) There is another read-only simvar for 'Attitude Bars Position', however this is not currently stored in an offset. Hope this helps, John

Possibly, although you could try the 'Device Cleanup' tool (with devices disconnected) available from here: https://www.uwe-sieber.de/misc_tools_e.html I've not used this myself though! Oh - and make sure you back-up your registry first, just in case!

Its really not needed as you already have a license. I just checked and its fine to use distinct names and email addresses for FSUIPC and WideFS, you just need to run the installer twice, register FSUIPC the first time, and WideFS the second (do not choose the 'Both' option!). Not an option, sorry. No, its not needed with FSUIPC5. It uses the SimConnect interface built into P3D.

In FSUIPC? Your ini file shows no assignments. Its basically empty. Did you install the saitek drivers? If so, you need to uninstall these first. Disconnect all your devices, uninstall any associated devices from the device manager, reboot your PC and then reconnect your devices. If you still get duplicate devices, you will have to clean your registry. Regards, John

Start a command prompt, change directory to your WideClient folder, then list the contents of that directory. There must be a log file there, as well as an ini.

Sorry, I don't understand. You get that message from running the 'Install FSUIPC5.exe' program? That is not possible. That is the error you get when you try and run WideClient on a PC where FSUIPC is already running (i.e. in P3D) or WideClient is already running.

You can register WideFS with a different email address but I'm not sure about the name. Did you try re-running the installer to register WideFS with the details from your registration email? If not, please try that first. If this doesn't work, if you PM both your FSUIPC5 and WideFS registrations to me, I'll see if I can generate you a new key for WideFS with your FSUIPC5 details