I don't know if this is a bug, but...

[maxter]

... this strange occurrence has now happened twice to me.

Usually, for all my MSFS flights, at the end of each flight, I save the situation to a .flt file, to which I have a shortcut on my desktop. This
way, when I click on the shortcut, I immediately go to the aircraft where I left it last.

This has really worked out well for FSp as each flight is a natural progression of the last one, especially as I am only using GA aircraft.

Now here is the problem...

Twice now, I have saved the situation files at airports after which I have upgraded the scenery which have included those airports... and
both times, after starting up MSFS FSp has lost it's configuration, selected company and all other changes that I have made to the
defaults.

Resetting these has taken only a few minutes, but it has been annoying anyway. Each time, the scenery changes has regenerated the
scenery file indexes at startup of MSFS which may have something to do with it.

Any ideas Dan???

[maxter]

Ummmm... anyone else get the the "reset to default config bug/problem/issue"???

[DanSteph]

mhhh sorry no idea yet... perhaps posting the log.txt from
FsPassengers folder when this happen ?

Dan

[maxter]

DanSteph wrote:
mhhh sorry no idea yet... perhaps posting the log.txt from
FsPassengers folder when this happen ?

Dan

OK, thanks Dan, will do, hopefully not a next time...

[NeilC]

I get this problem as well.

I didn't realise it was connected to the scenery library. I also save the situation at the end of every flight, and then when I start FS9 it starts
with that flight all loaded up as I left it (apart from the time, which starts with system time). This seems to work very well with FSP.

I also occasionally get the problem where FSP resets to default, it involves reselecting active company and changing all the preferences
back to the way I like it.

I have not changed any scenery, but I will keep a look out next time it does it, and see if FS mentions updating scenery as it loads.

I thought that it had something to do with closing down FS with the aircraft in another place other than the one it then reloads?