Yes, if I do save a flight, it does create that file. But I’m still able to choose a different flight from new without loading a saved one. Right now, I have no saved flights (there’s too many problems with these right now so I’ll wait until Asobo works out these bugs).
For now, I just manually pick my flights.
So when you delete that saved flight, you are able to pick another airport and aircraft? If you choose not to save it, the next flight are you able to pick a different airport and aircraft? Basically, this how I’m doing it as I’m not saving flights anymore. (OK, that sounded wordy!)
Exactly, the problem is the .fssave file, or the way the game creates it. When I end a flight, the game automatically saves the flight under a .fssave file. The next time I start any other flight, the game will automatically load that file that it saved itself, even though I specifically command it to load a new and different flight.
I submitted the bug through Zendesk, I hope they solve it.
thanks guys for sharing the workaround to delete .fssave files - that works. And I guess it should be possible for Zendesk to solve that issue - it’s quite clear what happens…
A temporary fix I just figured out is to delete the 4files.
User/name/AppData/Local/Packages/Microsoft.FlightSimulator_8wekyb3d8bbwe/LocalState/MISSIONS/Custom/CustomFlight/
Interesting. Asobo needs to look into that.
You (and others here) should keep updating your ticket with zendesk that the problem still exists. You can edit your zendesk ticket to push it back to Asobo.
