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

AFLT does not copy the textures

Mr.Crocodile

Mr.Crocodile

Messages
243
Country
italy
Reading the manual, I remembered that AFLT should copy the related texture in the texture folder of the scenery indicated in the program field (page 4 of the AFLT User Manual). But for some strange reason it does not happen and when I create a new light library, the program does not copy the related textures to the indicated folder. Is there any reason for it?
This is happening both with AFLT 3.1.02f and 3.1.03

Ciao
 
This has not previously been reported and, without your Library Folder I have no way of knowing. Since you seem to imply it worked before, perhaps you didn't properly identify the destination scenery folder when you set up the Library folder. Open the file Library.ini in the Library Folder. It will identify the scenery folder path. If that's not the correct path and you are unable to change it from the Main Panel, edit Library.ini with any text editor while AFLT not running.

As I posted elsewhere in this forum, I am preparing for an extended absence and so don't have the time to investigate right now. As well, I'm working on a much improved version of AFLT that will be announced soon.

Don
 
Yes, I'm sure that it worked before using the early version 1. Probably I forgot to pay attention to it using the version 2 (for sure I added manually the textures with one of my last scenery made using old version 2). Then I started to use version 3 and only a few days ago, as told above, reading the manual I remembered that the program should copy the texture automatically and I noticed that it did not happen.
I just checked the Library.ini file and it seem to correctly indicate the scenery folder path.
The strange thing is that the .bgl library file is correctly copied into the scenery folder, but not the texture in the related texture folder.

Code: 
Scenery Folder Path=\\ASUS-2GHZ\Flight Simulator 9\Addon Scenery\LIPO_Brescia-Montichiari
P3D ID=LIPO
Light Model=Stop Bar AB
PCL Control=
PCL Control Value=
PCL Auto-Off=0
Airport Operates 24hr.=True
Airport Opens=0
Airport Closes=1439
Airport UTC Offset=0
yBias_Approach=0
yBias_PAPI/VASI=0
yBias_Wigwag=0
Last Array Accessed=
Array Display Complexity=NORMAL
Make Library For=0
Path to Airport .bgl=
Base FileName for Libraries=LIPO_TaxiLight_LIB
Select Model List=0
Override - Effects=False
Override - All In One=False

The path is related to a network pc (not the same where I work for the scenery but the one where I have the simulator) and obviously the path has all the read/write sharing authorisations.

Anyway at the moment it is not a big issue for me.
 
Thanks for checking the Library Folder. Since no one else is reporting a similar issue, I suspect it has sometime to do with the network path. AFLT doesn't "know" anything about network paths. Perhaps AFLT doesn't recognise it as a valid path for textures. I'll check. Perhaps this can be avoided in the new version.

Don
 
As soon as I have one minute I’m going to give it a try using an FS installation test on the same pc where I have AFLT, to check if the problem appears or not.
 
You must log in or register to reply here.
Back
Top