Cameron

Looking forward to seeing it, Jim!

I think you missed $10 for the pack that's NOT part of the "complete package" for the paints from XP Jets. So, with that, I believe CoreyR's pricing calculation is correct. $10 XPJ Paint Pack + $62 FJS 727 Pack + $19.95 Complete Paint Pack + $10 CIVA = $101.95. The CIVA was announced with this product, it's listed as part of the "Boeing Aircraft:727 Series" on the org store, and the 727 does in fact have a menu for it in sim and tells you to purchase it if you want that feature active. It's able to be extended beyond this aircraft and it is Philipp's, but it was released today for a reason, and it's not too far fetched to consider it a part of this package. I'm sure you know what I would potentially say next, Dozer, but I'll refrain this time.

We are not doing any form of support or mods for 10.2 until it goes final as stated in post #9.

No, we protected ourselves against all of this weeks ago.

Still getting acquainted, but thus far I find these sounds to be horrible (especially exterior) in implementation by FlyJSim. The video portrayed them a lot differently. I've heard TSS' sounds in Flight Sim, so I know this isn't their issue, but rather FlyJSim's.

Unfortunately this is a common theme with GoFlight equipment and third party aircraft that use plugins. To Keith: Great video! Thank you for sharing!

Great shots, Jim!

Please remove this video, Radek, and please see the following: https://www.x-aviation.com/catalog/conditions.php (Section 15).

Can't say I know the cause since this aircraft doesn't use plugins, but glad that fixed it.

Sounds like engine management and the side effect of torque.

This has already been addressed, Jerry: http://forums.x-pilot.com/index.php/topic/4226-in-progress-transponder-range/

My best guess would be that you had a session with a previous aircraft where the instrument lighting was turned all the way down, which also controlled these items. X-Plane will "save" this and roll it over to the next aircraft. You can open up an aircraft that has rheostats for this stuff and turn them back up, then load the Duchess to see if that solves it.

I have to agree with this. While we genuinely do not mind providing any customers the support they deserve, to save yourself a lot of frustration it is important you read the material that is already provided to you. Asking questions here which are easily answered in the manual becomes redundant and does take away from the time we can dedicate to bettering the product with more enhancements or answering legitimate questions/bug reports which cannot be answered in the already provided documentation.

This will vary depending on a number of factors. While no charts are published, please consult the manual for speeds and use your best judgement depending on the configuration of your aircraft. Page 9 is there for your reading pleasure.

X-Plane may have fixed the availability of it, but this does not mean add-ons will work right away. This must be re-animated/coded with the new datarefs when published.

Yes.

Not all joysticks are created equal. There are numerous joysticks available which have one more more rotational axis for the purposes of trim (be it elevator or aileron). Javier is stating to not trim your aircraft using the joystick when flying with the Jetstream.

This prevents control surfaces from moving while parked to prevent sudden movement and damage to an aircraft when unattended. It is this way in the real world, and simulated in the aircraft just the same.

Very important to read the manual. Please see page 48 in red text.

Gary, As Javier said in the post just above yours and in response to the fact that it is suggested there should be a delay, he is already looking into this.

A paintkit will be released in time, yes!

For starters, the Jetstream plug-in will not load in 64-bit, which may be the start of your issues. This is 32-bit only for the moment.

Just to clarify, this is explained on page 48 of the manual.

Thank you! We'll be back...

What happens if you make these adjustments with the mouse and not your hardware setup? I'm curious to know the result of that first before we continue to troubleshoot this with you.