But other countries are different. In the UK for example, the London CTR, which surrounds Heathrow, is Class A airspace from the surface to 2500 ft. Stacked above that is the London TMA, which is also Class A and steps up from 2500 ft to FL195. That's why it should be modelled. EDIT: To the best of my recollection, the London airspace was modelled in FS9.
Hence why I said the USA only.

I wasnt referencing the entire world, just that the USA is going to the ICAO system more closely than it does now.
UPDATE: I totaly missed the point of your post, I apologize. You were referiing to Class A being displayed/modeled because of how it is used elsewhere in the world. Fully understand how you meant it now, and I agree it should have been modeled outside the USA in FS. FS can only get so real. At some point you actually have to get into a real airplane.
I havent checked XPlane to see how they model airspace, but may be picking up X10 shortly, if I dont go the P3D route instead.
That was my point. Surely it's a good thing to standardise these definitions internationally - aviation is international. The ICAO Class A definition is
Type of flight: IFR only
Separation provided; All aircraft
Service provided; Air traffic control services
Speed limitation: Not applicable
Radio communication requirement: Continuous two-way
Subject to an ATC clearance: Yes
That's hardly "...integrated multiple aspects into one massive confusion."
The aviation ICAO system is a conglomeration of multiple coutries aviation systems to uniform it. It can get confusing when you get really deep into it beyond what the wiki shows.

What you show above is only airspace types, I was referencing ICAO as a whole when I stated that. Im not arguing any points, just clarifying.
Back to the original topic.
Max will easily MAKE and export an object this large.
ModelconverterX will load a cylinder, for example, of 50,000m radius .. it just won't apparently display it.
Not sure whether FSX will display such an object
Is there a scale map of the KSFO airspace with altitudes etc annotated. It would be pretty easy to trace and extrude parts of it into a giant colour coded model.
The issue, as already discussed, is whether it will display as one object or in bits.
The theoretical range to display objects in FSX was 60nm (not sure where I got this information from!)
I tested a 30mile radius object in FS9, did not test in FSX at the time to see the differences. I think I stated that MCX wont display an object past a specific size, but it will convert. Arno could probably state the range MCX would allow. I dont know if there is a way to modify range the object displays as in FS9 my test radius was 30 or 40 nm from center and it vanished (at work so I cant reconfirm if it does or does not vanish at 30 or 40).
What's the purpose of your post other than arguing against my personal opinion?
Lol Thats a good response. But lets leave it at that. We dont want the mods closing this thread over civil unrest, its still new afterall. We can bicker when it reaches 90 days
