Cameron

I'll also continue to investigate this.

We're not looking for ways to change anything at the moment, but thanks, Kyle. I'm glad you enjoy the CRJ enough to try and dig deeper and learn everything about it! Much of calculations are defined by the parameters by which X-Plane calculates things. Laminar may be very interested in your findings (Austin more specifically). I cannot guarantee it with their workload, but perhaps! There are multiple variants of the CRJ, with various weight configs and features. We opted for as balanced as was necessary with the assistance of CRJ-200 pilots on hand (I also remember a number of check airmen "signing off" on this product...a number of which can be found in this forum). Have fun above all, Kyle, and Happy New Year!

I'm not sure what you're talking about here, Luke. The SDK has rules to follow to build and develop plug-ins which expand the features of X-Plane. This aircraft uses other datarefs than what GoFlight is looking for due to various reasons. This is why the plug-in is not working for you. More discussion on this has already taken place here: http://forums.x-pilot.com/index.php/topic/4317-incompatibility-with-saitek-panels/

Thank you for the heads up, Dan's cheerleader! You always have those pom poms at the ready. Nice looking add-on. Will probably pick it up.

The practical reason lies with the fact that as a novice programmer, Javier did the best he could and doesn't know how to create commands at this time.

You need to consult whomever makes the plugins for GoFlight hardware. We do not control that! We do offer a list of datarefs to link things to: http://forums.x-pilot.com/index.php/topic/1871-list-of-all-crj-datarefs-cockpit-builders-heat-up-your-soldering-irons/

Awesome, Keith!

Please submit a support ticket at X-Aviation for this. http://www.x-aviation.com/catalog/contact_us.php

I'm not quite sure how this could be happening for you. I've just loaded 1.4.5 in the latest version of 10.2 even and I can POS INIT each and every time. You're saying you can't even get this to work on your first aircraft load? I don't even have a complaint from anyone about this until here, for that matter.

Datareference. I don't believe Javier opted for any commands on this aircraft.

Perhaps I don't follow you here. Given you are a programmer and are capable of creating what you need with a list of datarefs, what's the problem? The list is here: http://forums.x-pilot.com/index.php/topic/4380-custom-datarefs/ Seems simple enough to me. One dataref to control bigger numbers knob, one dataref to control lower numbers knob.

http://www.vattastic.com/

You are assuming things like the radio should be able to use default and not custom. In this case you are wrong. The rules developers follow are very simple: Use default datarefs if they do what you need them to. If they don't, custom is the only way. We will not be releasing a default only route. Given that custom plug-ins are the way for the future, perhaps it is time developers of hardware related plugins consider other options (like INI files that allow the dataref for which a product should listen/adjust for). This would at least standardize things a bit, so long as the developers agree to make CMD compatible add-ons.

It does depending on your hardware and how you have things configured in X-Plane.

Hi, Harfang, I have changed your download as well. That said, based on your CPU and GPU as well as the fact you have no issues in X-Plane 9, I'm not sure this will solve your issues in 10. Your system will be rather taxed with X-Plane 10 no matter what.

Weather is not something we control.

This makes no difference at all. X-Plane is running in 32-bit mode, so it can't access anymore than the 3GB of ram you see already in use.

Hi, Mike, I've changed your download to version 1.4.5. Please download this, install, and see if things change for you.

Sounds like you are having memory exhaustion issues. A few things to try: 1. Re-name your Custom Scenery folder to Custom Scenery_old 2. Create an empty folder in place of it called Custom Scenery 3. Lower your resolution setting and restart X-Plane. After these steps does the problem persist?

In short, 64-bit will be the answer for the 1.5.x series.

You may want to also try going back to 1.4.5 if you have that available.

There's no plugin for this aircraft, so if there's something not working for you I'd say it's on your system. I can't duplicate the same issues as you, and we've received no reports of such.

This definitely has nothing to do with Oahu. Never seen or heard of this before, and we don't use any form of plugin that could even BEGIN to mess with settings like that. Perhaps deleting your preferences would be a good start.

Go to the rant section for this kind of talk, please. The .org serves a tremendous purpose to the X-Plane community and I do not hope it disappears. While I do not agree with the tactics of the owner and operator, I believe the community itself is valuable.