Cameron

Kyle, A topic made in January of 2012 is new to you? This topic is quite old. Over 365 days old. Again, please do not open up old topics.

Kyle, please don't resurrect old threads.

Must be something else at play then because 'B' is definitely brake toggle.

You have the templates...it's a layered PSD file...turn off the Brit Air layer if you want to rid of Air France.

Can you please try this in a demo install of X-Plane 9 and also provide your latest log file?

Cool shot! Where was this? I like the trees in there!

Erik, The assumption here when you asked if you could post here was that you had screenshots of a fly-in to post. Others here are correct, this is not the correct section (topic has now been moved). A note to all: I do NOT condone this to be any bit of an "official" fly-in for X-Pilot at all. If you choose to partake in anything Erik does, know that it's assumed to be for fun and not organized or appointed by us here. Erik: This is the last time I'm going to say this....shape up, or get out of here. You are consistently rude with comments like "I don't care what you think" type talk. The next time you're gone...for good.

Only a photographer can say that and legally get away with it.

Just have fun!

Sorry to hear about this, Zymurg! I followed that topic and pretty much knew how it would end up, but it's sad that I even knew that and was correct as to the end result. Either way, welcome to our friendly community! We're happy to have you here!

Are the sounds similar to how Carenado does theirs, Steven? Looking forward to hearing your final thoughts on this whole thing prior to buying!

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.