mackintosh

Hear hear. Support for SLI and proper multicore would already be enough as far as I'm concerned. Those two should already boost performance far beyond that of FS9 and FSX. Right now most of my CPU cycles and GPU power wasted. I don't need improvements in graphics, I do crave improvements in performance. This thing in my sig can run Crysis at 60fps @ 1080p, damn it, I want the same performance in Flight! ;)

You can make the 2D panel work. Not sure about the VC though. I guess when a product's as bad, nay, terrible as the Wilco Airbus, no one bothers trying.And now they have the audacity to charge for what is essentially nothing more than a patch that, from the looks of things, is purely cosmetic. The nerve of these people. Sheesh.

Yep, ditto. It's a pity it only comes now, when there aren't that many of them flying around Europe any more, but I'll still find a use for them in my hangar. I only wish they hadn't announced it yet, Q3 2011 is so far away...

I have to admit to not having noticed exterior inaccuracies in the MD-11, I was mostly focusing on systems modeling, which to me is quite impressive (although I can't really pretend to have any in-depth knowledge of those either...). I suppose as a reviewer you're much more attuned to such discrepancies. Just out of curiosity (and apologies for the derail) - what are some of the most obvious errors?

PMDG's MD-11 is, as far as I'm concerned, the pinnacle of FS9 development with LSH's Maddog a close second (probably due to the inherent complexity of the MD-80). LDS767 is still an amazing piece of software engineering, but I feel both the MDs have surpassed it. The jury is still out on the iFly NG.

This is absolutely, 100% correct. The equation for determining the most appropriate USERVA value is USERVA = 4096 - 768 - amount of gfx ram. Setting USERVA too high will result in excessive paging, severely degrading performance, setting it too low will, obviously, defeat the purpose.

It's a decent package (and the only 737 classic package out there afaik). It had some teething problems years ago, but it's pretty flyable these days. The visual model is awful though and I have found it to be a framerate hog (admittedly it's been a while since I've used it...), so I've replaced it with the 50North 737s.I disagree with the opinion that it's not as well modeled as the iFly 737. I'd say they are comparable in features. Since the iFly models the NGs, it's obviously newer and has more bells and whistles, but the FT 737 is pretty rich in features for a 737 classic and for its age as a product.That's not to say it's without problems however. While most of my flights go fairly smoothly, it does have a tendency to overbank every now and then and is prone to falling out of the sky at higher sim rates than 2x and handling can be somewhat erratic at times.

I just noticed that they deleted my post (which was the first mentioning the suspension). Well, I guess I won't be going back to that forum again. Really poor form. Least they could do is to be mature about it. Lots of companies have cashflow and other issues, it's communication that makes the difference. Oh well.

Well, having bought it when it came out, I finally got a chance to do a test flight today. I have to say I haven't been this pleasantly surprised by a release in a while. This thing's done one of the most exquisite, picture perfect autolands I have ever seen. As we all know, programming an add-on to perform a perfect autoland is no easy feat and is often a testament to how well an FDE and panel work and in iFly's case, they have it down to a T.

[wrong thread, duh]

Guilty.

The stuttering isn't caused by texture size (at least not 100% of the time). It's mostly caused by missing alpha channels in DXT3 textures. If you add the missing alpha, most of the stutters should be gone. Can't speak for DFW, haven't bought it yet, but nearly all other FSDT sceneries have had this issue.Here's some more on the subject: http://www.alpha-india.net/forums/index.php?topic=8581.0

Well look at that, guess who called it? :( Seriously though, I do cling to a faint hope this will not simply be a rebadge of his "upgrade".

I've been around the block long enough to know that Wilco is not the dev. In fact I said "Wilco" precisely to avoid pointing out the fact that FT were the developers of this abomination to begin with. "Track record" in this case is a dangerous sword to wield :(