Important Information about the Release
-
To make this information as easy to locate as possible, here is a fresh reminder for any users looking to patch their Working Title GNS 530/430 so that it can be used with the Dukes in SU14. This is only required if you are on SU14 (as opposed to SU15 Beta), and want to use the WT GNS before SU15 and have not done so already for previous Black Square aircraft. As soon as the simulator is updated to SU15, you may disregard this information.
This patch is optional and only for users who wish to use the WT GNS 530 with the Dukes before SU15.
Due to a bug introduced with SU14, the following change can be made to your local copy of:
...\Official\OneStore\workingtitle-instruments-garmin-gns\html_ui\Pages\VCockpit\Instruments\NavSystems\GPS\WT530\WT530B.js (and WT430B.js)
Search for "Update loop for the main screen", and replace the existing update function with the following:
update() { var _a, _b; const isPrimaryInstrument = this.props.options.navIndex === 1; this.clock.onUpdate(); this.props.backplane.onUpdate(); if (isPrimaryInstrument) { (_a = this.autopilot) === null || _a === void 0 ? void 0 : _a.update(); // Planner update const now = Date.now(); if (now - this.lastCalculate > 3000) { this.planner.hasFlightPlan(msfsGarminsdk.Fms.PRIMARY_PLAN_INDEX) && this.planner.getFlightPlan(msfsGarminsdk.Fms.PRIMARY_PLAN_INDEX).calculate(); // SimVar.SetSimVarValue('K:HEADING_GYRO_SET', SimVarValueType.Number, 0); this.lastCalculate = now; } this.gpsSynchronizer.update(); } (_b = this.vnavController) === null || _b === void 0 ? void 0 : _b.update(); if (this.currentPowerState === PowerState.On || this.currentPowerState === PowerState.OnSkipInit) { this.gpsSatComputer.onUpdate(); } }@Black-Square said in Important Information about the Release:
Due to a bug introduced with SU14, the following change can be made to your local copy of:
...\Official\OneStore\workingtitle-instruments-garmin-gns\html_ui\Pages\VCockpit\Instruments\NavSystems\GPS\WT530\WT530B.js (and WT430B.js)
For Steam users, just go to your community folder then go up one level, you should find your Official folder there along with your Community folder (and of course you go to Official\Steam not Official\OneStore)
-
To make this information as easy to locate as possible, here is a fresh reminder for any users looking to patch their Working Title GNS 530/430 so that it can be used with the Dukes in SU14. This is only required if you are on SU14 (as opposed to SU15 Beta), and want to use the WT GNS before SU15 and have not done so already for previous Black Square aircraft. As soon as the simulator is updated to SU15, you may disregard this information.
This patch is optional and only for users who wish to use the WT GNS 530 with the Dukes before SU15.
Due to a bug introduced with SU14, the following change can be made to your local copy of:
...\Official\OneStore\workingtitle-instruments-garmin-gns\html_ui\Pages\VCockpit\Instruments\NavSystems\GPS\WT530\WT530B.js (and WT430B.js)
Search for "Update loop for the main screen", and replace the existing update function with the following:
update() { var _a, _b; const isPrimaryInstrument = this.props.options.navIndex === 1; this.clock.onUpdate(); this.props.backplane.onUpdate(); if (isPrimaryInstrument) { (_a = this.autopilot) === null || _a === void 0 ? void 0 : _a.update(); // Planner update const now = Date.now(); if (now - this.lastCalculate > 3000) { this.planner.hasFlightPlan(msfsGarminsdk.Fms.PRIMARY_PLAN_INDEX) && this.planner.getFlightPlan(msfsGarminsdk.Fms.PRIMARY_PLAN_INDEX).calculate(); // SimVar.SetSimVarValue('K:HEADING_GYRO_SET', SimVarValueType.Number, 0); this.lastCalculate = now; } this.gpsSynchronizer.update(); } (_b = this.vnavController) === null || _b === void 0 ? void 0 : _b.update(); if (this.currentPowerState === PowerState.On || this.currentPowerState === PowerState.OnSkipInit) { this.gpsSatComputer.onUpdate(); } }@Black-Square Thank you 1000 times for this decision! <3
-
Guys, everything is back up and running now. Apologies for that period of downtime.
Thank you.
-
is that similar issue than this thread ?
https://community.justflight.com/topic/6342/cannot-move-tablet-around/14
people had to switch sim interaction mode from Legacy to Lock in accessibility setting -
is that similar issue than this thread ?
https://community.justflight.com/topic/6342/cannot-move-tablet-around/14
people had to switch sim interaction mode from Legacy to Lock in accessibility settingi did try to change the mode to "interaction mode from Legacy to Lock" I still can not touch anything on that iPad unless I am looking around in middle-mouse and aiming the center of my screen on what I want to select on Ipad
and when I did go to Lock mode. i was able to move the iPad but sill not able to touch it / select any thin on it -
did you made some change to your mouse control ? if yes maybe give it a try with default mouse control (for that just go to control setting, select your mouse, press M to enter profile manager and create a new profile, it should create a new profile with default control ?)
also have you tried with no other mode to be sure it s not another mode conflicting ? -
did you made some change to your mouse control ? if yes maybe give it a try with default mouse control (for that just go to control setting, select your mouse, press M to enter profile manager and create a new profile, it should create a new profile with default control ?)
also have you tried with no other mode to be sure it s not another mode conflicting ?@Nicotine70 Yes i have not changed any thing on the mouse controls and I rest them
https://drive.google.com/file/d/14lV9CQHQbLAX1yPHI5TKaXvrDMSQ2Vwy/view?usp=drive_link
ass you can see in the videos
https://drive.google.com/uc?id=1JjMWOmKNwKTQvHZ-ixHO4f8RzJoi9WQc -
sorry that was just a thought, I don't have more suggestion :-/
it s curious that it register click only when middle button is pushed... -
Sorry you're having this issue. Since you're either the only one, or one of very few, reporting this issue, I suspect that it is something about your specific installation, and not the product. If I haven't already done so elsewhere, I suggest that you make a ticket with Just Flight support, as they are vastly superior than I am at troubleshooting simulator level issues. They might have already seen this in other aircraft too, and already have a solution.
-
To make this information as easy to locate as possible, here is a fresh reminder for any users looking to patch their Working Title GNS 530/430 so that it can be used with the Dukes in SU14. This is only required if you are on SU14 (as opposed to SU15 Beta), and want to use the WT GNS before SU15 and have not done so already for previous Black Square aircraft. As soon as the simulator is updated to SU15, you may disregard this information.
This patch is optional and only for users who wish to use the WT GNS 530 with the Dukes before SU15.
Due to a bug introduced with SU14, the following change can be made to your local copy of:
...\Official\OneStore\workingtitle-instruments-garmin-gns\html_ui\Pages\VCockpit\Instruments\NavSystems\GPS\WT530\WT530B.js (and WT430B.js)
Search for "Update loop for the main screen", and replace the existing update function with the following:
update() { var _a, _b; const isPrimaryInstrument = this.props.options.navIndex === 1; this.clock.onUpdate(); this.props.backplane.onUpdate(); if (isPrimaryInstrument) { (_a = this.autopilot) === null || _a === void 0 ? void 0 : _a.update(); // Planner update const now = Date.now(); if (now - this.lastCalculate > 3000) { this.planner.hasFlightPlan(msfsGarminsdk.Fms.PRIMARY_PLAN_INDEX) && this.planner.getFlightPlan(msfsGarminsdk.Fms.PRIMARY_PLAN_INDEX).calculate(); // SimVar.SetSimVarValue('K:HEADING_GYRO_SET', SimVarValueType.Number, 0); this.lastCalculate = now; } this.gpsSynchronizer.update(); } (_b = this.vnavController) === null || _b === void 0 ? void 0 : _b.update(); if (this.currentPowerState === PowerState.On || this.currentPowerState === PowerState.OnSkipInit) { this.gpsSatComputer.onUpdate(); } }@Black-Square and to fix the auto pilot on the Piston Duke , on May 13th while trying to fly I set the Auto Pilot and all it wants to do is a death dive by using thr KNX radios since I wanted to fly an RNAV PROC.
-
I've never seen that behavior before, and nobody else has reported it yet. Could it possibly be a hardware binding issue? If not, Just Flight support might have seen this behavior in other aircraft, since they have an extensive troubleshooting database that might be able to help you.
-
I too am having issues with the Duke (Turbine) Autopilot. For one, as soon as I turn it on it immediately kicks off and I believe it's also setting the elevator trim to full nose down. This is on top of a left banking spiral that is un-recoverable despite rudder and aileron trim showing to be centered... Also, my tablet doesn't really work. I can only see the first tab and it doesn't move around like the demo videos showed.
