FSDreamTeam forum
Products Support => JFK for FSX/P3D => Topic started by: Mower on September 06, 2016, 02:43:19 am
-
Hi guys, I have the latest FSDT JFKV2 installer and it does not see my licensed P3D.
Antivirus is disabled.
What files is it looking for? I had to make some alterations to the P3D executable to get Ultimate Traffic 2 and TIR to work, it's now called P3D.exe. However, changing that file back to it's default name made no difference. What exactly is the installer looking for?
I have FSX SE installed and the installer sees that.
Cheers.
-
What files is it looking for? I had to make some alterations to the P3D executable to get Ultimate Traffic 2 and TIR to work, it's now called P3D.exe. However, changing that file back to it's default name made no difference. What exactly is the installer looking for?
The P3D registry keys should point to the correct folder AND a Prepar3d.exe executable, of the correct version (meaning=not manually altered) must be there.
If the installer doesn't see your P3D, it can only due to one of the following, or a combination of all of them:
- The P3D registry key is not pointing to the folder you have installed P3D.
OR
- The executable is not named Prepar3D.exe
OR
- The file version of the Prepar3D.exe.exe doesn't match a supported version. The installer doesn't care about the build, it only checks if the major version is 1, 2 or 3 for P3D.
-
Understood. Thanks for the quick reply. I will check these issues and advise back.
-
"- The executable is not named Prepar3D.exe"
That resolved the installer not finding my P3D v3.
Now I ran into a new issue during install that a forum search didnt find a fix.
(http://img.photobucket.com/albums/v340/Mower/fsdt1_zpszltjgrzl.png) (http://smg.photobucket.com/user/Mower/media/fsdt1_zpszltjgrzl.png.html)
(http://img.photobucket.com/albums/v340/Mower/fsdt2_zpsmdhrjida.png) (http://smg.photobucket.com/user/Mower/media/fsdt2_zpsmdhrjida.png.html)
-
Now I ran into a new issue during install that a forum search didnt find a fix.
Yes, this has been discussed here, and it's a result of your XML file being corrupted, either by another faulty installer, or by having edited by hand, see here:
http://www.fsdreamteam.com/forum/index.php/topic,12680.msg104212.html#msg104212
-
Cheers, brother, for the excellent support.