Autopilot After SIM Update 14
-
@jmarkows said in Autopilot After SIM Update 14:
What issues are you having with the Caravan? Check this topic:
I've been participating in this thread already, so my problems are already explained in my early posts here.
EDIT: Just reviewed the thread you linked and that is very encouraging. Didn't realize there were more solutions beyond what is above.
However, I am STILL quite confused about the WT mods in Content Manager. There is one that is larger (MBs) and one small one (a few KB). I understood one was the actual code change and one was just a pointer for planes that weren't updated to use the WT code. I'd appreciate it if someone can confirm which of those should be in place.
-
One of them is the actual avionics incorporated in SU11. That's the one without a thumbnail. The one with the color picture of the GNS units is the pointer mod for aircraft that haven't been updated to call them natively.
Until they're updated, you need it for the Black Square aircraft, and this is called out in the manuals for them. There's quite the brouhaha in the MSFS forums rightnow about the fact that nobody seems to really know what they do and don't do.
As I (and end user who has learned a little fighting with various aircraft that need it) understand it, it's a very simple change to point things calling for the original Asobo avionics to the new WT avionics. In theory, that shouldn't affect anything else, but it can and does "break" stuff when called because the avionics also contain/handle the autopilot. The new WT autopilot works very different from the original Asobo stuff, so things coded to use different features or send different events may not work or may work funky.
-
@ultradianguy said in Autopilot After SIM Update 14:
I'd appreciate it if someone can confirm which of those should be in place.
You need both.
-
@Bert-Pieke So this is helpful, although when I originally reached out to Justflight support - before they raised the ticket with BS directly - they told me the opposite. So I hope everyone will get on the same page about this.
And then also clarify which of the additional code edits are needed to fix all the issues - I've seen in other threads that BS has suggested changes to the 530/430 files, the KAP140 files, and systems.cfg.
-
@ultradianguy said in Autopilot After SIM Update 14:
So I hope everyone will get on the same page about this.
Things change... it is the nature of the beast.
-
@Bert-Pieke Of course - I understand that. In this case, the instructions to resolve this specific issue - same ticket - have been contradictory. Some of that is likely due to evolving debugging. But some of it is insufficient communication between JF and -in this case - the BS dev.
We're all human and fixing my sim experience is hardly the most important thing in life - but also I've spent a lot of my own time on resolving issues with a commercial product. I backed off on using it altogether because I just couldn't justify that amount of time for fixing something that shouldn't be my job. So I'm just asking the players to communicate with each other and then provide a comprehensive and consistent message in one place that doesn't require hunting through posts in one or more threads. No blame, no unkind words. I don't think that's unreasonable.
-
@ultradianguy said in Autopilot After SIM Update 14:
I don't think that's unreasonable.
I do not think you are being unreasonable at all, and I understand your frustration.
Personally, I am just happy that the developer is engaged and quick to jump in when problems arise.. Other aircraft, I have had to park, waiting for the "update" to make its way through the system.. -
I could probably post this in numerous topics on this forum right now, but I will also add that you will no longer need the extra WT package from the in-game marketplace if you make one small change to just the Caravan's PANEL.CFG. If you change these two lines...
htmlgauge00=NavSystems/GPS/AS530/AS530.html, 0, 0, 320,234 htmlgauge00=NavSystems/GPS/AS430/AS430.html, 0, 0, 350, 190To these two lines...
htmlgauge00=NavSystems/GPS/WT530/WT530.html, 0, 0, 320,234 htmlgauge00=NavSystems/GPS/WT430/WT430.html, 0, 0, 350, 190That's essentially all that WT package is doing. It's redirecting calls to the original Asobo 530/430 to the new WT 530/430.
-
@Black-Square said in Autopilot After SIM Update 14:
I could probably post this in numerous topics on this forum right now, but I will also add that you will no longer need the extra WT package from the in-game marketplace if you make one small change to just the Caravan's PANEL.CFG. If you change these two lines...
Thanks much and thanks for all the communication. Any chance of gathering all the needed edits in one place ? I think we're up to 5 files that need revision now to resolve all these issues:
- GNS 530
- GNS 430
- KAP 140
- Systems.cfg
- Panel.cfg
-
Systems.cfg, and GNS 530 are actually the only two that need medication for a functioning aircraft. The others are just to improve your experience.
As I've mentioned several times in this thread already, the reason I have not offered a mod to make the autopilot fix specifically, is that there are so many "fixes", "tweaks", and "compatibility mods" out there, all of which overwrite the GPS/autopilot completely, that tech support already struggles to diagnose existing problems caused by these community created modifications. They are all created with the best intentions, but a quick fix for one aircraft quickly becomes outdated and wreaks havoc for years after it has served its purpose. You can imagine why I am not too keen on creating yet another one of these packages for something that will be fixed by Working Title as soon as possible.
-
Great news - I went ahead and made all the suggested changes discussed in the above 5 files, including the Flight Director edit and the 4 functions in KAP140. I just took a short flight and so far, everything seems to be working! It was not a comprehensive test, but I was able to switch to the GNS in both positions and then successfully set altitude hold, VS armed and captured a new altitude, NAV with both GPS and VLOC. I manually steered the aircraft in the direction of a track that was way off and when it got near, it captured it beautifully. CDI on both the analog HSI and the HUD were correct. All functions cleared when I turned off AP.
Hopefully this will hold next time I fly but so far, it checks out 100%. I'd forgotten what a nice plane it was because of all the frustration. Thank you @Black-Square for all the assistance.
-
Oh - one question - is there any chance of mods for the regular Caravan affecting the BS Analog version? I know it's a different plane, but it seems there are more interactions than I would have expected so I wanted to check. Tonight's flight was without any mods to the default Caravan. I don't normally fly the G1000 version - but I put the mods in because there are bushtrips and other content that use the default Caravan.
-
So glad it's working for you. Every time there is cause for me to go back and fly the Caravan, I'm reminded of how much I enjoy it. With those changes, I don't think you should see any of your issues return. This is not always the case with software, but those were very definitive fixes when I found them.
The only potential interaction between the default Caravan and mine should be the sounds. I recall a few reports from tech support of users with the mod installed hearing the fuel cutoff warning buzzer in one or the other aircraft when they shouldn't have been, but I haven't heard any reports of that in a long time. If you do have any issues, let me know, because they are all easily fixed.
-
Sounds good. Thanks again for the stellar support Nick (and for the impressive debugging!) Both Ian at JF and you have been terrific.
I do think for the benefit of others it would be helpful to collect all the suggested edits in one place - even if it's just a single post in one of these threads. You could label the critical vs optional ones. That's your call of course. Anyway, hope to not be bugging you again for a while. ;) -
@ultradianguy I'm working on it. We'll hopefully have this up as a FAQ as soon as I've actually come up with some wording that makes it understandable without all the surrounding context from these threads.
@jmarkows primarily, but this may also help other people: Quick note from the other thread about your comment reference line numbering; I always recommend that people use Notepad++ for edits such as these (https://notepad-plus-plus.org/) - it's free, recognises many types of code by default and provides colouring and other feedback to show where there are problems in code if you make any mistakes. It also doesn't add command codes, null spaces and other things which Wordpad has an annoying tendency to do.
-
Hi! Is there an update coming out anytime soon with these changes? If so, I'll wait because I'd rather not make any mistakes trying to do it myself.
-
We can't modify WT's code and so we'll have to await SU15 coming out before we can sort a permanent fix.
X-Plane users will be used to living in a constant state of flux with their sim, but it's a relatively new experience for Microsoft pilots and developers. -
This post is deleted!
-
So WT on discord said that they have fixed a number of things for upcoming SU 15 including GNS autopilot problems. If we made changes in the WT530B.js should we we revert back to the original WT530B.js before the update comes out with SU 15? Or will the update just install a new WT530B.js ? Thanks
-
Great question. I installed the update this morning, and the update manager overwrote the files, meaning that no further user action should be necessary. I found that the update did fix the problem, so if you are still having problems after the update, try renaming/removing/deleting the WT530B.js altogether. This will cause the update manager to download the latest version for certain.
Thank you, everyone, for waiting while Working Title sorted this out. Unfortunately, they did not have the resources to incorporate any of my numerous other fixes and improvements for the GNS that I supplied them with in SU15, but there is hope for the next sim update. I will keep you all posted.
