NZFF

All,

I just installed Ant's Brisbane Airport (available here: http://www.antsairplanes.com/scenery.html ) and it looks like I lost the instrument approaches for the airport in the database. My (and the AI's) only option when arriving in Brisbane is to do visual approaches. Has anyone been able to restore the instrument approach procedures for use with FS ATC?

Ive have downloaded but never tried it , got caught up other with stuff , I have not install the Orbx Brisbane but i'm getting tech glitch's across NZSI after installing freeware.. wonder if that maybe a cause ? seems be an ongoing thing if your running a historical PC .

SeanTK wrote:

QUOTE (SeanTK @ Dec 28 2013,2:38 PM) <{POST_SNAPBACK}>

All,
only option when arriving in Brisbane is to do visual approaches.

Hah! - Welcome to sunny Queensland
Not sure what I have for YBBN in my FSX...the OrbX FTX scenery was quite a disappointment, which is why I mostly fly in NZ VLC.
I will have a look, and report back.

Sean, I just installed Ant's Brisbane, after making two IFR planned flights from Toowoomba to Brisbane, one in default FSX and the other with FTX active. Both flights did what I expected and there was plenty other IFR traffic to be heard.
After installing the airport and starting some flights there, I found:
If I request taxi VFR, all the inbound traffic seems to also be VFR.
If I lodge an IFR flight plan, I have to go through Brisbane Clearance before I can contact Ground for taxi clearance.
I can then pull off the taxiway at the hold point, tune the Tower, and listen to planes requesting departure IFR.

I will have to pick a busier time, to see which AI is affected - at the moment I have both the default and the FTX AI active.
Interesting...
UPDATE
I just repeated the two baseline flights I made this morning, YTWB>YBBN., using the same flightplan.
Whether I load the flightplan before anything else, or wait until I'm up and stabilised, Bribane Approach still tells me to expect vectors for a visual approach to Rwy 10.

I opened Ant's airport in ADEX, but I couldn't see anything which could be causing this.
The only difference from this morning to now, is the installation of Ant's Brisbane.

UPDATE2:
I did find this in a thread on the Avsim forum, after Googling FSX all AI visual only

"There are two types of 'code'. The first is the code for the beacon itself, and this transmits the signal you pick up. This is what you can edit in AFCAD, or AFX.

The second type of code is the 'approach' code. This is a sequence of waypoints to any type of approach (ILS, GPS, VOR, etc). Often, developers only write the first code, but not the second code. This is a pain for users, because it means AI and users can't get vectors from ATC for the approach.

Sometimes runway designations change (ie, 34L becomes 34C, or 34L becomes 35L). The ILS beacon is easy to update, but if you don't also update the second set of code (the 'approach' code), then there will be no ATC selectable approach for the resignated runway.

Finally, approach code allows you to do cool things, like curved approaches at Kai Tak. I just wrote an approach for a curved approach to Boris Forero's SEQU. It's neat to watch the AI take the turn on late final.

It is very easy to write this approach code using the GUI in ScruffyDuck's ADE.

Cheers,

Bryn. "

Thanks very much for the investigation! It looks like I'll be figuring out how to write approach code!

UPDATE: That worked! I imported approaches from another third party, recently dated AFCAD file, and now everything seems to work perfectly. Thanks again!

AI ifr or vfr is encoded into the ai flight plan, has nothing to do with airport.

mjrhealth wrote:

QUOTE (mjrhealth @ Dec 29 2013,4:18 PM) <{POST_SNAPBACK}>

AI ifr or vfr is encoded into the ai flight plan, has nothing to do with airport.

Well, there was no way for me to even access anything but visual approaches from the database regardless because the approaches associated with the airport disappeared. So, this problem only involved the airport files, not the AI flightplans.