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.

AFAIK there is something done at SU5 that should fix it, or at least partly fix it. I guess we are close enough to the release of SU5 to wait and see. Assuming there will be no short hotfix from BS. That might not work after the release. Just my 2ct EDIT: and BTW for me it does not work with the Bonanza, Baron or Caravan. So copy something from them to the Caravan would not solve it for me. Assuming there is even a difference in code, what I doubt.

@Black-Square That fixes both use cases, thank you.

I'm going to take a guess that @Black-Square has way too much on his plate to fix this, so... I am willing to pitch in to find a solution. Does anyone know where to start in the config file?

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.

I have "Repaired Engine" and Health is 100%. The Chip Detector is illuminated in the enunciator panel and it appears RED on the tablet engine diagram. I do not have any 3rd party binding software.

@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.

Agh, that section of code was just a mess, so I rewrote it. There was little code left from the Analog Caravan, but that was some of it. Should be all better now. Thanks.

In the 1997 revision of the Caravan I POH that I based my work on, I have the standard empty weight of Cargomasters S/N 208B0179-208B0381 and associated STC's at 4,040 lbs, including the cargopod. Of course, all aircraft have different equipment installed from the factory, and have many modifications over the years that impact empty weight, but perhaps this came from a confusion over the inclusion of the cargopod, which weighs around 150 lbs. Would you like me to adopt this new 4,040 lbs number? I will promise not to refer anyone who complains about the loss of 115 lbs useful load to you

This is something inherent to how I implement my turbine engine simulation on top of the native engine simulation. I've briefly entertained adding a compensation for time acceleration in my code, but I'm not actually sure it would behave the same on every computer, since I think it has more to do with the simulation polling rate than the time acceleration itself. In the meantime, this effect should not be limited only the fuel flow, but the entire engine simulation, so adjusting the power lever position at your desired time acceleration should yield correct performance and fuel burn results.

That one is on Asobo, but I appreciate the continued reports, and I've added them all to my ongoing list of fixes.