Customer expectations. -sighs- The CRJ does some very interesting things with a whole suite of very interesting software. vasFMC, etc. The Saab is based around an entirely different suite of software, being Gizmo. vasFMC's aim in life is to be, well, an FMC. It's good to see it go modular and embeddable at last. Gizmo's aim in life is to unlock X-Plane from the hands of elitist programmers and arcane, horrible, taxing, boring, horendously over-burdended C. It aims to let you express your systems ideas as quickly as possible. We don't write web pages and DHTML in C/C++ or even Java applets, we use JavaScript and DOM, or Flash. For the record, there are parts of Gizmo that are multi-threaded, scripters in general don't know or care which parts. I would like to eventually add a facility where Gizmo scripters can; A: Draw using a nice friendly graphics API to a texture in RAM that in a way that can be threaded. This would be similar to what the CRJ does. (I think... not sure on the gory tech details tbh.) B: Provided dedicated "worker thread" spawning api's with as many useful tools exposed as possible so that scripters can be artistic and push Gizmo and its facilities in ways I've not anticipated. The reality is that it's relatively slow progress. I've got a new job and I'm trying to rack up as many hours as I can to prove worthy to the management -and- save my a$$ off. So while the CRJ has just blown the lid off the the benchmarks for X-Plane, please do not simply assume that every product is going to hit that mark in the same ways. I'm doing what I can, when I can, to make Gizmo as potent as possible in every way. It's pretty much the only I.T. work I do anymore. I'm working a boring as hell "freight" job to pay for it too. On the upside, I don't need a Gym membership. It's 00:21 here, the end of my day, apologies if I'm worn a little thin here and there. Opinions are my own. Bla bla bla. Can't speak for the performance of the Saab, haven't flown it.