Cameron

The actual programming of this add-on was never meant to have A/T, and if it worked before and doesn't now by a simple hardware configuration, it was a fluke. I don't believe we'll be investing the time at the moment to implement a feature that is rarely seen in almost ANY of today's CRJ-200's flying the skies. Our primary focus is to get what is meant to work working for everyone.

Is this serious? You are telling the people who made the CRJ add-on that you are flying and are telling you that it never had a/t that it had...a/t? It didn't. Never has. Never will.

This is nothing new. It's been going on for a long time now. SSL is not well documented (at all), and Gizmo is continually growing. At this time it's a toss up, but we've looked into it at times. My guts tells me Gizmo will end up being the "product" of choice for developers soon, as it's more optimized and better tuned for LUA scripting. No. There are two new map modes. The one you are in is similar to terrain awareness. As you get higher, the terrain is no longer an issue and you are in the "clear." Clear in this case = black. Yes, you may now edit the aircraft to your hearts desire. This is one of the benefits to the newer system/Gizmo, and something we listened to our customers on.

Jode, This does not look to be a Corvalis or Gizmo bug based on your logs. Those files are cleaning out okay. It appears one of your other plugins in your non-clean install is causing this. You may want to add those plug-ins into your clean install one by one to see which one is the culprit. Sometimes deleting your preferences can solve this as well!

Hello, all, This will serve as a formal forum announcement that we have released the version 1.3 update for the Cessna Corvalis TT. All customers who have purchased the Corvalis up till now have been sent an e-mail by X-Aviation with complete installation instructions on how to update your product. We have made this a very simple process! For those that purchase the Corvalis from today forward, your purchased download will already be updated to version 1.3 for you. What if I didn't get the update e-mail? If you did not receive your update e-mail don't fret! X-Aviation has updated our system to allow all customers to update with ease, regardless of whether you received an e-mail for the update! Here's what to do: 1. Login to your X-Aviation account here: https://www.x-aviation.com/catalog/login.php 2. View your past order history invoice that contains the Corvalis purchase on it. 3. At the bottom of the invoice you will find a blue highlighted link to your update! The new installer does not require you to have any Corvalis installed, and you also do not have to uninstall any Corvalis. Simply run the installer and follow the on screen prompts when you run the update! ------------------------------------------------- Version 1.3 of the Cessna Corvalis TT includes a significant remake/upgrade to the PFD Inset Map and the MFD Map Page. We are now utilizing features of Gizmo that have allowed us to fully integrate a Moving Map into the C400. The following is a list of additions/fixes included: CHANGES: -The PFD Inset Map and the MFD Map Page both include a "Moving Map" featuring "Topography" or "Terrain" Modes. -When in "TOPO" Mode an Elevation Scale is displayed with ground height and Aircraft MSL indicators. -When in "TERRAIN" Mode a Terrain Scale is displayed. -PFD Inset Map and MFD Map Softkeys have been added to allow for selection of "TOPO" or "TERRAIN" Mode. -MFD Softkeys have been updated/changed to be more like the "real" G1000. The "TFC" Key is now "TRAFFIC" and the "WXR" Key is now ""STRMSCP". -New icons have been added to the MFD map to indicate when "STRMSCP", "TRAFFIC", and "TERRAIN" Mode have been selected. -The Aircraft icon on the MFD Map has been moved more toward the bottom of the display to more closely match the "real" G1000 and provide more "look-ahead" capability. -The "Nav Range Ring" on the MFD Map has been scaled down and now includes a "Range Box" displaying the range of the ring in NM. The overall map range is displayed in the lower right corner of the map page. -All X-Plane map icons (Airport, Fix, NDB, VOR, and Traffic) have been customized to more closely match those of the "real" G1000 and to be consistent with those displayed in the Waypoint Information Window. -The Vertical Speed Pointer on the PFD in 3D cockpit view now moves vertically with variations in the vertical speed of the aircraft. -The SFC and Fuel Flow gauges have been re-calibrated to more closely match that of the POH. -The FMS Waypoint Entry process has been changed so that when entering a new waypoint the FMS will find the "nearest" waypoint (of type) to the aircraft (for Index 1) and the "nearest" waypoint (of type) to the previous waypoint for all other indexes. A huge thanks goes out to Ben Russell and his development of Gizmo! Without his contribution to the community features such as the maps could not be possible. Please consider donating to his continued development for such an awesome program! More info on how to support the project is here: http://forums.x-pilot.com/index.php?topic=2040.0 As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support! Enjoy these latest updates, and stay tuned to the forum as we continually announce the latest happenings.

Glad to hear all is well still in Simon's CRJ-Land!

Hi, Caneman, We can appreciate your want and enthusiasm to receive this patch. We'd like just as much to get it to you. With that said, please trust that when we have news we'll post it. At this time, we don't have much more news than we're actively working on it and will have it out very soon. Best, Cameron

You need to please attach your log.txt and crash txt log file as well.

That would be an un-activated product. As you just activated, I assume this was on your first load up of the CRJ. When you fail to activate within 30 seconds of loading the aircraft the screens will go blank until after you activate and re-load the aircraft.

Yes, this is normal. It doesn't delete these files or folders so that you do not lose data that does not come stock with the CRJ.

Straight from the hardware test page: This test is not an indication of how well the product will perform on your machine, but rather a test to see if your hardware is compatible. Hope that clears that up.

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!