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

Multiple Runways

B

Bluestar

Messages
142
Country
us-texas
I am working on an airport with three runways with the same numerical designation, but are distinguished by L, C, or R. AFLT is only showing the numerical designation for the runways in the menu header. As an example I will try to modify the approach lights on RWY33L (red), but no changes show up. I reopen the menu and it has not changed. After further investigation I discovered that the change I was trying to make for one runway had been applied to one of the other runways with the same number. Another example is on RWY33C I have MALSR lights, I try to add MALSR lights to RWY33R,. The e RWY33R lights appear, but they no longer show in RWY33C.

I am using the update .10 for AFLT
 
I was a little surprised by your post because I knew it recognized Left and Right. Unfortunately, Center goes undetected.

Update tomorrow.
 
I just tried (a) and still no joy. For example if I have installed MALSF on RWY15R and go to RWY15C and add ALSF!, the approach lights on RWY15R disappear. If I go back to RWY15R and click Edit, the menu shows ALSF1, put there are no approach lights displayed for RWY15R. The header menu still reads the same for both runways, "Approach Lighting - Runway 15/33."

If you need me to send a file just let me know which one.
 
Strange. Ive just done the same thing at KDFW with no problems.

Please send me your .ad4 file.
 
Oops, I w can't now - and maybe never did - duplicate the issue. In all my tests now, both on the AFLT editor screen and in Flightsim, all entered lights appear and none disappeared.

Are you sure you actually installed and used 4.3.10(a). It should say so in the title bar of the main panel.

The header menu still reads the same for both runways, "Approach Lighting - Runway 15/33."
Click to expand...
Not sure what you mean by "header menu". Using 4.3.10(a), all references (i.e., placements.xml and tooltips) to all 3 parallel runways are suffixed with "L", "R" or "C". Using 4.3.10, i.e., the general release, the "C" suffix would have been missing, but the other two should have been there.

It's unusual to overlay runways as you have done, i.e., overlaying 16/34 with 15R/33L. But, I don't think that has anything to do with the problem.

So, starting with a "clean" .bgl generated using the .ad4 file you sent, please give me precise instructions for duplicating the issue.
 
I get End: Primary (15C) Secondary (33C) at the top of the Approach Lights dialog box - seems to work OK here.
 
gadgets said:
Oops, I w can't now - and maybe never did - duplicate the issue. In all my tests now, both on the AFLT editor screen and in Flightsim, all entered lights appear and none disappeared.

Are you sure you actually installed and used 4.3.10(a). It should say so in the title bar of the main panel.

Not sure what you mean by "header menu". Using 4.3.10(a), all references (i.e., placements.xml and tooltips) to all 3 parallel runways are suffixed with "L", "R" or "C". Using 4.3.10, i.e., the general release, the "C" suffix would have been missing, but the other two should have been there.

It's unusual to overlay runways as you have done, i.e., overlaying 16/34 with 15R/33L. But, I don't think that has anything to do with the problem.

So, starting with a "clean" .bgl generated using the .ad4 file you sent, please give me precise instructions for duplicating the issue.
Click to expand...

Don,

I am showing 4.3.10(a) in the main panel.

Is it possible that I have a corrupted AFLT program file?

If so how would I delete everything and still be able to save my work?
 
Did you make the .bgl you are using as the Airport Refrence file yourself or did it come from some other source. If the latter, then try making your own. You may have a corrupt file, but I'd guess its the .bgl - especially since both Tom and I can work successfully with a .bgl produced by ADE from the .ad4 file you sent.
 
gadgets said:
Did you make the .bgl you are using as the Airport Refrence file yourself or did it come from some other source. If the latter, then try making your own. You may have a corrupt file, but I'd guess its the .bgl - especially since both Tom and I can work successfully with a .bgl produced by ADE from the .ad4 file you sent.
Click to expand...

I started with the basic FSX file for KSPS and have slowly added to it using ADE and then ADEX with P3dv4.5. The only thing that I have added to it that are not generic to the scenery are the airplane mdls. These mdls were made from ai models or from aircraft in P3d.

I will start over with a new KSPS and see what happens.
 
I went back and created a test airport. The runways showed as they should with the L, C, R.

I'm guessing that I will not be able to salvage my current AFLT. What file/files do I need to erase so I can get a clean start?

Sorry for the problems guys. Your help is greatly appreciated. :)
 
Well, you did discover that AFLT didn't process the names of center runways properly!

Why do you think you have to salvage anything. Just replace the old airport reference .bgl with a good one (there's a function under the Files menu for doing that) and all should be well.
 
You must log in or register to reply here.
Back
Top