P3dv4. Using fsaerodata updated airports, both the global and the N. America ones. I also have Flightbeam's KMSP scenery.

It's acting like there are duplicate airport files for KMSP, because ATIS is returning twice the number of runways that actually exist at KMSP, and the extra runways are a degree off of the correct ones (i.e, I have 30L and 30R, and 29L and 29R).

I ran Scruffy Duck's airport finder, and it found the fsaerodata files for KMSP but did not see the default files for it, or the Flightbeam files.

It's odd because I have most of Flightbeam's other airports, and none of them exhibit these problems. Everything was installed on the same day after I had to reinstall the entire sim following a Windows self-destruction.

I'm not good at all with scenery files, so what should my next steps be for getting rid of these non-existant runways?

 

Thanks all.

 

First place I would start would be to open your Flightbeam Manager. Then click on the Troubleshooting tab and have it run a scan. It will tell you if it finds any conflicting scenery files and will allow you to turn off their .BGL's from within the application. 

KMSP is (also) in p3d\scenery\namc so PWJT8D is probably correct with the requirement for flightbeam manager to disable the original .bgl(s).

I double checked in case I forgot to do that this last install, but the FTX_Vector_apt\scenery\ABP_KMSP.bgl file is deactivated. That's the only conflicting KMSP file the Flightbeam manager found, too.

I found Minneap.bgl in \NAMC\, but I thought that included the whole area. Should I rename that to .bgl.off like the Flightbeam manager did for the Vector file?

 

Edited February 13, 20197 yr by eslader

What weather engine are you using? Maybe you need to update the Nav data for that as well?

Just athought. Hope it helps.

Jesse

Active Sky, but I just did a test without running AS at all and still saw that rwys 30L, 30R, 31L, 31R, and 32L, and 32R were in use. KMSP's actual runways in question are only 30L and R. 

BTW, just to be totally clear since my original post probably wasn't, ATC is the *only* thing effected. Visually the runways are correct. There are no duplicate runways or taxiway signs like you often see when 2 scenery files are conflicting.

 

 

You did not mention it, are you using any AI Traffic programs?

1 hour ago, eslader said:

I found Minneap.bgl in \NAMC\, but I thought that included the whole area. Should I rename that to .bgl.off like the Flightbeam manager did for the Vector file?

 

Don’t ever disable default files such as the one you listed. You’re correct that the Minneap.bgl include other scenery items beside the airpoart.

What happens if you disable the fsaerodata file that Scruff Duck round?

Hmm. Disabling that seems to have made it worse, as now I have runways 34, 33, 32R, 32L, 31R, 31L, 30L, and 30R being called out by ATIS.

 

I'm quite confused now.

And @PWJT8D no, sorry I should have mentioned. Stock AI traffic, stock ATC.

 

 

Edited February 15, 20197 yr by eslader