Wrong. We don't have to adapt to them. We are willing to WORK with the developers of these add-ons to improve compatibility. The CRJ is a very sophisticated plane, and cannot be compared to anything else available in the means of how its systems, displays, or data is programmed. This is proving to exploit bugs in our programming sometimes, but also exploiting bugs in OTHER plug-ins programming as well. It is just as unfair for you to state that this is all our fault. We are MORE than happy to work with developers and have been actively contacting them to work around these issues. That's not a plug-in issue. That's somehow an incomplete object load. When you initially load the CRJ do you see the WHOLE plane, or does it always look like you have shown above? This appears to be something specific on your computer, as this has NOT been reported on any others, and is a classic case of missing object files or too high or settings for your setup. We are working as hard as possible to resolve these issues. You are ONLY seeing the vocal people here who do have issues. There are MANY, MANY people with NO issues too! Unfortunately, life is not any easier because we cannot duplicate any of these crashes like some others have, and we have tested this on over 7 machines now. To give you a fair idea, the amount of people having issues is well under 20% of total sales. This does not mean that we aren't going to work any harder, but it means that we are NOT purposefully releasing software that appears to be buggy. We are committed to solving any issues for everyone, and will not stop working until we do. The amount of nights with no sleep has gone far beyond what you can even imagine at this point. This has nothing to do with X-Aviation or the Take Command product line. This is an evolutionary product with growing pains that are unforeseen, and had we been able to duplicate any of these issues on our test machines we would have NEVER released the aircraft in this state. Believe me, this is no more fun for us than it is for you!