v1.1 Update Details
-
I would like to say a big thank you to Black Square for updating a product that was already excellent. It is so good that this developer does not forget about customers as soon as they have bought a product. We all know of some big name developers who are extremely bad at updates, even for serious issues. But in this case we have a developer who has quickly updated the aircraft after listening to feedback.
That is excellent customer service. I wish that some other companies would take note.
Jerry
-
I am extremely disappointed that they haven't fixed the missing left side oil cooler door. Something this obvious should have been at the top of the list.
-
@CXDriver227 wow, really? Could you post a reference where this was pointed out and ignored? Haven't heard of this one before.
-
-
-
@dherrero, the initial release for some people was v1.0, which is the most logical version numbering so the update is referred as v1.1 to make it easier.
However, on JustFlight, the actual file name and version is v0.1.1
v0.1.1 is the official label, v1.1 is just a misuse of language -
The autopilot only works correctly with certain avionics package choices and not with others
I get the message about either updating the GTN avionics and or reinstalling the Duke turbine
. I'm definitely on SU 15
"This instrument has been disabled due to a bug introduced into the WT GNS 530/430 in Simulator Update 14 (SU14).
When SU15 is released, reinstall this aircraft and click the option for SU15.
Users on SU15 Beta, or those who have already patched their WT GNS, may reinstall immediately to use this instrument. -
You're saying that you get that message on the GNS 540/430 right now? That message was removed completely from v1.1 of the Dukes, and can be bypassed by selecting the correct installer option in v1.0. If you have v1.1 installed and you're still getting that message, then try uninstalling the aircraft completely and reinstalling, just in case the installer missed updating the files somehow. If you still receive that message, then there is something truly strange going on, and I can send you to Just Flight support to look further into the problem. If that's not what you're seeing and I misunderstood, please feel free to explain some more.
-
@Black-Square I'll check today to see if I'm still on an older version of the Duke Turbine. If so and updating doesn't help then I'll update the avionics packages.
"Why is the autopilot behaving strangely, not changing modes,
showing HDG/NAV simultaneously, or not capturing altitudes?
This is indicative of GPS addon incompatibility. Please make sure that you have updated all
the avionics packages that you are using, including the TDS GTNxi 750, the PMS50 GTN 750,
and the WT GNS 530, and that you do not have any outdated packages, such as the original
PMS50 GNS 530 modification.
No additional packages should be required for the autopilot to work correctly with the
various GPS choices. The product is tested with ONLY the TDS GTNxi 750, the freeware
PMS50 GTN 750, and the free WT GNS 530 marketplace package installed. Please see the
“Third Party Navigation & GPS Systems'' section of this manual for more information" -
@Black-Square version 1.1 was installed on June 14th so I'm uninstalling and downloading now to re-install. Do you expect I'll need to look for GNS updates also?
-
After re-installing if I choose 530 (650 secondary) the AP is ok but the top avionics unit shows the error message. With 750-650 AP is not ok ( shows go around button for no apparent reason etc)
With either KLN90B or KX 155B the screen looks right and the AP works.
I've been mostly a VFR pilot who uses AP a lot, so if AP works I could live with the error message,but if I begin to explore IFR it wouldn't be great.Two screen shots here:
[https://drive.google.com/drive/folders/1Hhnu7_ukIsDrBFrl_j4_5FM_wcP86Qcv?usp=sharing](link url) -
Is the GNS 530 working for you also? I had no idea an outdated PMS50 GTN could cause that message to appear, but I have at least a hunch about why that might happen.
