John Dowson

offset 3308 will contain the same value for P3Dv5 as P3Dv4 - 12 (for P3D 64-bit). You can use offsets 3304 and 3124 to determine the FSUIPC or P3D versions respectively, if needed. Cheers, John

It isn't. What makes you think that? Have you read that post? Its not free for ANY user (ie. a registered copy), BUT I will supply a new key free of charge to those users who have purchased FSUIPC5 on or after 1st Feb 2020, offer lasting until the end of May. keys for WideFS7 are still valid for FSUIPC6. John

Yes, please re-read that post - here's the pertinent section: For those users who have recently (i.e. on or after 1st February 2020) purchased FSUIPC5 but will be updating to P3Dv5, I will supply a free license if you PM (or email) me your registration details (order number and date). As always, PLEASE DO NOT publish your key details in any public forum (or your key will be banned). This free upgrade offer is valid until the end of May 2020 only.

Glad its working for you now Pete - if your happy, I'm happy! Strange about the crash though, but if its now working I wouldn't worry. Cheers, John

Hi Peter, That is strange - are you using the same ini file (renamed of course)? I doubt it, as it is working in P3Dv4.5. I don't know - maybe. You shouldn't need SPAD for throttle quadrants - only the switch, radio and instrument panels would require SPAD (or SPAD.next). Do you have the saitek drivers and software installed? If so, best to remove them. If you aren't using the same .ini file as for P3Dv4.5, then try that first (copy your FSUIPC5.ini to FSUIPC4.ini and move it from your P3Dv4 Modules directory to your FSX one). Also, if you are using an add-on aircraft, please also try with a default one to see if you get the same results. If its still not working, post your .ini and .log files and I'll take a look. Cheers, John

There should be a copy of the installer log in a file in the same folder as the installer (if you can't see the .log extension, you may have to disable the hiding of this file type via the Explorer options). Note that if you have installed the latest FSX-SE beta then please see this pinned post: Its not clear from that post, but I think you need to install the non-beta first before installing FSUIPC4, then upgrade to the latest beta and download and use the special dll that supports the beta. Please see the following post for further details: If thats not your issue, then please attach your installer log.

Yep, there is no change in installation details between FSUIPC5 versions.

Hi Paul, yes, 0x3308 will still be 12, for P3D 64-bit. John

Hi Marc, Paul, Offset 3124 will contain the new P3dVersion number (50), and offsets 3306 will contain the FSUIPC version number as 0x6000 (U16) with the version letter at offset 3304 being 0x0. Hope thats clear - let me know if you need anything else. John

Ok good! Thanks for reporting back. John

By the way, I have just noticed that you have hijacked a Topic that is over 10 years old ! It would have been better to have started a new Topic! John

Its probably not too clear from that FAQ entry (I will update), but you cannot use the installer for the Beta version. You have to first run the FSUIPC installer on the latest normal version, then run FSX-SE and close. You should then update FSX-SE to the Beta version and then replace the special FSUIPC4.dll for FSX-SE Beta in the Modules folder (by overwrite the existing one). John PS. Also see

Then you need to read this, as I said in my initial post :Support for the "BETA" version of FSX-SE (build 63003) John

...there should also be a copy of the install log in the same folder as where you ran the installer. Note also that you need to run the sim at least once after installation before you run the FSUIPC installer. John

Yes. You will need to rename your FSUIPC5.ini file to FSUIPC6.ini. This should be explained in the installation manual. Cheers, John

Not quite. It also installs the documents (user manuals, etc) and updates the sims DLL.xml file to start the FSUIPC dll when the sim starts (which I guess is part of the dll installation). It will be in the Modules folder, under you sim installation directory, where the FSUIPC4.dll is installed. If you cannot see it, you may have to un-check the option 'Hide extensions for known file types' in the Explorer options, so you can see the file types ini / log / txt ... Does this mean that you are not using the latest FSX-SE beta? Do you have both FSX and FSX-SE installed? If so, check both sim folders for a Modules folder. John

Yes, should be on SimMarket on Wednesday or Thursday. I can't get it up any earlier due to the Easter weekend. Regards, John

Glad you fixed it...and quickly! Presume you mean FS-Interrogate2 though! John

Thanks Ålvaro - and same to you! John

Please see:

Please see :

If you have assignments in P3D, then you will have to just remove the axis assignments and leave your controllers enabled. The problem with this is that you might find that P3D will sometimes automatically detect these as new axis and re-assign them, which would then cause problems due to duplicate assignments (in P3D and FSUIPC). This may work ok, but the alternative would be to disable controllers completely in the sim and do all your assignments through FSUIPC. Depends. MakeRwys just scans your scenery to collect data on runways and makes this available for use by other programs. You do not need this to use FSUIPC. That is strange, and I would suggest that you check the calibration in windows, but you also say so the windows calibration must be ok. You can try assigning and calibrating in FSUIPC to see what values you get there. Cheers, John

Or you could maybe try setting UseAxisControlsForNRZ to Yes - see the Advanced User Guide. John

Are you using the latest FSX-SE beta? If so, please see the following post: If not, please attach your installation log. John

I cannot see your pinterest links. Please just attach your log.