• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Missing PAPI

K

KellyB

Charter Member
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.
 
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.
 
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.
 
aeromed202 said:
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.
Click to expand...

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.
 
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 must log in or register to reply here.
Back
Top