Cameron

As this has now been solved, this topic is closed.

Aside from being a large package, it was also completely finished at one time before we decided we did not like the quality and scrapped it to start completely over.

This topic is now closed.

Hello, all, This will serve as a formal forum announcement that we have released the version 1.4.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.4.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 that says: "Take Command!: CRJ-200". 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! Your liveries/downloaded paints will be safe in this process! There are some important fixes and requests implemented in this update. The following is a list of additions/fixes included: [bUGS] -Fixed the crash on loading a SID or STAR when magnetic information was not loaded because of a long absolute path -Warn of incomplete navdata installations -Enhanced recalculation of Dme-intercept waypoints -Fixed pagination issue when selecting an approach transition -Fixed a problem displaying DMEs on the WPT Sel page -Fixed recalculation of remaining distance to destination -Enhanced compatibility with some third-party plugins such as FSAirline manager and Airport navigator 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.

As we prep the 1.4.2 release this topic is now closed for organizational purposes.

As we prep the 1.4.2 release this topic is now closed for organizational purposes.

As we prep the 1.4.2 release this topic is now closed for organizational purposes.

As we prep the 1.4.2 release this topic is now closed for organizational purposes.

As we prep the 1.4.2 release this topic is now closed for organizational purposes.

This has been in place since pretty much the beginning, Jim. I believe showing you how to program the FMS step by step is present in the tutorials.

In the very topic having to do with CRJ crashes....

Kyle, If you've done any research on your issue at all you'd realize the issue you are experiencing has been solved and is in internal beta testing for 1.4.2, so yes, we expect your patience at this point as well as your diligence in searching for and reading topics that have to do with the same bug you are experiencing.

Very odd, Arti. I have seen reverse of what you speak of on someone else's machine. Nothing CRAZY, but a big improvement over the last series.

Wait for the next update. It's definitely not an activation issue.

Better to just wait for the next patch.

I'm a distributor. I'm pretty well versed in what's going on with X-Plane thanks to X-Aviation's relationship with Laminar. Whomever you talked to is going off of faulty data in their database. It will NOT be that price, nor will it release that day. Laminar has double verified this and is looking to correct the data. The Graphsim side is not supposed to be in production for a few more months, let alone at that price.

This is a mistake in price and the release date is also wrong (will be April). This product will also ONLY include US scenery, not global like we sell.

Tom, I could care less what you have to say about issues vs. "bad for business." I don't view any of them as such. This comes with the territory of programming plug-ins, so for me to expect that customers would not complain when something goes bad, let alone report bugs is silly. There is nothing you have ever divulged or stated that is any more or any less "bad for business" than anyone else. My issue is with your demanding attitude. You do this often, it is spoken of often, and it doesn't take many posts to go through from you to see it. If you want support (or to help us provide you with it), post away about your problems. However, including snide remarks about something being boring, demanding instantaneous help over others also seeking support, and a slew of other negative comments included in bug reports is NOT NECESSARY. Say what you need to say in your support posts and leave the negativity at the door. It's simple. I really don't feel like digging up each negative remark from you. I consider you smart enough to know what I'm requesting, so I'll leave it at that.

Tom, You know this has not always been the case. Things have been quite stable for some time, and 1.4.1 is a big update with apparent growing pains. Please discontinue with the always negative, demanding posts. I will not hash this out further with you here. There are many customers, all to which we are listening and tending to. Everyone deserves equally fair time and support, and that's how we delegate our time. You may downgrade if you see fit for the moment. I, as well as the others, are quite tired of the posts from you when you do happen to have a problem that make you feel you demand more attention than everyone else as a paying customer. This is your only and final warning regarding this. Please consider and think before you post. This is the end of such discussion. Do not respond to and drag this out. You have been informed. The CRJ is a very well supported product with a team of very dedicated individuals. Updates don't happen "just because." Items will be investigated and fixed in a timely fashion, and I stand by my feeling that this product is among the best supported products in the community.

Crash logs are really necessary when reporting these issues, guys. Please!

The issue is definitely the three monitors vs. that card. You are battling fill-rate. There really isn't a card to date that can handle what you're trying to achieve as a single GPU in games as heavy as X-Plane. SLI and X-Fire is it, and as of now XP still cannot take full advantage of this. The card that comes anywhere close to capability right now as a single GPU is the 7970.

We'll investigate this. Open your LEGS page on the FMS and verify that those three are not listed at the end of your flight plan.

Can you do us a favor...I recognized this with another customer earlier... Can you go into your Resources/Plugins/ folder and see if vascore is in there? If it's not, this is good. Just double checking. The installer should have deleted this, and the CRJ should tell you if it's present when it shouldn't be, but we did have one customer who was not alerted and found this folder. When deleted, his crashes went away.

Sadly, there is not that type of thing on a wide scale multiplayer level. You could, however, logon to PilotEdge, VATSIM, or IVAO and fly in controlled airspace with others online.

I'd have to agree with you there. Nice job!