• 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 v5 REIL lights

I had no ini at the first start,
That's intentional. AFLT will look for (and hopefully find) all installed versions of Flightsim on its first running.
 
This seems to be proof-positive that Win 11 changes the registry location of the key elements used by AFLT (and all my other apps and other apps such as ADE) to determine the locations of the various Flightsim variants.

As I have said on previous occasions, my system is not capable of running Win 11 and, at this stage, I'm not about to invest in a new computer. But, I someone identifies the path Win 11 uses for each variant and tells me how I can determine whether or not Win 11 is running, I'll do my best to update my registry searches.
 
I’ll try this!
unfortunately didn't work for me, just getting an error after clicking ok...
aflterr.png
=>
************* Exception text **************
System.IO.DirectoryNotFoundException: Could not find part of the path "C:\Users\ADMIN\Documents\Prepar3d v5 Add-ons\AFLT for P3D\Scenery\scenery".
в System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
в System.IO.FileSystemEnumerableIterator`1.CommonInit()
в System.IO.FileSystemEnumerableIterator`1..ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler`1 resultHandler, Boolean checkHost)
в System.IO.Directory.GetFiles(String path, String searchPattern)
в Microsoft.VisualBasic.FileIO.FileSystem.FindPaths(FileOrDirectory FileOrDirectory, String directory, String wildCard)
в Microsoft.VisualBasic.FileIO.FileSystem.FindFilesOrDirectories(FileOrDirectory FileOrDirectory, String directory, SearchOption searchType, String[] wildcards, Collection`1 Results)
в Microsoft.VisualBasic.FileIO.FileSystem.FindFilesOrDirectories(FileOrDirectory FileOrDirectory, String directory, SearchOption searchType, String[] wildcards)
в AFLT4._5.MakeLibrary.SaveXML()
в AFLT4._5.MakeLibrary.PrepareXML()
в AFLT4._5.MakeLibrary.SaveLibrary()
в AFLT4._5.MakeLibrary._Lambda$__R19-1(Object a0, EventArgs a1)
в System.Windows.Forms.Control.OnClick(EventArgs e)
в System.Windows.Forms.Button.OnClick(EventArgs e)
в System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
в System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
в System.Windows.Forms.Control.WndProc(Message& m)
в System.Windows.Forms.ButtonBase.WndProc(Message& m)
в System.Windows.Forms.Button.WndProc(Message& m)
в System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
в System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
в System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
 
I've had this problem before, when AFLT adds "scenery" to folder names. It seems to come and go. Try creating a Scenery folder inside the AFLT for P3D folder and try again. If that doesn't work, try adding a Scenery folder INSIDE that new Scenery folder.
 
All necessary folders in the AFLT for P3D folder are created automatically and named as the project. I have no idea how a folder named "scenery" could get into AFLT for P3D\scenery folder, nor has that phenomona been reported previously to my recollection, unless the project is named "scenery" or it is manually placed there.

For more info on the AFLT for P3D folder, please refer to the SDK Section "Add-ons"
 
I mentioned previously that AIFP did this (added an extra scenery folder to the path) in an FS9 project I was working on. Probably unrelated though.
 
I've had this problem before, when AFLT adds "scenery" to folder names. It seems to come and go. Try creating a Scenery folder inside the AFLT for P3D folder and try again. If that doesn't work, try adding a Scenery folder INSIDE that new Scenery folder.
i created these two folders ( C:\Users\ADMIN\Documents\Prepar3D v5 Add-ons\AFLT for P3D\Scenery\scenery) manually and it worked;)
 
All necessary folders in the AFLT for P3D folder are created automatically
probably this is again some kind of problem with Cyrillic characters and the tool cannot create the necessary folders, only if i do it manually it works:
well, I was able to turn on the lights I needed, but this always requires the autolaunch (via add-on.xml) of an additional tool(part from AFLT), as I understand it, it manages the code from .xml e.g:
<SimObject Name="1_Light_0">
<Placement Lat="-17.560792876189" Lon="-149.618010929811" Alt="0.5" AGL="True" Hdg="74.13"/>
<Model SimTitle="1_Strobe_Light_Controlled" Type="STROBE">
<ConditionalVisibility AlwaysOn="False" Heading="74.13" Spread_H="180" Spread_V="90" Range="10" PCL="True"/>
<Flash Duration_Seq="1200" Flashes="16" Duration_Flash="75" SeqNum="2"/>
</Model>
</SimObject>
it is very similar to sode .xml code, but i checked it doesn't work with sode( just doesn't read some values)...
Accordingly, you will always have to use an additional tool (part from AFLT), moreover, the folder with AFLT for P3D should have a higher priority than the scene itself, otherwise the lights may not appear at all...
 
Last edited:
Niksan29, I can only refer you to the User manual. The things you are "discovering" are all discussed near the front.

As you have discovered, AFLT for P3D operates quite differently internally from AFLT for FS9/FSX. The reasons for this are fully discussed in the user manual.

If you stop looking for ways to use it differently than I intended, you might have better success.
 
If you stop looking for ways to use it differently than I intended
no, I was just trying to add lights as it is intended. I didn't meet any problems, but thanks to the help of the participants, all of them were resolved at the moment...
 
Back
Top