Steam Gauge Overhaul

[image: a4fef8af-601e-463d-b061-203ef7c1fdf6.JPG]

@Black-Square THANKS for your response and usual pro-attitude regarding researching and fixing things up Nick! That's why Black Square is so good!

I have the exact same issue. I'm not sure whether it is caused by the aircraft or the GTN750 software. Additionally I'm having quite a lot of CTDs.

Noticed that it does in fact cycle off and then back on but when testing earlier didn't see it happening like when using the mouse to click the toggle switch. Tried to edit but time limited to when we can edit a previous post.

Hello fosl I mapped a button to "AUTO THROTTLE TO GA" in MSFS Options, and it works well.

I haven’t tried that yet, but I will see what I can do. Thanks for trying.

+1 here. Using the pms50, which works beautifully, but the 430 doesn’t sync up so it’s not much use. Fantastic plane otherwise though…

It worked. I was surprised to discover that this code will control the OBS in all modes, NAV, GPS, and RNAV. You just get the independent setting of the OBS when you switch between RNAV and normal modes (unlike the other Black Square aircraft). Now I have to test to make sure it doesn't lose the sync with any of the modes.

@Black-Square I've learned a great deal about aviation generally by way of flying your Caravan from Florida all the all over to Scotland where I am now in FSEconomy, I look forward to any future updates/fixes/improvements forthcoming for this aircraft. Even with SU15 and all your various suggested workarounds in previous threads, there still seem to be a few minor AP gremlins: AP screen remains lit when powered off(intended behavior?), some issues with under or overshooting altitudes, but nothing major. That's really the only thing I can think to complain about, and as I said its minor, not game-breaking. Seems to be something about the interaction between the PMS50 GTN750, the WT "layer"(do I even need the Marketplace WT thing now?), and the KAP140 code of the sim itself.

Update... False alarm.. a PC reboot seems to have solved the problem..

Feedback from PMS50: Usually, set the AP approach mode when flying the FAF leg and make sure to be at the published altitude at the FAF could make it to correctly catch the GP at the FAF. I usually try to capture the GS / GP further out (great example would be the LONG approach step downs at major airports such as Detroit Metro) and let the AP ride it down. But as I'm now flying some aircraft with the GTN750, this surprised me when I could not capture as soon as I was established on the final apch crs. Learn something every day.

Yes. The aircraft needs an ai.cfg file, and you need to update layout.json to add that file. Just needs a patch to address the bug, or a DIY mod in the meantime.

[image: 4005f828-e5d8-4943-9c9d-000d15ed1acb.jpg]

@Black-Square Yes I did, as mentioned in https://community.justflight.com/topic/5864/caravan-autopilot-won-t-disarm/19

At least you figured out a fix, and it's not too bad, just a cut and paste. But something you shouldn't have to do. Still, MSFS is amazing for all its warts.

In my BKSQ Caravan using PMS50 GTN750 (latest version as of the time of this post) with the extra WTT-package 1.0.7 for AP/flight plan installed. A few updates ago, PMS50 stated that the WT-layer had a major update. Ever since then the AP remains lit when disabled. (i.e. ROL mode shown, etc.) However, the AP is not engaged in roll or pitch, just that some of the lights on the KAP140 display and the AP annunciator panel remain lit. I do have the systems.cfg and KAP140.js changes applied. Before the aforementioned PMS50 update and with your recommended bug-workarounds, the AP worked most of the time flawlessly, including no lights when disabled. It appears to just be a visual problem, AP works as expected (some bugs perhaps occasionally with weird altitude tracking overshoots still but that's another issue). I'm still on SU14, maybe SU15 will change something.

@Black-Square It works kind of... The values are not updating properly. I can fiddle with the deicing stuff and despite the cockpit gen load needles are moving, the values are not updating every time. They updating a bit random. It would be cool if the propagated variables would simply reflect the needle position. So a FIP analog gauge would get alle the smooth movement and stickiness like the real needle. And even on the digital gauge, it would be cool to see the values rise and fall and not jump. [image: ce1dcaf4-f92e-4dd4-b375-74d3803a2f94.png]

@hangar_101, I do have a published snippet for the Bravo and Analog Baron. The ID number to look it up in Spad is 10854. It's my only published snippet so far but has the autopilot settings I posted above.

Thanks so much for your response and my sincere apologies for only seeing it now! I was not expecting you to come back so quickly and must have not set up notifications! Really appreciate you confirming the above! Love your products and the King Air especially. Really is beautifully done!