While waiting to purchase the FSUIPC6 as mentioned in last post, I popped up an idea: “Why not test the existing FSUIPC5 with the new P3D first?”

So I copied the DLL.XML from the configuration directory of P3Dv4 to the directory of P3Dv5.

Bingo!

They work together nicely.   I don’t even need to modify the file at all.   Just copy and paste the DLL.XML from the v4 directory to the new v5 directory and then all is set.

The two folders involved are as follows:

C:\Users\<user name>\AppData\Roaming\Lockheed Martin\Prepar3D v4

C:\Users\<user name>\AppData\Roaming\Lockheed Martin\Prepar3D v5

They are the folders where Prepar3D.cfg and DLL.XML are located.

Alternatively, you could copy the whole Module folder which contains all FSUIPC files from P3Dv4’s application directory to the one for version 5.  Then correct the path of FSUIPC in the DLL.XML file accordingly.

Surely the new FSUIPC6 will have additional improvements and update support.  But it’s still good to see the older FSUIPC5 has no problem supporting the newer P3Dv5.

The delaying of putting the new FSUIPC on the shelf by the shopkeeper seems not a bad idea, after all.