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

FS2004 Can't Get Started

Hi,

Using 4.1.16.

1. The VASIs are brighter indeed, that's good. But the main problem with BGL lights is they all fade out just as I need them for the approach. The VASI BGL lights become unusable at 3.6 NM (no matter how many you place there), and I need them to be readable at 5.3 NM, where I will be starting my descent to the runway as I approach at 2000 ft AGL (the Bridge Visual approach at KSFO is at 1900 ft, for example).

A default ADE VASI is readable out to 6.7 NM, which is plenty of room to acquire the VASI lights and then follow it down. So I'll need to continue to include a default VASI in my ADE file.

2. The lights do not appear to pulse anymore. Good!

3. I can confirm that no strobes are added to an airport that has no strobes in the ADE file. Good.

We are making nice progress, thanks.

Did you see my post above about all AFLT BGL files being deleted when AFLT compiles to that folder? I don't think it will be a problem for most people (who compile each airport to a separate folder) but if people are compiling all light files to (for example) the Addon Scenery/scenery folder this might be a problem.
 
Last edited:
Just a heads up. Applying Use Stock Lights does not trigger a Save warning. No big deal, they are easy to restore.
 
but if people are compiling all light files to (for example) the Addon Scenery/scenery folder this might be a problem.
Click to expand...
Shouldn't be. Each file copied has the project ID in its name.

Applying Use Stock Lights does not trigger a Save warning
Click to expand...
Don't think it ever did. Easy to add.

We are making nice progress,
Click to expand...
Hopefully enough that I can focus on undesignated taxiways over the next couple of days.

Don
 
Don, please look at my pictures. Even though the two projects had different names, AFLT deleted the original project. The names were not the same and yet it was deleted.

The issue is still there that the Create/Delete/Create Approach sequence will not display the last approach on the map. I just Edit the approach instead which is a simpler technique anyway, so perhaps this isn't important.
 
Even though the two projects had different names, AFLT deleted the original project
Click to expand...
Yes, I see where the problem is. Its a very old piece of code and does not, as I thought it did, look for the project ID in the file name. Next release.

the Create/Delete/Create Approach sequence will not display the last approach on the map.
Click to expand...
I'll check that out tomorrow

Thanks,
Don
 
Don, the compilation of P3D v3 & v4 files now creates everything at the correct place. Perfect!

Many thanks
Martin
 
The issue is still there that the Create/Delete/Create Approach sequence will not display the last approach on the map.
Click to expand...
Tom, I have fixed the delete .bgl files issue (AFLT now checks for ProjectID), but I am unable to reproduce the "missing approach issue" using the sequence of instructions you provided earlier.

Don
 
Oh well, it happens to me every time but I guess it's just my computer. As I said, I just avoid that sequence - it's not really a common procedure, I just did it to be exhaustive.

Glad to hear the delete file issue is fixed.
 
You must log in or register to reply here.
Back
Top