John Dowson

Yes, it should I will correct that, thanks.

You should not install FSUIPC6 into this folder really, although it will do no harm. There must be an FSUIPC6 folder under this, that contains the add-on.xml. You can install FSUIPC6 in there if you like, but it is better to install outside of this folder really(e.g. mine is in E:\FlightSim\P3D Add-ons\FSUIPC6). Note that if you have (or will) install any other add-ons into P3Dv5 via the xml add-on method (which is now the recommended method by Prepar3d), then the add-on.xml for these will also be created in a folder under "C:\Users\***\Documents\Prepar3D v5 Add Ons". This folder should just contain a list of folders, one for each add-on.

You only have to do this once. When you re-install, you can just skip this stage by clicking the 'Next' button. I see no need to have a 'check' function. What I would like to do, when I get a chance, is to maybe pre-populate the registration panel fields from your key file if already registered. I know, this annoyed me, but there is not an easy way around this as its not supported by the tools I am using. I will write my own tool for this at some point, but not sure when this will be.

No, its not correct, and that is not in the instructions. The instructions say to rename and copy to your installation folder.That is not your installation folder. When you install FSUIPC6, you can select the folder in which you want to install. If you choose the add-on.xml method (which is the default), then a folder called FSUIPC6 will be created under your Documents\Prepar3D v? Add-ons folder (where ? is replaced by 4 and/or 5, depending which versions you choose to install into). You could (and should) choose to install FSUIPC6 itself in another folder, although the installer will also default to this folder for a clean install. If you previous have FSUIPC5 or 6, then it will default to the existing folder to install (usually the Modules folder). You could check/post your install log (which is in the installation directory and also a copy with the installer) which would tell you what is installed and where (and what you previously had installed). Can you check that you don't have the 'Allow the computer to turn off this device' checked on your USB devices. If thats not it, I need to see your log file. It is not possible to have 2 installations for one sim. Probably a good idea to uninstall and start again, and make note of where you have installed. Then, after installation, copy your FSUIPC5.ini file to that folder and rename it. John

That is just showing the unregistered version. You have to register at the end of the install process, enter your details and click the Register button. You will get a pop-up telling you if your registration is successful or not. Did you do that? What did the pop-up say?

What has this got to do with your original question, which was related to registration (and also under an unrelated topic title)? If you have new issues, please create a separate topic, with an appropriate title. Thanks, John

Hi Pierre, first, you posted in a sub-forum - please post all support requests in the main forum. For your actual problem, please download and try the latest release (6.0.3). There was a patch released yesterday that correct a problem with flight plans between v4 and v5 in a shared installation. If that doesn't solve your issue, please report back. Regards, John

Think there is maybe a discrepancy as the IPC version number is 6003 (maybe should be 6030). With the FSUIPC6 release, I am trying to change the visible version number to the format <major>.<minor>.<patch><addedLetter for internal release>, but keep the internal numbers as they are. The patch level uses the last two digits so that I can go above 9 in the visible version. Maybe I've specified this incorrectly, I'll check sometime next week. John P.S. Major should be 6, minor 0, and patch/number should be 3 (with latest release). Will check the offsets later.

Hi Joesen, we do not provide bespoke support like this - its just not possible with the amount of users and time that support requires. We provide the information and help for you to solve the problems yourself. Please re-read the information already given and read the documents. John

7x7 here at the moment, unfortunately...was hoping to take the afternoon off! Wish people would just RTFM...., which would solve 99% of problems! Glad it's now working for you. Regards, John

Hi Stephan, yes, there looks to be a problem validating your WideFS7 key. Not sure what the issue is yet, I will investigate. This is the 2nd occurrence of this problem. In the mean-time. I have PM'ed you a key file that you can use. Cheers, John

Best to put your installation back to how it was originally installed (by the installer) first, otherwise you will have a discrepancy with what and how the uninstaller thinks you have installed and what you have changed. The uninstaller removes the reg keys after the end of a successful uninstallation, but this will not happen if it fails at some point, if you have confused it by manually changing install locations or methods. Cheers, John

Ok, will check these but will probably be tomorrow now - thanks for your patience, John

Hola Gilbert, first, you posted in the 'Download Links' section. Please post all support requests in the main support forum, not in one of the sub-forums. There are also many similar support requests. Did you check these for your solution? Did you read the installation and registration guide? Your advice you are looking for is almost certainly in one of these locations. As you have not provided any specific information as to what your problem is, other than 'it dont work', I cannot advise further. So, please read the installation guide first. Saludos, John

Btw, there has been a few patches (current version 6.0.3) that improves the handling of certain bits of functionality (flight plan loading, auto-save) between dual installations.

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