P3D v4 Troubles with AFLT

#1
Don,

Sorry, but as for SAMM, my PC (Win 10 x64, and P3D v4.3 as clean install after complete uninstall of former version) lets AFLT return the same message "No version of FlightSim found in system registry. AFLT cannot continue...etc)

Creating an ini file with this single line "Path to P3Dv4=F:\Prepar3D v4" allows generation of following ini file
Path to P3Dv4=F:\Prepar3D v4
Path to P3Dv4 SDK=F:\Prepar3D v4 SDK 4.3.29.25520
Path to P3Dv4 Compiler=F:\Prepar3D v4 SDK 4.3.29.25520\World\Scenery\BglComp.exe
Dialog Width=678
No Check For Update=False

Would it be possible to get a sample of a normal ini file as generated by AFLT?
Thank you for your comprehention and assistance.

Philippe
 
#2
Don,
Sorry... Disregard above message... found the origin of this non-detection...
My HKCU\Software\Lockheed Martin\Prepar3D v4 section showed an AppPath F:\Prepar3D v4\...
Removing the three dots did allow AFLT to open and find my P3Dv4 without troubles.
I really do not know where these 3 dots came from...

It further seems that firing up P3D v4 automatically creates again into my registry
HKCU\Software\Lockheed Martin\Prepar3D v2
HKCU\Software\Lockheed Martin\Prepar3D v3
HKCU\Software\LockheedMartin\Prepar3D

The following keys are OK and evidence actual SetupPath
HKLM\SOFTWARE\Lockheed Martin\Prepar3D v4
HKLM\SOFTWARE\Lockheed Martin\Prepar3D v4 Content
HKLM\SOFTWARE\Lockheed Martin\Prepar3D v4 Scenery
HKLM\SOFTWARE\Lockheed Martin\Prepar3D v4 SDK

Blue skies
 
Last edited:

gadgets

Resource contributor
#3
I thought I had made a change in the registry software to ignore those three dots. I'll check again.

Thanks for letting me know.

Don
 
Top