Thanks for the comment. Indeed, I've already done the work for all my other aircraft. There is actually yet another step I could take to make the flares really bright (hyper-realistic, shall we call it) during the day, but this would take much more work, so I wanted to see what my users thought of this change first. I think the results are definitely acceptable now, and anymore would be (probably less realistic) eye-candy.

Hey Nick, same as the guy above me, I'm using the WT GNS 530/430 combo and I'm seeing the KAP140 baro setting having no effect and the main altimeter setting controlling the AP. Currently flying the Cargomaster in MSFS 2024, Caravan v1.1. Edit: removing the ping, as based on the comment re: WT update cycle I suspect you're aware of this. I thought it worked in the Analog Caravan in 2020 though? I was using WT avionics back then, as well.

I tried a full reinstall of all variants, and had thought for a moment that it had worked. However, it's back to it's original ways. I've been mostly flying the amphib, and it's a coin toss as to whether I will have to re-select my control profiles. Not an issue on any other BS aircraft.

@Mustang I just checked the model and the configurations, and the correct thrust centerline distance should be 6.8ft, whereas it's currently 6.0ft. It's not a holdover from the piston engines, which have the same centerlines, so I'm not sure where that came from. I've fixed it for the next version, but I suspect the change in performance will be pretty minimal. You're welcome to test it yourself. Look for the Engine.0, and Engine.1 lines near the top of the engines.cfg, and replace them with the following lines: Engine.0 = 6.9, -6.8, 0.7 Engine.1 = 6.9, 6.8, 0.7

@Galf Do you have v1.1 of the Caravan? There was an issue in v1.0 that prevented those items from saving, but only for the Cargomaster.

@scanham That's a very interesting combination of things. Looking at the code, both cannot be true at the same time. The red chip detector on the tablet visualizer and the engine health bar read the exact same variable in the same block of code, and depend on no other variables. Can you provide some screenshots or video to help troubleshoot this? A picture is always worth a thousand words.

@ksmith Wonderful! Thanks for the feedback. Let me know if there's anything else I can do for you guys!

@Black-Square Sorry about that one - for some reason I thought real taxiways changed the pavement markers too. Here's another one today: CYHZ Runway 32/14 - all of the signs say 23-05. Runway 23-05 is correctly marked. Let me know if you want me to continue to tag you on these - or just post and let you get to them when you can.

Yup, that works for the 650, but not for the 750 which was what was confusing me.

+1, sounds like a really cool improvement idea.

@RPGamerous I mean yeah, I agree, especially that it would technically be the only variant with an actual 3d cockpit differences. As I said, I don't believe it would ever take any priority over the steam gauge variants - but it would be definitely a super cool backlog item reserved for whenever Nick has time in between the major releases

If you actually have the Bonanza Professional (the newest version), there is a dedicated MSFS 2024 installer similar to how the TBM850 has one (and you should use it rather than copying the 2020 version over). If you actually have the Bonanza Overhaul, then no it doesn't work in 2024 without a lot of massaging and maybe not even then.

Ah ok... I tried CTRL C very quickly and could see the tablet trying to change the GPS, but it still ended up back at the default 650/750.

We should hear soon about more upcoming projects. @Voice-of-Reason said there is a big update article they're about to publish, once Nick puts some finishing touches on it.

Interesting, it was happening repeatedly to me, and after several startup and shutdown cycles since I had done a few flights without going back to the menu. Notes I should have included in my first post: using the Cargomaster, MSFS 2024 SU4 release, and yes the tablet to manually trigger the failure. I had thought it would be in an area using common code across variants, but I did not actually test that. Is there anything I can do to help troubleshoot it? The first time I triggered the failure was actually the longest it took to happen; I had a few seconds to play with the throttle and see there was no engine response, and right around when I moved the emergency lever was when it died. I had thought I had done something wrong until I noticed both fuel tanks were at zero. Subsequent failures of the FCU produced quicker, but not quite immediate results. Sometimes it would instantly zero, on at least one occasion I saw the tanks empty in a few discrete steps.

@FlightEngineer1 yes, I'm aware of ai.cfg. I have used this to enable and tune (to an extent) autopilots in planes that don't have them natively, with mixed success but usually well enough to pass muster. This often also entails adding an autopilot electrical circuit to systems.cfg, and checking engines.cfg (why there?) to make sure that the param DisableAutopilotControls=0; sometimes a dev will explicitly set it to 1 and then no autopilot. Maybe I'm just old and slightly bitter at this point, but I have no faith that Asobo will ever address this, are aware of it, or even know what they're doing in this regard. There are core algorithm parameters that were REQUIRED when I was doing industrial process control PIDs, which are utterly absent here. Which brings into question the form of the equation they are using. They're never going to expose the maths, and I have better things to do.

@CousinHubert said in Lost SAVE button: Thanks to you all ... NB that if you ever need assistance or encounter problems with any product developed, published or sold by Just Flight or Just Trains, your best bet is always to contact Support. https://community.justflight.com/topic/2/product-support

Sadly, my CTDs are back. I've tried several combinations of video driver version (always after running display driver uninstaller), emptying my community folder, clearing the rolling cache, reinstalling msfs, etc. and it always crashes after ~15 minutes, sometimes earlier. Wondering if SU4 issues (e.g. cockpit persistence problems) are causing stability issues. CoherentGTJS.dll is often the culprit, which makes me suspect javascript conflicts. I'm using Beyond ATC in VR through the toolbar, which is dependent on javascript reliability.