Caravan Autopilot - won't disarm?
-
I changed absolutely nothing, I just started the sim up again and did the exact same thing, and this time it worked. Maybe I broke something by not giving the avionics a bit to spin up (since I loaded in mid air), but without changing a damn thing it's now working great. Panel goes blank when I disengage the AP and it doesn't reengage on me.
I might try reverting the flight director change with the KAP140 changes and see if it ending all AP modes fixes the original problem when I have more time, just for hahas.
Thanks so much for the help, so happy we got it sorted!
I do have something else with the Caravan that could use some looking at with the audio panel, but that's a quality of life thing and doesn't really hamper the experience. I'll write it up as another topic.
-
@Black-Square Just for kicks, I changed the flight_director variable in the systems.cfg back to 0 to see if your KAP140 changes canceling all modes when disengaged also fixed the AP auto-engagement. It does not; it will revert to ROL and PIT anyway and come back on.
Maybe worth discussing with the WT folks to see why that silly-sounding change makes such a difference, but good catch and thanks for coming up with it to try.
-
Thanks for trying that out. I thought about telling you that I fully expected it to go back to misbehaving without that change, but I thought I didn't want to seem like a know-it-all. Thanks again for helping me find that issue. I will certainly be looking through their code more and mention it to them soon. Unfortunately, I think things are still a little backed up over there after the holidays. I'm just glad you have a fully functioning Caravan now! I hope you have some time to enjoy flying it. It's still one of my favorites, though it seems the curse of an aircraft developer is that I only get to enjoy my aircraft when they're broken or unfinished!
-
I will! I haven't flown an airliner for my VA in a few months now; as I said elsewhere I've been flying our winter tour in the TBM, but I might switch a few legs to the Caravan now!
Any idea when you'll push these changes (along with anything else you have up your sleeve) live? Or are the Dukes coming first and then a polish pass on everything else?
-
I'm glad you're enjoying it! That's probably what it's going to be, yes. I have a lot of smaller changes that I've brought from my newer aircraft into the older ones, but I also want to do a major update for the TBM. Sorry I can't give anything more specific than that. I hope you'll let me know if there is anything else I can help you with in the meantime, though!
-
Just the comm panel and vPilot!
For a wishlist I think the only thing I'd really like is native integration of the WT avionics in your line instead of using the Marketplace mod to point to them. Maybe for the Caravan it won't really make a difference since the KAP140 is so simple, but for example we talked in the Go Around thread about how the GA button doesn't work in the TBM with the 530 since WT changed how it handles all that compared to the old Asobo one. Maybe that's part of your upcoming plans, as I think you mentioned it is integrated into the Dukes.
If flying time were no object, I'd run out and buy the whole Steam Gauge collection right now, but I'm definitely going to go take a much closer look at either the Baron or King Air and grab a Duke when it releases.
-
I'm on it! I've already made the GNS 530 change for all my aircraft on my side. It's literally only adding a couple characters to the panel.cfg. What take a little more effort is integrating the "WTT Mode" modification offered by PMS50 for their GTN 750. I've done that for the Dukes too, but that only matters to dedicated users of the PMS50 ecosystem.
The King Air is certainly its own beast, but the Dukes will be so superior to my other products upon release, I think that buying the bundle with piston and turboprop versions would satisfy me for almost endless hours of flying. I hope you enjoy whichever of my products you choose to fly!
-
I stumbled on this in the main MSFS forums. I've talked with Les before about it in other places, which is where most of my limited knowledge of what the optional WT mod does for planes.
Just in case you find it useful:
https://forums.flightsimulator.com/t/the-kap-140-autopilot-will-not-work-more-than-once-per-flight/625924/14 -
Hello - I am now utterly confused about what changes are needed to make the BS Caravan AP work correctly with the GNS avionics. I had given up on flying it altogether after trying suggested changes to the GNS code. @jmarkows pointed me here which I much appreciate. But I'm unclear which of the many suggested above were confirmed as a solution.
I've seen the original changes to the 530 and 430 files, possible changes to the KAP140 js, and also a change in systems.cfg. As well as keeping or not keeping the WT content manager mods.
@Black-Square can you please provide a single, comprehensive set of instructions in one place for the needed changes to fix the issues? My experience seems to be quite similar to that of @jmarkows .
-
@ultradianguy said in Caravan Autopilot - won't disarm?:
Hello - I am now utterly confused about what changes are needed to make the BS Caravan AP work correctly with the GNS avionics. I had given up on flying it altogether after trying suggested changes to the GNS code. @jmarkows pointed me here which I much appreciate. But I'm unclear which of the many suggested above were confirmed as a solution.
I've seen the original changes to the 530 and 430 files, possible changes to the KAP140 js, and also a change in systems.cfg. As well as keeping or not keeping the WT content manager mods.
@Black-Square can you please provide a single, comprehensive set of instructions in one place for the needed changes to fix the issues? My experience seems to be quite similar to that of @jmarkows .
- You DO need the marketplace mod installed. Without it, the plane calls the original Asobo GNS units and autopilot and things like NAV won't capture and follow
- You DO need to set "flight_director_available" to 1 in the systems.cfg in the Analog Caravan folder
- You do NOT need to make the change to the KAP140.js file; the AP shouldn't display any modes when disconnected, and that code change fixes that, but it's not critical to the fix so you can wait if you don't want to make that change yourself.
- You do NOT need to make changes to the WT530.js and WT430.js to fix the hot swapping issue with the latest WT avionics, but an official fix is likely not coming until SU15 and you run the risk of the AP not working if the state saving doesn't load you into something with the 530/430 already set. I DO recommend you make this fix.
They're not complicated fixes and all that's required is some copy and pasting. You should make a copy of the original file before making the changes, that way you can easily go back if you don't do it right.
-
Thanks - not worried about making the edits - no big deal - just wasn't clear on which were determined to be helpful.
The way people are discussing this is a bit confusing - as saying that the WT avionics are now incorporated into the core sim implies (to me) that no addin is needed in Content Manager. (In my mind, anything I see in Content Manager is not Core - but maybe that's just mistaken).
Anyway, regarding bullet 1 above - there are two GNS files listed in CM - a bigger one with no thumbnail and a smaller one with a thumbnail. I'm understanding the most recent replies to mean BOTH should be loaded.
Confirm?
(And thank you) -
@ultradianguy said in Caravan Autopilot - won't disarm?:
Thanks - not worried about making the edits - no big deal - just wasn't clear on which were determined to be helpful.
The way people are discussing this is a bit confusing - as saying that the WT avionics are now incorporated into the core sim implies (to me) that no addin is needed in Content Manager. (In my mind, anything I see in Content Manager is not Core - but maybe that's just mistaken).
Anyway, regarding bullet 1 above - there are two GNS files listed in CM - a bigger one with no thumbnail and a smaller one with a thumbnail. I'm understanding the most recent replies to mean BOTH should be loaded.
Confirm?
(And thank you)Confirmed, yes. The one without the thumbnail is the core avionics and to my knowledge actually can't be uninstalled. The one with the color thumbnail is the pointer, which can be removed, but you want it installed.
Just to give you a warning to something that tripped me up making the KAP140 edits, Black Square gives four lines that the provided code snipped needs to go after: those are functions and that should be the first line in each function. My first attempt, I misread it as putting it after the block of four functions, and that bricked my avionics. The rest are super simple.
-
@jmarkows Ah, thank you. So I'm adding the same code snippet as the first line of each of those 4 functions?
I usually do this sort of thing in notepad++ which will recognize the file as js and give me some indication where a block begins and ends. Not a full-fledged development environment but helpful.
-
@ultradianguy Correct.
I think a little below that are snippets from my file and Black Squares that should illustrate it a little better, as I said my first attempt didn't go quite right 😂
-
Cool, thanks. (Tried to just like your response but I guess you can't do that here?)
-
Thank you for your post, @jmarkows. That's exactly the current situation. Sorry that this reminds so confusing right now.
I heard through yet another grapevine yesterday that Working Title will not address this until SU15, which is rather upsetting to me and my support team, as you might imagine. I'm sure that it's not by choice, though. Despite the ability to make instantaneous changes at no cost, software development can still be a slow moving machine.
-
-
@Black-Square I think one or more of these fixes might have had unintended consequences.
I noticed flying the Caravan this morning that the AP will now adjust the held altitude based on the cockpit altimeter and not its own. I was holding at 7000ft with a setting of 30.23 (or so, the Kollsman window is impossible to read), when I pulled a local altimeter of 29.94 and adjusted the cockpit one first.
The plane began climbing back to 7000ft as soon as I touched the altimeter but the KAP140 was still set up 30.23. Adjusting that had no effect, but I did discover that playing with the KAP140 Baro setting is still doing something under the hood because you will get all Alt warning beep if you set it differently enough; about .3 in either direction, which IIRC is roughly 300ft.
-
I suspect that's because the Working Title autopilot is missing some features of the native one. For example, it has no bank angle limiter. I added this in my modifications I sent them, so hopefully it will be added in SU15. The KAP140 is my only autopilot with a separate barometer, so I'm not surprised I haven't noticed, given that the Caravan was released well before the WT GNS. I'll take a look next time I have the sim running and see if I can spot a mistake or improve their code.
