ilarikousa

Negative. It's made by a guy called Chris Serio. JD's role has been a consulting one at most.

You can always make it optional.. a "realism settings" box with options to choose from... "Realistic altitude units" could be one.. problem solved.

I've been using X-Plane quite alot recently, but am waiting patiently for v5. Something that the team should address is your descent profile. It would be lovely if you didn't get the same 11k/12k crossing restrictions every time. Since you asked for suggestions, mine is to make the descent profile a little less predictable, for example based on the amount of AI. And what about using FS's (albeit static) airspace data to set sector lateral and vertical boundaries, like this http://www.x-plane.com/blog/2011/02/the-world-is-under-control/

That's how it works...

I fully agree -- and it'll only get better with 5 :)

I find it bad that ORBX has been making love with Microsoft...they're no longer being objective...

Glad to know it might be possible -- another realism booster!

Brussels has them too: "Beeline six four bravo, taxi via outer six, bravo one, holding point two five right" :(

Hi,As you are well aware, some airports use certain nonstandard taxiway designators (reference for example the LEPA ground chart). The most common ones are Link, North, East, South, West. Could you include at least those in the scripts, as many afcads have Link taxiways coded as LINK so we could hear it the usual way and not Lima, India, November, Kilo or the like? Subs?

Well, there are some bugs but in my mind this is the best solution till the LDS757 comes out. The QW systems modeling is too simple for me. Just make a copy of the QW757 .air files and copy them to the CS folder(s) under the names specified in the CS aircraft.cfg.

I combined QW flight model with CS systems, great combo...

Is there any particular reason for why you've chosen to limit RC to 1 comm radio only?

I have forgotten something important..the "Twin Cessna" aircraft type callsign...could you add that if not already there?

I'm going to wait for the FSL one -- Wilco's just looking to cash in on the early birds :)

You mentioned once that RC5 has the "caution wake turbulence" advisory. Would it be possible to make v5 apply the proper time-based separation on takeoff (e.g. have you wait the correct amount of minutes) by ticking an "Apply wake separation on departure" type checkbox in the interface to cater for programs that simulate wake turbulence? You would just need to query user aircraft type vs. departing AI type and decide on the delay per FAA/ICAO regs as approppriate...