Autopilot After SIM Update 14
-
@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.
-
Thanks so much... My A36 Bonanza panel was broken... I could not even move the left GPS options switch and my GPS was missing. Now it is back!
-
I'm glad it's working for you guys. Sorry I didn't look into this problem myself even sooner. Trust me, it doesn't benefit me to have broken autopilots in any way, so I'm looking forward to an official fix from Working Title just as much as you are.
-
@Black-Square
Thank you for the code. Look like it fixed the AP. Working now. Thanks again...and wishing you a Happy and prosper New year. -
@Black-Square can you please give me a little description of where we would change the code
-
From my post above:
Search for "Update loop for the main screen", and replace the existing update function with the following:
This function should begin on line 22326 of WT530B.js, if you have the exact same version as I do.
Still waiting to hear back from WT, everyone... I'll let you know when I hear something. This timing with the holidays has been very unfortunate, I think.
-
Small remark. I can confirm that his modifcation definitely works for the BSq TBM 850. All AP problems were solved after replacing the two files. The downside is that the tablet of the A2A no longer works after doing so. Putting the original WT530B.js and WT430B.js back made the A2A tablet work again.
So make sure you store both the original and the modified files, so that you can use the appropriate ones for the plane you want to fly at that time. -
@Black-Square Hello Nick, Thanks for the continuous support.
Does this also have effect on the state saving?
It does not seem to work currently with SU14.
I always close off MSFS by returning to the main menu and then exiting, but fuel state and avionics selection are still reset to default.Kind Regards, Andre
-
@Black-Square the saving grace is how wonderful it is to fly ๐๐
-
I cannot imagine how that one line edit could affect the A2A tablet. Anything is possible with software, but I suggest that it is extremely unlikely.
No, this should have no impact on state saving. I have also noticed no change in state saving behavior since SU14, nor has any been reported to technical support. Trust me, I would love a magic bullet for state saving, as well. I have no idea why the Asobo recommended approach works so poorly for some users. For the record, it's not that the state does not get saved, it's that the saved variables get detected as valid, but load all zeros.
I am moving many of the most important features over to a different state saving technique that I have found more reliable for the Dukes. If it works well there, I will move over to that system for all aircraft. The TBM already uses this method for some features, which should make it slightly more reliable than my older aircraft.
-
@Black-Square said in Autopilot After SIM Update 14:
I cannot imagine how that one line edit could affect the A2A tablet. Anything is possible with software, but I suggest that it is extremely unlikely.
I just tested it. Made the changes in the 530/430 files and jumped into my Comanche. No problems with the Tablet. Neither with or without active 530/430.
EDIT: And just tried out the TBM and the AP is working as intended again.
-
Thank you for sharing. I hesitate to much such a strong declaration without testing it myself, but as I've become more knowledgeable about the WT GNS while making some of my own improvements, and that line really should not cause any external problems like that. Thank you.
-
I really do not know what is going on, but on my system the tablet of the Comanche definitely does not work if I replace the two WT GNS 530/430 files, while the other aircraft are just fine. By putting back the unmodified files the Comance tablet again works. I realize that it will be pretty difficult to figure out what is going on, since hardware/software configurations differ.
-
I modified the original files again by just replacing the lines between update () { and the last } of the respective block. I guess this did the trick since my problems with the A2A Comanche tablet have been solved, while the AP of the TBM 850 now also works as it should.
Thanks again for helping out and my apologies for the confusion I added. -
Hello - per my earlier message ( I think on the MSFS forum), the change does not seem to have fixed the Caravan for me. I did a flight yesterday and still found that with the 530/430 selected, Nav was not working properly. There was no course deviation line on the HUD, and the AP did not correctly capture the course. When I switched out the Garmin GNS 530 and put in just the nav radio, everything worked fine. The only add-ins that were in place when I tested were FSUIPC and Better Bravo lights.
As before, other planes were working correctly with the 530/430.I'll go back and made sure I made the edit correctly to the GNS files.
Perhaps you could post the revised files to take editing mistakes out of the loop? -
Here's my report for the Bonanza/Baron:
I had the issue that the aircraft almost never loaded with the configuration I wanted (GNS530/KX155) but kept loading with the GTN750/GNS430 config. Before anyone asks - I of course shut down the sim via main menu - quit to desktop every time.
After switching in flight, the avionics never worked.
- after entering a FPL in the 530, no DTK/DST was indicated
- CDI did not show any deviation
- AP only worked in roll/pitch hold mode
Firstly, i still had an old WT GNS mod in my content (v1.1.4) which I deleted. After that, it still didn't work, though. The aircraft still frequently loaded with 750/430 and didn't work after switching.
Then, I changed the code as described above. After that, the aircraft loaded 8/10 times with the desired 530/155 config, and even when it started with 750/430, it worked after switching.
So, the code change must have done the trick for me. I'm just afraid it will be overwritten with the next sim update (and I won't remember this one anymore ;-)
Out of interest: Where is the aircraft configuration stored? Wouldn't it have been easier (and safer) just to offer the different configs as variants instead of hot swapping? I mean, who switches the avionics in-flight?
And as a side note: I don't own the A2A Comanche, but afaik it also uses the WT 530/430. And with this, editing the code for it very well can have an effect on the A2A. I think the whole thing has to to with the hot swap function BKSQ built into the aircraft. It does not show for every user, by far not, only for some of us, as in so many other cases.
Boris