John Dowson

Ok, thanks for testing Niberon. I'll release officially this as v6.0.4 in the coming days. John

Ok, thanks for reporting back.

Hi Percy, What do you mean by this? What aircraft are you using? Nothing has changed between FSUIPC5 and 6 with regards to mouse macro functionality. I verified mouse-macro functionality on P3Dv5 with the macros I have/use, and found no issues. Given the above, I'm not sure. I don't think I've seen a switch or button with a drop-down menu - could you elaborate? Thanks, John

Hi Andrew, strange and confusing results...any ideas as to what is causing P3Dv5 to crash? Could you try the following dll please (6.0.3d): FSUIPC6.dll It has additional logging. Start with only the following in your ini: Debug=Please LogExtras=1 Just before you close the session, go into the logging tab and set the extras value to 8197. If you could then generate a log when iy hangs. Thanks, John

Hi Niberon, could you try the attached dll for me please: FSUIPC6.dll If that works, I'll update the documentation and release later in the week. John

Do you have the VRIDisableCMDRST parameter set to Yes in the ini by any chance? I am very surprised that the first dll didn't work (which is actually 6.0.3a but I forgot to update the character string, sorry) as this should be equivalent to FSUIPC5... I'll discuss with Pete to add some logging to try and track down this issue...

Did you click the Register button?

And also please try this one: FSUIPC6.dll The first dll above is compiled against the same Windows SDK as FSUIPC5, so hopefully that one should work. The one attached in this post is compiled against an intermediate SDK. It would be useful to know if this one works or not as well. Thanks.

Just checked and I forgot to update version for IPC in the header. I will correct this in the next release.

Yes, forgot to mention that, sorry - I'll update that topic. John

Hi Andrew, could you try this dll please: FSUIPC6.dll

Your COM ports cannot be opened: 969 VRI port 1 "COM2" failed to open 969 VRI driver port 1 "COM5" failed to open 985 VRI port 2 "COM6" failed to open 985 VRI driver port 2 "COM7" failed to open Is VSPE running? Try adding the logging flags, as suggested: Debug=Please LogExtras=4 You also seem to have two [General] sections in your ini, with the first one prefixed by '!1=n' which will be make that section be ignored. Either delete that whole section, or remove those characters before the section name and also the other [General] section.

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