Cameron

Hi, there, I have just recently received a message from the developer. At this time our focus is getting things ironed out for our customers. I'm not sure we can really work something out for this given the description the author provided to us in terms of how he gathers information. We'll look into this in time!

Hi, Bill, That's correct. Linux tends to run X-Plane the best of all platforms provided you get a good graphics driver set. The downside to Linux is that there are also a lot of plug-ins not made compatible with it for X-Plane. Coincidentally, the CRJ appears to be the most bug free and "smooth sailing" on Linux at this time. That may just be because Philipp is a heavy Linux user, and as the primary programmer of the CRJ now that would make sense. Thanks, Bill! Hope to see you in the CRJ skies soon!

What are you getting at, Kaphias? Are you trying to say the hardware tester does not accurately do its job? Last I checked it reported to people whether their drivers and hardware would show the displays of the CRJ just fine...just curious.

Hi, there, This indicates you have the earlier 1.1 installer. Please go re-download the 1.1 update and install again. It should fix this issue!

Thanks for acknowledging our generally good reputation, Simon. A matter of living and learning to be sure, and I agree. Fact of the matter here is none of us saw these issues coming since everything was so smooth on our 7+ test machines. We'll do our best to learn from this! Thanks! Cheers, Cam

Hi, All, First off, thanks to many of you here for your patience. We understand that for those of your experiencing problems with the latest update, this is a very frustrating time. Please know that we did not release the 1.1 update or product knowing these bugs were around going in. The reality of the matter here is we tested this product more than any other X-Aviation release has been tested before, and problems that never cropped up in our testings are being found in the customer base. Our test routines included multiple people, lots of computers, and varying flavors of operating systems, versions of OS's, as well as different plugins installed to try and ensure we had ironed things out ahead of release. Unfortunately (and fortunately), we're in somewhat of a "first" position. We are the first to accomplish an aircraft release of this magnitude. The systems are extensive, and the product has been something people have been after for a long while now. That's the fortunate side. On the unfortunate side, because we are the first of this category in a release, we are also the "guinea pig" to stability of other products with one as complex as this. We are exploiting code habits on other plug-ins (some still supported, some not) that are not so "good," while we're also finding some bugs in our own software or trying to create work arounds for other products' compatibility. We are actively contacting authors of said plugins to either help or figure out workarounds, providing them copies of the CRJ in an effort to make YOUR life a little easier. We want every customer here to enjoy this product, and if anyone of you here truly knew our current work schedule on this product alone since even before release day I think you'd safely agree that we mean what we say when we say we care very much about resolving these issues and getting any kind of patches we can out the door. We realize that some of you feel as though you're being treated as a tester. Please don't misconstrue this! If we ask you to test something, it's because we want to help you and understand the issue you have. We want this product to work for you so you may get to enjoy it just like we have. It also means that if we're asking you to undertake a task like refreshing your libraries, redistributables, or anything along that line that we are unable to reproduce your error but are very committed to trying to understand what is going on on your end so we may help! I know Javier has also mentioned installing Linux (this is part way a joke) to a rare few of you. This is not a must, it is not something we are forcing you into, and it does not mean we are ignoring your issue with your current OS. Javier's main point here is that we want you to be able to enjoy the product, and some of you who are overly frustrated, do not want to test, etc. may find it more appealing to install a free operating system that is relatively easy to install and is known to provide more FPS with little hassle once you get it going. If you're also willing to wait till we sort out/investigate your issue, then that's just as well! One thing to bear in mind here is that the customer base for the CRJ is large. The majority of people who seek to post in the forums are those with issues, while the happy one's usually keep to themselves. We have done some internal customer polls at X-Aviation with a group of pre-selected people, and so far the stats ring out as follows: 83% of users report no problems 17% report an issue 98% of the reported 17% issues are Mac users. The Mac users who are having issues are getting a fix very shortly. We have worked tirelessly to figure out what's going on here, as again, Javier, Philipp, and myself cannot duplicate these errors on a WIDE array of Mac OS systems. There are also MANY Mac users just like us who do NOT have problems running the CRJ at all, and because of this it has made it even more difficult to solve. This simply goes back to the above statement about how through our many tests prior to release, none to little of what is reported here could ever be re-produced! Thanks to the help of the Mac users who have reported problems and provided crash logs since we could not re-create the scenarios ourselves, we believe we have found the problem for Mac and are promptly working on the fix. Should you wish to read about this you may do so here: http://forums.x-pilot.com/index.php?topic=2373.msg23061#msg23061 In short, the Mac issue is a bag of mixed nuts. It is and is not a CRJ issue. It is a CRJ issue because we employed what we thought would be a better, more realistic font set for the CRJ. This works on a lot of systems, however, on a lot of others it does not and that actually comes down to an issue with Apple, Inc. themselves. We will be going back to what we know works for everyone and hopefully close the chapter of CTD reports very, very soon. Javier, Philipp, and myself all greatly appreciate your business, your support in offering crash and standard log files, and we are committed to making the CRJ experience a good one. Sometimes it can seem like a never ending episode of walking into walls when we get replies like this (click "this"), but we remain strong with the will to push on and continue to break X-Plane's boundaries...for you! Thanks to everyone for your time, patience, understanding, and business! All the best, Cameron, Javier, and Philipp

Was that necessary, Tom?

Hi, James, Without doing a complete re-do of the UV map, this is likely not possible and will likely not happen (at least in the immediate future). I like the idea, but there are too many other fish to fry at the moment! Thans for sticking this through! We appreciate our customers very much!

Thanks for those encouraging reports, guys! As it appears we're on to a fix now, this topic is closed. Those interested in reading on the upcoming fix, please read here: http://forums.x-pilot.com/index.php?topic=2373.msg23061#msg23061

Thank you from all of us!

Thanks, guys! We really appreciate the compliments in a wave of frustration at the same time. Enjoy!

Topic closed. This has been resolved and is NOT a CRJ issue. Cheesecake on the way, Javier.

Caneman, If it didn't fix the problem, you'll need to wait for the hotfix. Rest assured, we are all working feverishly to resolve this, and finally know where to go to likely resolve this. Thanks for your patience through all of the frustration!

Thank YOU!

No offense, Tom, but you do come across relatively hard headed at times, and rather demanding. We all want this to work for everyone. We'll get there. Sorry if it's not working for you at the moment. All the best, Cameron

Tom, They ARE important to the masses because this is how the CRJ ships. If you want to get crafty and remove the plugins, then okay...as long as its after activation. However, this will cause issues down the line when you need to re-activate. I'm still unclear on the XSB issue. In the poll I have done in a short list of users, and one additional user on this forum, all have reported that the CRJ (1.1), Gizmo, and Shrink Wrap all work perfectly well with XSB. I can't vouch for you, and I know your test was otherwise. That said, I do NOT recommend that people start removing plugins associated to the CRJ unless you know what you're doing, and because of that I will not recommend this to the general population at all. I know you are a heavy SASL user, so this only helps to make matters "worse" for you.

Gizmo, Shrinkwrap and Vascore should remain.

I would challenge that statement. You're a pretty smart cookie, Simon.

Simon, The instructions are to uninstall and then reinstall in succession to figure out the exact culprit. You've quite clearly misunderstood this.

Probably a clash between Gizmo and XSquawkbox and sound. ... Shrink-Wrap is a very basic plugin and shouldn't clash with anything. Meanwhile, the same plugin combo works for others: http://forums.x-pilot.com/index.php?topic=2403.msg22993#msg22993 *sigh* Someday....haha!

May come down to Windows update, or a mix of installed apps conflicting. Closed until Philipp can come around.

It's not a CRJ problem, Perry.

Elbert, No, the uninstallers are unique to each machine. You'll need to go through and make sure the following are removed manually and re-install on your machine: 1. CRJ-200 from the Aircraft/X-Aviation folder 2. Shrinkwrap, Gizmo, and Vascore from X-Plane/Resources/plugins folder 3. JRollonPlanes folder and all of its contents from the main X-Plane directory 4. In your user home directory of OS X: Library/Frameworks/: You should remove libcurl and the two QT folders in there. Once all of the above has been deleted, re-run the 1.1 installer.

Hi, Vance, Thanks for this post! Glad to hear you are having successful sessions and enjoying version 1.1! We'll look into that back to back load. Thanks again!

Japo32 is username. Javier is real name.