Why are view settings being saved as part of the mission file?

[Lixma 06]

It's infuriating.

 

You set up your cockpit snap-views just right - and then you load a mission you made a couple of days ago and you're back to square one.

 

Is there a reason for this?

Edited October 9, 2018 by Lixma 06

[MadDog-IC]

That only happens if you use the "Prepare mission" option of the Mission Editor, either don't use it or open the mission file with a zip file editor and delete the config folder from within.

[Lixma 06]

I've never used the prepare mission option, I've no idea what that is.

[Eldur]

Came here from https://forums.eagle.ru/showthread.php?t=222064&page=6

 

Now I get why my custom snap views would never save for longer than the actual session

 

Might have been that I tried the mission planning thing once becaue I thought I could set up new waypoints there to Viggen in style. Apart from that I never use that function, simply because it seems to be totally useless to me... but even more so I don't get why the settings are then saved in the miz when entering that planning thing

 

Glad I didn't open a bug report 'cos of that already since I was going to do so...

[virgo47]

I've just spent around hour of hunting this strange behaviour, why it happens, it wasn't easy to google the right keywords, but here I'm after all, removing Config from the mission file helped and I'm fine.

But I definitely consider this a bug! Why would a mission creator force his custom snapviews upon me? That doesn't make any sense at all.

While we're at it - I see two clearly snap-view related files in the Config/View directory, the other two (Server and View) - are these fine to delete as well? Is there any possible added value in Config/View in the mission file or is it just a misfortunate mission editor behaviour?

[BIGNEWY]

It usually happens if a track replay has been converted to a mission and the track and the view folder are not removed from the archive