John Dowson

Hi Luke, you should have read the installation and registration guide - this is explained there. Really, its better to let the installer/uninstaller do this for you. You should have re-ran the installer and selected just one P3D version to install into. This would then automatically uninstall your previous (duL) installation, and install into the selected sim. You can then re-run the installer, select the other P3D version, and install into a different directory. The options for this are explained in the installation guide. Making manual changes may confuse the installer/uninstaller, as it reads registry keys to determine if and how it was previously installed. Manual changing the installation method/location will invalidate these keys, giving a discrepancy as to what is installed where and what the installer thinks is installed (via these keys). This will cause problems running the uninstaller or running the installer again. Cheers, John

No - it is not possible for FSUIPC6 to overwrite the ini if it is there. Are you sure that you copied it to the correct place? Do you still have the original - if so, maybe try again (and post that) I have no idea why no devices are being recognised though, although this is a separate problem. Are your devices recognised by Windows? How about in P3D (I see you still have controllers enabled there)? Btw, there have also been a few minor updates over the last few days, latest version if V6.0.3. Please download and install that, although I don't think that will make any differences to your issues. John

Are you using the latest FSX-SE beta? If so, please see

Could you let me know your FSUIPC6 and WideFS7 order numbers please and I'll check them here. Thanks.

But there are no profiles set-up in your ini. In fact, the ini is nearly empty (i.e. default), and only shows 4 axis assignments to one device, although no devices are detected, which is very strange. Did you rename your FSUIPC5.ini file to FSUIPC6.ini? Please see the installation manual on how to preserve your settings.

Try the WideFS user guide, its described there. As fully described in the WideFS user guide (see the "configuring" section), for broadcasts to work you MUST have at least WinXP SP1 or later on each PC, and all PCs must be in the same Windows workgroup. If you don't want to rename one or other of your workgroups so that they are the same, or they are the same but something else is using the broadcaster port already (Port2 in your INI files), you can instead add the ServerName and Protocol parameters into the INI. John

Before you send the log, could you activate logging for buttons and key operations. Close FSUIPC then re-open, go the Buttons & Switches tab, then try operating a few buttons to see what is getting logged. Close down the sim so the log closes properly.

There are now many posts on the same topic, and the answer is still the same: did you click the Register button in the registration dialog of the installer? If so, what did the pop-up say? Did you check the installation and registration guide? Btw, there is a newer version, 6.0.3, containing a fix for the auto-save feature in dual installations. Better to upgrade even if you don't use this feature.

But what about P3D4.5 with FSUIPC6?

Or use this: PFChid64.dll

Could you first download and install the latest version (6.0.3) - there have been a few minor fixes released this morning which affect dual installs. It could also be a corrupt weather file - these were not removed correctly in the previous version (fixed in 6.0.3). Try manually deleting your wxstationlist.bin file (in same folder as your Prepar3D.CFG file), it will be re-created the next time you start the sim.

That is strange. Probably a good idea to uninstall FSUIPC6 (using the uninstaller created in your installation directory or via the windows app management panel) and also to manually uninstall FSUIPC5 (remove the FSUIPC5 entry from "C:\Users\User\AppData\Roaming\Lockheed Martin\Prepar3D v4\DLL.xml" and delete "C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.dll" if it exists. Then re-run the FSUIPC6 installer.

Do you have axis assigned in P3D? If so, remove them, or, better still, disable controllers completely in P3D if you are doing all your assignments in FSUIPC. Note that P3D has a tendancy to re-assign your axis when recognised if you do not disable controllers. If thats not your issue, could you please post your ini and log files.

Can you download and try the latest version (6.0.3) as this seems to have fixed the UI issue. As for your zapper issue, I'm not sure but it may have to do with your Cylinder Alt Difference setting. I'll check this in the coming days but there are currently quite a few things at a higher priority, so this may take a while. Let me know if the latest version fixes your UI issue please. John

It should be version 5.1.3. I've just re-upload the zip - can you download and try again please. John

It has to go with the FSUIPC6.dll, in the installation folder that you selected during the installation process. If you cannot remember where that is, use the 'Open Folder' button in the FSUIPC Logging tab. John

So this occurs with FSUIPC6 being the only add-on? Could you download and try v6.0.2 please. No specific fix for this (as I cannot reproduce) but I would like to know if the problem still exists in this version for you.

If you choose to. When you run the installer, you can select the P3D versions in which you want to install FSUIPC6. If you select both, you will have a single FSUIPC6 installation for both sims. Or you could just select v5 and just install it there, keeping FSUIPC5 for P3Dv4. Or you can run the installer twice, and have separate FSUIPC6 installations for each sim, up to you. WideFS is comprised of WideServer and WideClient. The WideServer element is built-into FSUIPC from version 4 onwards, so WideServer will be available when you run v4 or v5 with FSUIPC5 or 6. Just make sure you also register your WideFS key when you register your FSUIPC6 key. That shouldn't be an issue. Maybe use separate installations initially while you do this. You can always combine them later (by just re-running the installer and selecting both sims to install into) if needed. John

Sorry, but that picture is far too small to see anything - and also shouldn't be posted if it shows your registration details... Are you registering both FSUIPC6 and WideFS or just FSUIPC6? If the former, are you registering with the same or different name and/or email? What do the pop-ups actually say? Maybe you can give me your order numbers and dates of purchase and I can check the registration here.

I meant the updated one I posted above. It should hopefully work for your set-up, but its not easy for me to test this fix myself right now. If you mean it's too late, then hopefully this issue will be fixed the next time you install..

Could you possibly try that installer first?

No need to do that! The software should be able to handle your set-up....

Hi John, could you try this installer for me please: http://www.fsuipc.com/download/Install_FSUIPC6.zip This should create a Docs folder in your selected installation directory if it can't write to your windows Documents folder. Thanks, John

Ok, thanks. An FSInterrogate document is also installed in the Documents folder if FSInterrogate is installed, so it may be that. The installer currently also aborts if it can't write to the Documents folder. I'll revise this over the weekend. Would be good to know why it can't write there though - I'll do some tests on this over the weekend as well.

You should have just turned off documents, and selected the others as required. Could you also try creating an FSUIPC6 folder in your Documents folder (OneDrive) to see if it installs with this pre-created? I'll look into this over the weekend, and maybe default to a Documents folder under the installation directory if it can't create one in the Documents folder. I can also make the documents available to you separately if you like, although please try the above first. John