NZFF

This update is designed to replace the default FS9 and FSX upper airspace BGL file with a more accurately modelled version of New Zealand's upper airspace.

This project was started after years of frustration at the lack of realism in the default upper airspace present in Flight Simulator 2004. Once established in a cruise climb, IFR traffic flying within the New Zealand FIR is invariably directed to a fictional "New Zealand Center"Â￾ sector and remain with them until descent. This sector does not exist in real life, and the airspace boundaries are vastly different from those used in reality also. This problem is still evident in FSX.

This update replaces the generic airspace boundaries with boundaries modelling those used in New Zealand a lot more closely. Although I have tested it with FS9, I have not tested it with FSX at all. All I have done as far as FSX is concerned is compare the generic BGL file with that of FS9. They appear very similar, so I have assumed that this update will work. Also, since I built it using the FSX SDK one would assume it is ok. Nonetheless, I'd appreciate hearing from FSX users as to whether it works or not!

The update can be downloaded from my website:

Download Here

If the download link redirects you to another page, it's most likely my webhosting provider not allowing links from external referrers. If it is a problem, just copy and paste the URL into your address bar or drag the link up to the address bar.

Cheers
Richard

Im still alittle unsure of exactly what this file will do ,and how i would use it within my sim,
is this if you use atc within the sim or does it change airspace boundaries lines within the sim like i was thinking it mite ?? also you say upper does this mean the lower is just default and mainly for heavys in mind ?
sorry about being so outta touch with this sorta stuff ..

Like Creator2003, I too am a tad confused about this addon.

I thought that Digital Fantasy's replacement AT90CEN0.bgl (v2.0), available as a free download from RBE, corrected both NZ and Pacific Airspace.

Enquiring minds and all that ...

ZK-LGD wrote:

QUOTE (ZK-LGD @ Dec 13 2007, 11:22 AM) <{POST_SNAPBACK}>

Like Creator2003, I too am a tad confused about this addon.

I thought that Digital Fantasy's replacement AT90CEN0.bgl (v2.0), available as a free download from RBE, corrected both NZ and Pacific Airspace.

Enquiring minds and all that ...

Hey guys

The update is purely for upper airspace (airspace above 9500ft). The majority of the changes in the RBE AT90OCEN0.BGL are all about waypoints and routes. It removes the defunct waypoints, adds the new ones, and defines the routes between them where they exist. It does also include airspace boundaries in the sense that they are shown by FS in both map view and in GPS view, but it doesn't actually change how they behave in terms of radio frequencies and handoffs etc.

The inherent problem lower airspace faces in FS is that you are at the mercy of whoever designed the airports near you, since COM frequencies are saved as part of the AFCADs and don't adhere to boundaries of any sort. You could add in correct frequencies to an additional file, but they would be overwritten by an airport with incorrect frequencies (certainly the case with default NZ scenery). It may well be that the RBE update tries to correct lower frequencies, but is overridden by this problem. I run it myself and without my update installed, the frequencies remain as they always have been on FS. I do, however, get the new waypoints, routes and airspace boundaries.

My update won't change the lower airspace at all. You'll still have the same frequencies and boundaries as you've always had. It doesn't draw boundaries for upper airspace either. First, because the generic upper airspace file doesn't allow this to happen and secondly, because upper airspace in real life doesn't always conform to lines on a map. For instance, the sector which makes up 123.7, 129.4 and 129.3 is actually shown on the map as one big sector with different frequencies in boxes roughly in the locations where the different frequencies apply. There are no lines that 'border' the sectors as such. In some cases, there are lines along true boundaries but not in all cases. So my sector leaves the 'lines' part up to the RBE update (if you have it installed) and instead just handles the upper frequencies.

If you think you can't see any difference, this will probably be why. Get yourself up to a higher altitude and you should notice that the airspace boundaries and handoff points mimic those used in real life. Auckland on 123.9, Christchurch on 126.0, 119.5, 123.7, 129.4 and 129.3, Ohakea on 126.2 and 119.2, and Wellington on 122.3 are all in there. These are all the frequencies that all high flights will have contact with enroute.

Does this make sense?

Richard