Cameron

There will not be an update for X-Plane 9. X-Plane 10 is a very stable sim at this point, and we must go where the ROI is. In this instance, over 95% of our customers have already made this transition in X-Plane versions. The MU-2 will continue to work as is in X-Plane 9. If you have X-Plane 10 you will be able to run this update. Part of the reason for X-Plane 9 now being excluded has to deal with the fact that the MU-2 is again on an entire code re-write. Too many issues presented themselves, and the new version of code is proving that the only logical route at this point is to support one version of X-Plane. In this instance, that version is X-Plane 10. When the code has been completed and proven to work in X-Plane 10, then we will do a quick run down to see if it works in X-Plane 9 at all (we already anticipate it will not). If it does not, we do not anticipate fixing this. As it stands already, a number of changes have been made to the aircraft file, which is in X-Plane 10 format for features that were only available in X-Plane 10 to begin with.

Nice shots!

Glad to hear you got it going!

That's correct! I just tried it a second time...works like a charm!

As Philipp has stated, the item is two words, and is case sensitive just as you see it in the checklist. I have personally downloaded and tried this. It works like a charm (the password unarchiving, that is) Aside from the case sensitivity, be sure to double check your spelling as per the checklist for these two words!

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.

Yes, it still uses these. Removing them will cause problems for you down the line at an unexpected date, as these control license verification and are done at periodic intervals. Failure to have them present will ultimately "break" your CRJ at that time and you will likely forget why. It is advised you not remove these if you wish to have a fully working CRJ.

Hi, Nano, No beta testers needed, but thank you for your enthusiasm.

Hi, there, Philipp will be the one to answer this. He's currently out on a short leave for a conference and some personal family items. Segfault has been addressed here multiple times for Linux, so be sure to search for this in here as well in the meantime!

Indeed, Cessna729 is correct here. Please note that all of this is documented in the manuals and we highly encourage people flying this aircraft to read them in their entirety. It will make your experience that more enjoyable rather than frustrating when things don't go right!

This is not a CRJ feature. We don't document it because we don't code it...Laminar Research does. It applies to ALL planes in X-Plane. We have absolutely not one thing to do with view controls in X-Plane.

Since you've also contacted us via email and I'll need some more info from you, we'll continue there.

Remove file 'Uninstall CRJ-200' located in your X-Plane 10 folder and then re-install.

I'm really not clear on what you mean. Press 'Shift' and the '9' keys together and then use your mouse and right click held down while moving the mouse to move the angle/head of the camera.

The only time this would happen is if your doing max thrust without limitation in the FMC, which then causes engine issues. These warnings would be displayed in red on the displays. Activation has nothing to do with any part of the engines at all.

I'm sorry, I don't quite follow what you are saying. Can you please elaborate so we may better assist you?

Hi, Folks, Update 1.5.1 has been released to fix crashing issues when the CRJ is the first loaded aircraft by default within X-Plane. Instructions on how to update, as well as what else is included in this topic here from version 1.5.0's update yesterday:

I think it's quite clear Big T is not looking for hassles. If you're confused by this, re-read post #3. I guess it just strikes home a bit harder since you're a part of the org moderation team, and seemingly stuck in similar situations as you've suggested to Big T if you know such outcomes. Probably best we not further get into that here, though. You and I still have some unfinished business to soon settle from a certain blog website. I've got plans for a proper platform for that.

Welcome to X-Pilot, Big T! Quite sad that you even have to make such a recommendation, Joe. Quite the hassle, too.

We have absolutely no control over how your hardware is mapped. You'll need to take that one up with Laminar, or look into your advanced joystick button settings within X-Plane.

Modifications will void the support of the product. Please remember that this product will not be easy to edit something like this. A 3D program would be required, as Planemaker panels are not used here.

Did you mean to say "no" problem, or are you still having an issue of sorts?

As stated in the update notes here and in the email: NOTE: If you don't like the fixed iPad-resolution of the new remote CDU, you can find the old version in plugins/CRJAvionics/Resources/docroot_old/.

We'll get Philipp on this, as he's the Linux guy!

Great!