Cameron

Really nice work, Pete!

This is your computer loading tiles in the background, not a parameter issue (dsf to dsf). If I remember correctly, your computer was a bit lower spec and is the cause of what you're experiencing.

You do realize the potential to make such a change is not as simple as you're currently used to, right Dhruv? Surely you do! Bear in mind every screen is drawn through CRJ code and NOT X-Plane Planemaker displays, so insinuating something is simple when it may very well not be is probably not the best way to suggest something to people. You and I go way back as friends, so I'm comfortable telling you this. Knowing Philipp he'll implement this and get it done quickly. There's never been a time where I haven't seem him so dedicated to a project, which is even more why your harsh words in a previous post can be easily perceived as insulting. Of course, we'll be waiting and looking for the same standards upheld for your product when the day comes!

Way cool, Philipp! Nice job!

I've reset your download. That said, I'm not sure how it's possible for you to "update" Gizmo. We ship with the latest version of Gizmo, and shipping with anything LOWER will cause your C400 to misbehave.

What resolution setting are you at in the X-Plane rendering settings?

I've been eyeing this one for a while and considering a purchase. How do you like it, Will? Fun to fly?

Hi, Careless, PMDG/MSFS are two very different things when compared to X-Plane. OpenGL vs DirectX for starters! Given your system specs, I think the first thing that sticks out is your CPU. The E7500, while great in its time, is aging relatively quick (I had an E8600). The CRJ works so "fast" with your cold and dark situation because the displays are not showing anything. These displays are primarily driven by your CPU, exhausting all CPU cores that it's able to. The E7500 is bottlenecking your 5870 (great card, by the way), which is also contributing to your lower frame rate, but not near as much as the CPU itself contributes to the operation of the CRJ. There are a few topics in this forum that have discussed ways to "preserve" fps, but overall you're not going to see a big improvement until you make the upgrade on the CPU.

Of course I have, Steven. Thanks.

And so now we have two. That said, Jason is out of state as mentioned and this will be on hold until he returns.

What you've seen is what there is for the moment. Thanks for your interest!

Glad you found it, Graham. In the future please seek support for this product through the appropriate support channel. As much as I'd like to help you as quickly and easily as possible, I really must focus on those who pay us to do so. If you like X-Aviation's support then please show your support and purchase from that venue instead for future products that are sold between the two. Thanks for your understanding, and happy CRJ flights!

Graham, None of this sounds right. You should be: 1. Downloading version 1.2 2. Unzipping 1.2 to your desktop or somewhere outside of X-Plane 3. Starting up the setup file...in this instance you're on Windows, so start up the setup.exe 4. Select your main X-Plane folder for installation...NOT any aircraft folder. Done. Lastly, I cannot find any order for you with X-Aviation. Please follow the posted policy:

I'm really unsure by a couple of things here...what did you "put in your aircraft folder?" You should be selecting the MAIN X-Plane directory and not placing ANYTHING in any aircraft folder at all.

Thus far you are the only one, yes. Jason is currently out of state with personal obligation. He'll be back soon.

Thanks! I'm happy to hear all went well for you. One of the key things we did here was recognize that many people would have downloaded additional liveries, so we keep those during this process. This means our customers don't have to re-download liveries as you've already noticed. Blue Skies!

Hello, all, Thanks for everyone's patience as we sorted out plug-in conflict issues! This will serve as a formal forum announcement that we have released the version 1.2 update for the Take Command! CRJ-200. All customers who have purchased the CRJ-200 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 CRJ-200 from today forward, your purchased download will already be updated to version 1.2 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-aviati...talog/login.php 2. View your past order history invoice that contains the CRJ-200 purchase on it. 3. At the bottom of the invoice you will find a blue highlighted link to your update! The new installer will detect whether this is a new install, or if you already have any CRJ-200 version installed. Depending on your current situation, the installer will run through the appropriate paths with you, including uninstalling all unnecessary items from the previous version! There are some important fixes and requests implemented in this update. The following is a list of additions/fixes included: * Added sounds from Turbine Sound Studios to the CRJ200. * Added custom sounds (introduction to sound plugin. More to come in future updates) * Corrected Navigation Display projection to work with legs crossing the 180 meridian * Corrected insertion of missed approach waypoints, fixing a potential issue when the missed approach and the approach transition contain the same waypoint * Corrected calculation of remaining distance to not include missed approach * Fixed crash when selecting a new SID without re-selecting runway * Corrected insertion of RNAV approach transitions that do not depend on STARs * Corrected APU fuel consumption (didn't use any fuel before) and inhibit APU start when fuel in feeder tank is insufficient. * Small fixes to improve stability, fixed some issues that could cause X-Plane to freeze * MAC only: transition to a new compiler and SDK, improving overall fluidity by better optimizations. These optimizations require at least OSX 10.6 Snow Leopard to work. 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.

Hello, All, This is an update to inform everyone that we have now come up with a solution for release and the 1.2 update is now being compiled into installers. We'll see you in the skies soon!

In due time!

Great news, Keith! Congratulations!

Thanks for showing some excitement! We are inching very close to a release. There was a MAJOR backend overhaul done for this package. Tests thus far have gone well and we're in the phase of finishing up last minute touches. I don't want to give a finalized date, but I'd say we're VERY VERY close.

Hello, Everyone, This is an update: We have made great progress in determining what the root cause of this issue is, and Laminar is also working with us on this. Part of this will put us in a better position for making your X-Plane 10 transition a bit more smooth. We are all working feverishly to come up with a fix and we are very excited to get this out the door to all of you! So far initial tests of a fix have shown partial success, so we're evaluating final options at the moment. More updates will be posted as they come. Thank you all for your patience! Happy flying!

Looking great! Thanks for the update!

For clarification: We have not sent out any update and don't plan to until a resolution is found. I realize this is a catch 22 for some, as X-Plane.org has released the update for their customers and we haven't, however, I feel it's important X-Aviation's customers get the respect of having this stuff thoroughly tested before hitting your digital shelves only to be surprised with problems. I'll continue to keep people updated as much as possible here. We have pinpointed the source of the issue but do not have a definitive fix just yet. Thanks so much for everyone's patience. We really do appreciate it!

1.1.1 Was a big update for Mac users. I would suggest you use it. As stable as your 1.0 may be, 1.1.1 is far more stable and has been for months! That said, there will be no need to have any particular version installed when updating to 1.2. The updater will figure out what you have and work from there.