Duke B60T does not retain previous flight states

npoulis

Hi there,

I have noticed that the B60T (not sure about the other) does not keep the state of the previous flight.
That means that everything returns to default values when you reenter the simulator.
For example, it does not keep:

Pilot and passenger weights, empty or not.
Fuel quantity.
Cargo quantity.
Cabin altitude dial.
Cabin temperature dial setting.
Switches, any kind.
Any kind of door open or closed.

I have the impression that at least some of the above were kept between sessions.
Beyond that the Duke is flying beautifully and is enjoyable as it was.

Nick.

bobsk8

I just started a new flight this afternoon, and when I ended my flight this morning I left the doors open, and new flight, doors are still open.

Sunake

Some of the stuff isn't retained. For example I have both tds and pms gtn addons. It always defaults to using the tds when I set it to use pms.

rjwalter

Even worse for me. I do a free flight with the duke selected. Next time I fly it shows the previous aircraft as the default selected. I then have to select the duke and update the control options every time I want to fly the duke. Rinse and repeat.

Not sure whats going on here.

konstantin

I have the same thing on Xbox. I can't fly because I'm not sure if the resource of the plane is preserved..

chrisjk24

Has this been address by black square? I am having the same issues. HOBBS and state of aircraft do not save, and the same as rjwalter - when I reload MSFS it doesn't show livery I flew last like it does with other aircraft (including the grand and normal duke)

Black Square

I've discussed this in a few places, but I guess not this thread yet. For non-avionics related state saving, I use the recommended Asobo technique for saving variables. I have devote a large amount of time over the years in attempts to figure out what this just does not work for select users. Some have had success by disabling virus checkers, but no solution for others. Notably, the two items mentioned lastly here, the liveries, and the Hobbs time, I have absolutely nothing to do with. This corroborates my belief that the problem is on a broader level within the simulator, and not with anything specific that I'm doing or not doing. Trust me, I wish I had a solution too, because there are a lot more features I would add if I had more consistent state saving for all users!

Mustang

@Black-Square said in Duke B60T does not retain previous flight states:

Trust me, I wish I had a solution too, because there are a lot more features I would add if I had more consistent state saving for all users!

Sounds like it might be time to consider dropping the 'Asobo technique' since it seems potentially broken. I've no idea how easy that would be to do on top of all the other awesome stuff you do, and I'm sure it's already crossed your mind... but thought I'd come and state the bleeding obvious regardless!

While I haven't touched it in a couple of years now, I heard that DCS is starting to get aircraft persistence which is really interesting too, and will bring more meaning to the startup procedures etc. there too. Simming just keeps getting better every year!

Black Square

Unfortunately, the Asobo technique is the only technique available to me without switching to WASM, which I have no intention of doing for numerous reasons (the reason that might matter most to my users is the greater possibility of CTD and performance degradation with WASM). The reason I use different techniques for avionics versus systems is because the avionics technique takes longer to load after the flight is loaded (waits until you press "ready to fly"), which can sometimes interfere with the flight loading sequence. I felt a little vindicated about this (not in a good way) when MSFS 2024 completely confused the flight loading sequence for all my aircraft. Luckily, this I have been able to resolve with some time consuming workarounds for my next updates.

Avionic

For the ones where it goes back to previously flown plane and doesn't save instrument etc. it is 90 % certain due to a cloud save error. SU4 introduces a popup warning users about this, but of course it shouldn't be breaking in the first place, and it is a PITA to set up controls etc all over or import one by one if you use the built in controls after a reset.

Here is how you reset - but do read the warnings about what it deletes. https://flightsimulator.zendesk.com/hc/en-us/articles/17060350083612-How-to-delete-a-cloud-save-to-fix-some-loading-or-crashing-issues-Crashing-on-the-identity-screen-spawning-inside-buildings

The thread about the new popup for it making many users realise they had this problem (including me) in su4 beta is here.

https://forums.flightsimulator.com/t/cloud-save-error-error-code-1047-and-now-2047/738971

Also seems like some people have problems with the cloud save even after deletion now. In my case, it fixed things - broke again 7 days later, and has now stayed working for a while after another cloud deletion.

Mustang

I appreciate the reply, Nick. Interesting to see some of the things you have to contend with behind the scenes. I can imagine how frustrating it must be. In my own daily work I'm regularly frustrated when things don't quite work correctly due to bad configurations or bugs/'features' that few are interested to fix.

To Avionic's post, I have had to contend with the cloud save corruption in 2024 too, and had to reset my cloud save completely. For me, it manifested itself with SU3's release. The game would freeze within a few seconds of reaching the main menu, so the game was unusuable. Nothing fixed it until I gave up and did the cloud save reset. I still haven't fully rebuilt my controller bindings since (but I don't use 2024 much). It often prompts me to save a new profile after editing a binding, even when I'm editing an already-customised profile. So it's getting messy with duplicate/triplicate versions of profiles with a (1) and (2) suffix. Confusing. But I digress!