• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

P3D v4 Troubles with AFLT

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
 
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
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