Missing PAPI

**KellyB** · September 17th, 2013, 13:41

I have an addon scenery for Bangor Intl. (KBGR) in which the PAPI doesn't show up.
If I look at the bgl in ADE150, it shows that one is specified.

If I use the stock airport files, the PAPI shows up.

The specifications are identical in both bgls.

Where do I go from here? Any pointers as to diagnosis and fixes will be greatly appreciated.

***Tom Clayton*** · September 17th, 2013, 14:16

If it's freeware, post a d/l link so the rest of us can take a look.

**aeromed202** · September 17th, 2013, 15:01

If it's a standard Afcad, lights can be fixed, but if the scenery runway is custom, Afcad lights will not show and must be added by the author.

**KellyB** · September 18th, 2013, 04:03

Originally Posted by Tom Clayton

If it's freeware, post a d/l link so the rest of us can take a look.

A generous offer. Here's the link:
http://www.flightsim.com/vbfs/fslib....rchid=15068326

The file name is kbgr_jy3.zip and it's done by John Young.

@Aeromed: I'm don't know how to tell the difference.

Thanks, both.

**aeromed202** · September 18th, 2013, 18:47

When I installed the scenery it indeed looked like the author created his own textures which override the Afcad, maybe it's just the grass covering the PAPI. The Afcad is the scenery bgl file that dictates the airport runways, taxiways, and other details around which buildings and other textures are added to create an entire airport. Typically the lights (PAPI, taxi, etc) created from the Afcad file show properly except when masked by some other texture. In this KBGR package, the author added his own PAPI4 on Rwy 15 but didn't on 33, probably just an oversight, according to AirNav there is a PAPI4 on both. The remedy is to contact the author and see what's what. Hope this answers your question.

**KellyB** · September 20th, 2013, 11:10

Originally Posted by aeromed202

When I installed the scenery it indeed looked like the author created his own textures which override the Afcad, maybe it's just the grass covering the PAPI. The Afcad is the scenery bgl file that dictates the airport runways, taxiways, and other details around which buildings and other textures are added to create an entire airport. Typically the lights (PAPI, taxi, etc) created from the Afcad file show properly except when masked by some other texture. In this KBGR package, the author added his own PAPI4 on Rwy 15 but didn't on 33, probably just an oversight, according to AirNav there is a PAPI4 on both. The remedy is to contact the author and see what's what. Hope this answers your question.

Thanks. I should try rwy 15. Not sure why I didn't think of that, other than senility.

I'll also see if I can contact the author. I gather from your comments that that is the only way to deal with it?

Thanks again.

**KellyB** · September 21st, 2013, 06:40

I got hold of John Young, the creator of the scenery, and he said he created a layer above the papi's, just as you suspected.
He used a program he called Airport for Windows (AFW), which he has dumped.
Anyone know where it might be found??

Google keeps telling me about the Mac wireless stuff.

Thanks.

**dhazelgrove** · September 21st, 2013, 07:51

Originally Posted by KellyB

I got hold of John Young, the creator of the scenery, and he said he created a layer above the papi's, just as you suspected.
He used a program he called Airport for Windows (AFW), which he has dumped.
Anyone know where it might be found??

Google keeps telling me about the Mac wireless stuff.

Thanks.

You can find it here: http://www.thefreeflightsite.com/Design.htm
Scroll down.

Dave