Instrument approach update for 16C/34C

Carob · Post by **Carob** » Sat Apr 21, 2007 5:16 pm

So do I need to replace just the AFCAD file or both? I guess I'm confused there. If you correct the AFCAD do I need to replace both?

What exactly in the AFCAD file got removed? Is it something I did by mistake or did it just happen?

What information is contained in that AP915150.bgl file? And, is that file just for KSEA or does it control other things?

BEFA Pilot · Post by **BEFA Pilot** » Sat Apr 21, 2007 7:13 pm

Sorry, I should have explained it better. You can replace both if you wish, but as soon as you edit the AFCAD the approach data will go away. The GUI AFCAD editor doesn't seem to understand the approach data and also resets the deleteAllApproaches variable back to "FALSE" causing the approaches contained in AP915150.bgl to be used.

A longer term solution is to replace the AP915150.bgl which contains all the original Airport and Facilities data for the pacific northwest. This procedure will work fine as long as you don't have any addons that have modified the file making your original different from mine.

Hope this makes more sense,
Brian

Carob · Post by **Carob** » Sun Apr 22, 2007 1:38 pm

I don't really understand anything about creating AFCAD files just a little bit about chaning very minor things.

But, this makes a little bit of sense.

I'll give it a shot and see how it goes.

Thanks very much for your help!

Carob · Post by **Carob** » Sun Apr 22, 2007 3:51 pm

Well, everything seems to be okay except for aircraft getting stuck on the taxiway.

I have attached a picture with a circle around the area.

Can anything be done about this? I hope so.

Thanks!

Carob · Post by **Carob** » Wed Apr 25, 2007 10:40 am

No idea, huh?

BEFA Pilot · Post by **BEFA Pilot** » Wed Apr 25, 2007 5:08 pm

I have only seen this occasionally and was usually caused by landing traffic at juliet or mike cleared to terminals A, B or S. Is this a new problem and does it happen frequently? I didn't change any of the taxiways so I'm not sure why it would have just started happening.

Brian

Carob · Post by **Carob** » Wed Apr 25, 2007 5:14 pm

I didn't figure you did anything with them that's why I thought it was odd. But, it never happened before.

On two attempts I saw it twice.

???

Mike... · Post by **Mike...** » Fri May 04, 2007 5:13 am

I'm sure we all appreciate the effort, but BEFA Pilot, your approach to this is not as good as it could be. Approach data should not be tinkered with in an Afcad file. And the stock AP file should also be left intact. The solution is to create a new file, hardcoding runway and approach data changes, which must then be placed in the Scenery/Generic/scenery folder. That file together with a proper Afcad will do the trick. And editing the Afcad is still possible.

I just created such a file, not knowing someone else already took a shot at it. I'm going to attach it to this post, plus the Afcad I use (basically the default one, but modded. Aircraft cross active runways, etc...).

For those who want to try it, disable any existing Afcad (and any of the other files attached to this thread previously!), then put mine in Seattle's scenery folder. Put the other file in the Scenery/Generic/scenery folder. Start up FS and test it out. (Increase winds, reduce visibility, listen to ATIS, check the GPS receiver, etc... Don't forget to change time a little to refresh the sim after you've changed the weather.) Then give feedback.

It works for me, if a couple of people can confirm this, I'll upload a nice package to Avsim.

Edit: attachments removed, package can now be downloaded from Avsim.

Mike... · Post by **Mike...** » Fri May 04, 2007 5:16 am

specialist · Post by **specialist** » Sat May 05, 2007 1:09 pm

Thanks Mike, it's working fine for me.