Leaderboard

Pitts S-2S

All of this is negated if the core of the aircraft simply does NOT fly accurately to a degree that makes it literally non-flyable. While some things may be "completed" they are all dependent upon one another systems wise...a domino effect. These "minor" updates would have been released long ago if such were not the case and has been seen on the DC-3, CRJ, etc. The MU-2 was not just an update to code. It was an entire re-write (clean slate), and dare I say Tom tends to code aircraft in a way most other developers do not. The systems depth BEHIND the scenes of which people do not visually see is astounding. I think you'll see this type of work reflected in the likes of even the IXEG 737...they are using the same approach. The update process works fine at X-Aviation. We get an update from a developer, we ship it out...same day. The rest of what you are questioning here is answered above. All code dependent on other code, and an entire plug-in re-write from the ground up. Crazy as it may sound, the MU-2 code is insanely complex. That's you, not them. Tom and I have discussed this in the past...so much so that we've sternly considered pulling the product down entirely. However, contrary to your view, we get an astounding amount of positive comments for this product from current day purchasers. I believe those who remain that purchase it know exactly what they are getting into and want the aircraft for what it is. To add to that, the screenshots and videos culminating from three years of use don't lie...people may draw their own assessment. Perhaps the only way for you to understand would be for you to be in the development cycle as someone on the team. Instead, you aren't, and if you can't understand it from what has already been stated here over the enormous amounts of posts, then I don't think there's much else to say! In short, we respect the fact that you have the views you do, but there has been good reason for the approach taken throughout all of this. Yes, we sympathize with the frustration (especially Tom, as seen in his various candid posts here). The situation is what it is. Tom has been polite enough to outline where he is in his "developer mind" for the next while, and things are not anticipated to change for the time being. We'll get there, but it won't be today. It'll be when it's ready.

A bit of news on the Twin Otter. Before you ask, this is not my project. I have been asked to do gauge animations and gauge programming only and the occasional post. I have absolutely nothing else to do with this project. There is no release date as yet.