Autopilot After SIM Update 14
-
When you say you're switching between GNS 530 and PMS GTN 750, are you referring to changing the config during an active flight?
Black Square has created an innovative option to make changes within the flight session, however I would not be surprised if in-flight changes mess up your flight plan and autopilot behaviour (see my previous post how the devices influence the autopilot models).
Referring to the GNS 530, also remember to have all old mods from the beta version removed, because it is now part of the stock sim.
I have no 530 instrument mods installed, only the PMS 750 is installed. Also, I haven't participated in the betas.
I haven't tested much further, but when I start a new flight with the 530, loading a flight plan into MSFS, sometimes the flight plan seems to load and sometimes it does not (50% of the time in 4 flights). When the flight plan loads, the autopilot seems to work fine. When the flight plan does not load, the autopilot doesn't work correctly. It will only go into attitude hold.
When I found the 530 was not working, I switched to the 750 using the switch in the cockpit. Upon loading the 750, I found the flight plan which should have appeared in the 530, was present in the 750 and the autopilot worked. I then switched back to the 530 with the switch in the cockpit and the flight plan was gone, the autopilot did not work. Back to the 750, and there it was, working again.
My time is limited and so I haven't tried the 530 in any other planes, I've only been flying the TBM 850 lately.
-
So i think i got it. Having as nav1 the 530, Autopilot isnt working, as a matter of fact i think it goes as it is in CWS mode. Switching to 750 even in flight, (and i dont have 750 at all), autopilot is fully working. Switching in flight to KX155 also everything is ok.
-
Please see the other thread https://community.justflight.com/topic/5736/ap-won-t-engage-from-flight-to-flight/3 where people report issues connected to Working Title. May make sense to follow this on their Discord (which is supported very well btw).
-
Looks like I have to modify my post from above where I said problem went away when I did not use addon livery. I did another flight with stock tbm and no livery addons in community folder and had same problem. Seems to work sometimes and not the other time. I tried a flight with A2A comanche and it work, but might a have been one of those times it work, have not had time to do more testing. In WT discord sounds like other planes having trouble too. Hopefully they can get it sorted out.
-
Please see the other thread https://community.justflight.com/topic/5736/ap-won-t-engage-from-flight-to-flight/3 where people report issues connected to Working Title. May make sense to follow this on their Discord (which is supported very well btw).
@sg_aviation ty, i'll check it :)
-
Had an issue with gns530 last night, wouldn’t capture set altitude in either climb or decent, first time I’ve seen this issue
-
I had variations of this issue from time to time and also during the SU14 beta, my config:
- TBM avionics setup - GN530 + KX155
- GTN750 installed (free version) - without the WTT package - Not really in use, just installed
My first hint of the issue is usually being unable to activate "NAV" mode.
I don't have an exact recipe to remedy the problem, but it's either one or a combination of the following:- Switching to GTN750 + KX155 , then to GTN750 + GNS530 , then to GNS530 + GNS530
- Toggling the "1 2" button in the EHSI
- Cycling "NAV" mode in the EHSI and also the "1 2" buttons , and also cycling GPS setups as above.
- Opening the GTN750 mini-panel
- Closing the flight and reloading another livery
- Sim-restart and loading another livery , starting with the GTN750 as the first GPS then switching to the GNS530
Hope it helps, please post if something did "the trick"! it's really hard to pinpoint....
My gut feeling is that the major cause is the broken sim state-saving that breaks some avionics states... but this is just a guess....
-
This is the first thread I've found on this problem since SIM upgrade 14 in Dec 2023.
GNS 530/430 has been working fine for me prior to this upgrade when flying a DC3 in MSFS2020. Dev Mode is off.
When in the DC3 I cannot get ROL to engage after takeoff, or engage HDG or NAV late when on course. When I engage HDG, the plane will head north and stay there even if I adjust the desired heading. The VS works OK.
Then I tried the Cessna 172 and all functions were fine.
I tried deleting and then reinstalling workingtitles GNS from the marketplace. No joy. Then I tried deleting all DC3 add-on liveries from Community, still no good. I am not running any other addons for the DC3.
So obviously I am baffled. Why does it work in Cessna 172 and not the DC3? Basic functions like ROL should not be a major challenge! I am guessing the DC3 cfg files are over-riding the GNS settings. This will definitely spoil my Xmas plans for long-distance DC3 flights......
Barry -
I had variations of this issue from time to time and also during the SU14 beta, my config:
- TBM avionics setup - GN530 + KX155
- GTN750 installed (free version) - without the WTT package - Not really in use, just installed
My first hint of the issue is usually being unable to activate "NAV" mode.
I don't have an exact recipe to remedy the problem, but it's either one or a combination of the following:- Switching to GTN750 + KX155 , then to GTN750 + GNS530 , then to GNS530 + GNS530
- Toggling the "1 2" button in the EHSI
- Cycling "NAV" mode in the EHSI and also the "1 2" buttons , and also cycling GPS setups as above.
- Opening the GTN750 mini-panel
- Closing the flight and reloading another livery
- Sim-restart and loading another livery , starting with the GTN750 as the first GPS then switching to the GNS530
Hope it helps, please post if something did "the trick"! it's really hard to pinpoint....
My gut feeling is that the major cause is the broken sim state-saving that breaks some avionics states... but this is just a guess....
@glideslope said in Autopilot After SIM Update 14:
My gut feeling is that the major cause is the broken sim state-saving that breaks some avionics states... but this is just a guess....
I'm not pertained by the issues and don't have a solution. However my gut feeling remains that this constant in-flight changing of devices further increases complexity and error-proneness.
My personal approach is to decide for the device to use first, set up mods accordingly and then start the session. If GNS530, remove GTN750 from community folder. If GTN750, install and add WTT mode package (it should then auto-load). I'm not relying on any panel state saving at the moment.
Regarding errors with the GNS530 recommendation is to follow the Working Title Discord, especially since apparently more aircraft than the TBM are pertained.
-
I tested your theory by disabling the PMS50 GTN750 (removing from Community folder). On first flight test the problem occurred. The flight plan did not load into the 530 and the autopilot did not work. As you've probably seen, on the WT Discord there seems to be potential consensus that this is happening only with Black Square aircraft.
I don't think that changing nav devices during flight is anything new unless Black Square are somehow doing it differently. The Just Flight Piper Arrows did this and so also does the A2A Comanche I believe.
-
GNS 530 doesn’t work on some occasions since SU14
-
Hi guys! I'm having the same problem on the Analog Caravan. I also own the Bonanza and the Baron from BS. I will test them out with the 530 and see if the problem persists. I wil also test with any aircraft that uses the 530 NOT from Blacksquare.
-
AUTOPILOT FIXED
Hello, all. I'm sorry to keep you all waiting for this solution. As this looked entirely like a problem with the WT GNS after SU14, I was waiting for a solution from Asobo/WT. I looked into the problem myself yesterday and discovered that it was actually caused by a complex interaction between the WT GNS and the TDS GTNxi 750. The TDS developer has provided a new version of his software (1.0.3.3), which can be downloaded from the TDS GPS Manager immediately.
Thank you for your patience. Please share this solution with anyone on the MSFS Official Forums or Discord who has been having this problem since SU14.
Thank you!
Nick C. -
Hi Nick
I'm having the same autopilot problems but I have never owned the TDS GTNxi 750. So not sure what is happening there
-
Same here, no TDS GTNxi
-
I was afraid you guys might say that. I knew I was jinxing myself by saying "AUTOPILOT FIXED" too. Since this is almost certainly new behavior with SU14, yet when I rolled back changes to the GNS 530, the problem persisted, it's possible that it's another conflict, just not with the TDS GTN 750. Do you guys have the PMS50 GTN installed? Perhaps you haven't updated it in a while, and it used to suffer from the same problem?
I have many more troubleshooting ideas we could try, but I won't bombard you with them until you indicate that you're willing to help. Usually this is something I would do in direct contact with someone through tech support, but I've been trying to post here more regularly.
Thank you for the patience!
Nick C. -
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
