Autopilot After SIM Update 14
-
Happy to try anything. I also opened a ticket with Just Flight about a week ago and they told me to uninstall the older Working Title GNS 530 package in the MSFS marketplace. But this did not fix the problem. Haven't heard from them since
Similar to the person in the other thread about the Baron ... It always works the first time you load up MSFS, but every time after that it stops working. It also works when you start the flight on the runway. My suspicion is that it's something to do with black square's state saving
-
And regarding the conflicts... I don't have any other mods installed.. just a few other aircraft like the Flysimware 414 and the WB sim 172
-
It also seems to be related to another bug which is your flight plan not showing up in the GNS 530. When it correctly loads, the autopilot works fine
-
I only use the TDS 750. I do own the PMS version, but find it a little weird since I'm so used to the official Garmin version. I've flown the King Air twice, the Bonanza once, and the TBM two or three times in SU14. I have not had any issues with the AP not engaging or following commands. I arm the ALT panel and then engage IAS and HDG or NAV on climb out. ILS/RNAV APP modes work fine too.
Maybe I've just been lucky? I do have the WT 530 installed in MSFS, but I do not like the older Garmin 430/530 units, they're not as user-friendly as the 750, nor can you tweak settings or the flight plan fast enough. They were great years ago however, lol.
-
Thank you all for providing more information, and for the votes of confidence. I've dropped everything else I'm working on to focus on this right now.
I have good news! I was able to replicate what you were seeing, and I have found a single line to be the culprit in the new WT GNS. I don't fully understand why, but I am able to produce the bug with 100% reliability by toggling that line on and off. You were right that this could be avoided if the instrument was loaded as the primary on startup, and never unloaded by the aircraft's state saving. I'm very confident that this is the culprit, and the TDS issue was only a side effect. Luckily, this is very easy for you to fix locally, but I will obviously have to contact Working Title for a patch to be made. Please make the following change to...
...\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(); } }Once you have seen if this solves your problem, please tell me asap so that I can contact Working Title. Thank you all for working with me. I hope this is the solution. Good luck!
-
Thanks so much for looking into this. I won't be home until Friday but hopefully someone else here can test this
-
B Black Square referenced this topic on
-
Thank you for the message! I'll wait to see if I can get a couple more confirmations, and then I will write to WT.
I'm so sorry that this took more than a week to find. I should have jumped on it immediately, but I assumed it would be fixed quickly if the problem had been with the WT GNS. The reason the problem doesn't occur in other aircraft, btw, is that the GPS never has to reboot in aircraft without hotswapping, but in my aircraft, the active GPS will often reboot at start when the configuration is synchronizing.
-
Thank you all so much. I will write to Working Title immediately. I have been working on my own improvements to the GNS 530 recently, so hopefully they will be receptive to those, and you can have an even better experience. Pretty please share this fix and the news of an upcoming patch with those on the MSFS Official Forums that might be having the same problem. I'll let you know when I hear from WT.
-
K knidarkness referenced this topic on
-
I had a strange incident with the 530 earlier. I loaded into the TBM, set up ground power, and checked the avionics (I run one 530). It did not load my flight plan from the world map, so I loaded it manually.
When I shut everything down and did a full start of the plane, the flight plan showed, but it was like there was no flight plan as there was nothing that would activate and nothing would delete.
Going back to the menu and loading my flight plan, then loading into the TBM and doing the same thing as above worked fine, except the GNS loaded the plan on its own this time.
Does that sound like it's related to this issue with the turning off and on?
-
-
-
Unfortunately, changing the WT code as described above did not fix the issue for me. When the GNS 530/430 is selected in the plane, I still am unable to engage NAV to use VOR navigation . Altitude and VS did work.
Swapping in the PMS50 GTN to the first slot allows NAV to work properly. -
Did you encounter this issue immediately after updating to SU14? Given that I've seen this work for so many people now, I think we've likely found the sole issue introduced by that update, but that doesn't mean you're not experiencing one of the known GPS incompatibilities our outdated files. Feel free to share more details with me, or contact JF support. They've gotten quite good at tracking down the regular GPS product issues. I'm all ears.
-
I find that I cannot setup the AP to intercept and capture a VOR radial by putting the AP in HDG and ARMing NAV. NAV will not turn on when the CDI indicator is not in the active range (that is, when the CDI is all the way off to one side or the other of the HSI).
-
I to am in this Autopilot mess. Absolutely nothing works ie HDG NAV ALT, HSI is completely bonkers. however I discovered that if I load the way points from the MSFS world map it’s all good.
I’ve only had the aircraft 2 days so I’m a bit annoyed it’s not working really. Although I do admit it’s a beautiful thing to hand fly.
Am I supposed to install WT stuff myself? I assumed it would already be within the sim.
Cheers -
If you use any other GPS or none at all, the AP works fine... only the current 530 has this bug.
Im using the the PMS 750 currently and having no issues.@Lemny said in Autopilot After SIM Update 14:
If you use any other GPS or none at all, the AP works fine... only the current 530 has this bug.
Im using the the PMS 750 currently and having no issues.Ok thanks, unfortunately I'm not a fan of the 750 so hopefully the fix will be out soon.
I'm pretty sure V1 simulations had the 750 play funny a week ago, the AP flew ok but the HSI was completely bugged out. -
Just a reminder to anyone coming to this thread later, but you can fix the current GNS 530 bug with one copy-paste edit to one file on your computer right now.
I know that's not the most convenient solution, but for anything better, I would have to post the entirety of WT's work. I also worry about generating yet more "compatibility" mods in the wild for people to further confuse their installations with.
For those following along, I have not heard back from Working Title yet, as I suspect they are off for the holidays. I have heard that this solution is being discussed with the developers on their Discord, though. I will let everyone know when I hear back from them.
