Snaps views resetting

[ac5]

Snaps views resetting, especially with the Corsair and Marianas WWII,

often after a Training mission. but also with other airplanes, especially Marianas modern.

Anybody?

[MAXsenna]

On 8/3/2025 at 3:24 PM, ac5 said:

Snaps views resetting, especially with the Corsair and Marianas WWII,

often after a Training mission. but also with other airplanes, especially Marianas modern.

Anybody?

Snapviews for maps doesn't exist, so I might misunderstand you. To reset for any flyable module, open your Snapviews.lua in Notepad++, find the module and delete its section. To reset everything, just delete the file. 

Cheers! 

[ac5]

23 hours ago, MAXsenna said:

Snapviews for maps doesn't exist, so I might misunderstand you. To reset for any flyable module, open your Snapviews.lua in Notepad++, find the module and delete its section. To reset everything, just delete the file. 

Cheers! 

I did not make myself clear... I am well aware that "Snapviews for maps" doesn't exist,

what I was trying to convey was that my saved snapviews sometimes get erased / resettet / 

reverted to defaults without any intervention from my part. 

Again: this issue happens sometimes with the Corsair and Marianas WWII,

often after a Training mission. but also with other airplanes, especially on the Marianas modern map.

I did not notice this issue on other maps. Hope so it is clear what I mean....

Anybody having also this issue?

[MAXsenna]

15 minutes ago, ac5 said:

I did not make myself clear... I am well aware that "Snapviews for maps" doesn't exist,
what I was trying to convey was that my saved snapviews sometimes get erased / resettet / 
reverted to defaults without any intervention from my part. 
Again: this issue happens sometimes with the Corsair and Marianas WWII,
often after a Training mission. but also with other airplanes, especially on the Marianas modern map.
I did not notice this issue on other maps. Hope so it is clear what I mean....
Anybody having also this issue?

Aaaahh! I completely misunderstood! (Interpreted it as question, my bad).

Make a copy before you start DCS, and check the file creation date/time if somehow the file gets deleted. Or file change date/time to see when the file gets changed.
Never heard if this issue before to be honest.

Sent from my SM-A536B using Tapatalk
 

Edited August 5 by MAXsenna

[ac5]

On 8/5/2025 at 6:12 PM, MAXsenna said:

Aaaahh! I completely misunderstood! (Interpreted it as question, my bad).

Make a copy before you start DCS, and check the file creation date/time if somehow the file gets deleted. Or file change date/time to see when the file gets changed.
Never heard if this issue before to be honest.

Sent from my SM-A536B using Tapatalk
 

Thanks.. Yes, I always make a copy, and the file SnapViews.lua is anyway always in my file history.

But this does not explain WHY my saved snapviews sometimes get erased / resettet / 
reverted to defaults without any intervention from my part. 

Does really nobody else have this issue? By all means I am not inventing it,

and I am neither a computer newbie or a DCS one......

[MAXsenna]

2 minutes ago, ac5 said:

But this does not explain WHY my saved snapviews sometimes get erased / resettet / 
reverted to defaults without any intervention from my part. 

Of course, absolutely not! I wasn't clear it seems. I left out the important parts. If you can find out exactly when it happens, like starting DCS, starting a mission etc. Then you can provide that to the devs, and they might be able to find out why. 

I have heard about others losing their controls settings, not snapviews. 

Oh, and BTW. The "Save snapviews" checkbox in the settings haven't been unchecked by chance? 

Cheers! 

[virgo47]

Are you sure it is resetting - or is it actually not right in particular missions? Because missions can be done in such a way they remember snap-views. It is mostly unintended, but it's easy to create such missions, and even some ED's missions for their modules had these snap-views baked in.

That is... create your mission with just a plane and try it. Does it use your snap views? If so, then they are not lost, just overridden by the other mission.

Edited August 6 by virgo47

[MAXsenna]

Are you sure it is resetting - or is it actually not right in particular missions? Because missions can be done in such a way they remember snap-views. It is mostly unintended, but it's easy to create such missions, and even some ED's missions for their modules had these snap-views baked in.
That is... create your mission with just a plane and try it. Does it use your snap views? If so, then they are not lost, just overridden by the other mission.

That's also true!

Sent from my SM-A536B using Tapatalk

[ac5]

Hi thank you all for your comments.

Yes, MAXsenna the "Save snapviews" checkbox in the settings is checked.

Well, virgo47, even if missions can be done in such a way they remember snap-views,

all of my missions are made by me, except the tutorials, so if they are made by me,

those missions should keep my Snap views, even if said mission set in a way that remember snap-views...

Let's say I play a mission I made. After finishing it, I do a Training mission, complete it

Then I load the very same mission, and often my Snap views are gone, mostly the zoom level of

the default front view.....  Go figure....

 

 

[virgo47]

1 hour ago, ac5 said:

Hi thank you all for your comments.

Yes, MAXsenna the "Save snapviews" checkbox in the settings is checked.

Well, virgo47, even if missions can be done in such a way they remember snap-views,

all of my missions are made by me, except the tutorials, so if they are made by me,

those missions should keep my Snap views, even if said mission set in a way that remember snap-views...

Let's say I play a mission I made. After finishing it, I do a Training mission, complete it

Then I load the very same mission, and often my Snap views are gone, mostly the zoom level of

the default front view.....  Go figure....

Just to be absolutely sure - what works and what does not? Because there was a problem with the default zoom (the zoom after the mission starts, that is the zoom for the default view). This is just another problem, although it has been fixed in the meantime...

Can you at least tell us what is happening with your Saved Games\<DCS>\Config\View\SnapViews.lua file? Does it change when you notice the unexpected behavior? That is - back it up and then compare it (use some kind of diff tool).

Also, does it happen with any other plane? Does it happen on any other map with the same plane? This may be plane-related. In SW anything is possible, so it may be even map-related, but I doubt this one.

To hunt it down, you have to go analytical.

[MAXsenna]

Hi thank you all for your comments.
Yes, MAXsenna the "Save snapviews" checkbox in the settings is checked.
Well, virgo47, even if missions can be done in such a way they remember snap-views,
all of my missions are made by me, except the tutorials, so if they are made by me,
those missions should keep my Snap views, even if said mission set in a way that remember snap-views...
Let's say I play a mission I made. After finishing it, I do a Training mission, complete it
Then I load the very same mission, and often my Snap views are gone, mostly the zoom level of
the default front view.....  Go figure....
 
 

Bummer! I was really hoping we were getting somewhere.

Sent from my SM-A536B using Tapatalk

[Art-J]

I've never played some of the default instant missions for P-47 because they override my snap-viewed personal FoV settings. I've read it's beacuse of some leftover file ED put in these missions. Now, If I play my own mission afterwards, i expect the game properly loading my own view settings and for Thunderbolt it does.

That being said, I remember when for a few years we needed to load D-25 and D-30 Mustang missions in correct order to avoid loosing all custom controls, same for clipped and non-clipped Spitfire. I'm glad this bug was fixed eventually. Maybe ac5 discovered a new but similar issue which doesn't go away unless game is restarted?

I do use snap-view customized FoV in my Corsair and I haven't yet experienced missions resetting it to default even though I switch between training and my own ones multiple times. The only time it happened to me was when I switched from American Corsair to British MkIV one, because the latter uses separate camera settings and thus I had to separately customize it as well.

Edited August 8 by Art-J

[ac5]

Hi all, that's the rub...

And yes, virgo 47, it happen with also with any other planes. Although in the case of other planes "DCS" just zooms out the default view

but does not touch the other saved snap views. Much worse with the Corsair, there "DCS" not "just" zooms out the default view,

but it also messes up ALL the other saved snap views! And yes, it happens also on other maps with the same planes, but far less than in

the Marianas maps, both modern and WWII. See screenshots with written on explanations. I also include the Missions.

 

Corsair-Complete-02.miz MIG-19-Complete-Marianas.miz

[MAXsenna]

43 minutes ago, Art-J said:

I've never played some of the default instant missions for P-47 because they override my snap-viewed personal FoV settings. I've read it's beacuse of some leftover file ED put in these missions.

Correct. Easy to fix. Open the miz in 7zip and delete the "snapview/view" folder or similar. Save the file and you have your own snapviews. 

I don't remember why they're saved in the first place.  

@ac5 I just noticed you've posted it in the Marianas WWII forum, that's probably why there's so little traction. It should probably be moved to the view bugs forum as this cannot possibly be a map issue. 

Cheers! 

Edited August 8 by MAXsenna

[virgo47]

OK, probably multiple things are going on here, so it's hard to say what exactly is wrong:

• Corsair-Complete-02.miz is clean, no baked-in views there. The other mission has Config dir inside it, it can be completely removed (Config/View overrides your views):
  
  This happens when the mission is "prepared" in the mission editor. That is Flight / Prepare Mission (Ctrl+M). Fly Mission alone does not do this and is safe to use.
• What happens with the Corsair in the clean mission, I have no idea. I didn't understand the story related to your screenshots of the View folder, not sure what happens when and what gets wrong.

So, first step is to be always sure that the mission doesn't have baked-in views. With that, any other troubleshooting leads nowhere and just confuses you. Let's compare only clean missions.

But with the "clean" mission, I have no idea what is going on.

[ac5]

OK Guys, thank you for your patience...

Though, as wrote before, all of my missions are made by me.

So if they are made by me, those missions should keep MY Snap views,

even if said missions are saved in a way that embeds snap-views...

Then why is the default view on the Mig 15, 19 and others zoomed out?

BTW, I have never used Flight / Prepare Mission, I use always the green button “Fly mission”…..

And indeed, I agree MAXsenna, this topic should probably be moved to the view bugs forum but I could not find a way to do it.

But then again, this issue happens, as I have just extensively tested, pretty much exclusively on both Marianas maps

In the enclosed .zip a bunch of my missions, ALL of these, without exception, keep the saved Snap views AND default zoom levels!

As soon as the Marianas maps are involved, then this problems starts.

That’s why I never experienced this before installing the WWII Marianas map.

Don’t any of you REALLY experience this issue?

And of course, latest DCS version.......

Missions-OK.zip

Edited August 9 by ac5

[ac5]

I think I have found a temporary workaround to this issue, at least until 

ED notices / reads this thread and hopefully fix this issue.....

I have marked the file SnapViews.lua as "read only", and it seems to work with all my

WWII Marianas Corsair missions, and even in the training missions.

Oddly enough, the 3 miz in the included zip still present the wrong level the zoom level of the default front view,

and in spite of the as "read only" status of the SnapViews-lua I can still after a few tries change 

in that default front view the zoom level, but then other views get busted.

Well, less important, as long as the corsair missions work, those should be in the WWII Marianas map...

Again, MIG-15, 19 and Sabre on maps other than the Marianas, no issues at all... Go figure....

REALLY?  Nobody experience a similar issue?

ED? signs of life?

  

Still-Busted.zip

[virgo47]

7 minutes ago, ac5 said:

Again, MIG-15, 19 and Sabre on maps other than the Marianas, no issues at all... Go figure....

How did you get to those missions? Are these your missions? Because all the missions have baked-in views, so yes, they will NOT WORK as expected:

I started DCS, opened the Mission Editor, created a new Marianas mission, put MiG-15 there, skill Player, saved. No baked in views. Something must have happened to put them there. Try to do this minimal mission and look into the miz file. Mine looks like this:

As you can see, no Config subdir there.

I'd like to help you, or at least say "I don't know how to, problem is somewhere else", but you have to stop complaining about the mission with baked-in views. They will NOT work with your snap views.

As I said above, first things first, be SURE the mission does NOT have baked-in views. Otherwise, we're wasting everybody's time - yours included.

Then we can figure out what else is wrong. E.g. how did the config/views appeared there. Or if it's not there, what else doesn't work. Right now we haven't moved from square one. Always follow the evidence. Otherwise things get confusing.

[ac5]

22 hours ago, virgo47 said:

How did you get to those missions? Are these your missions? Because all the missions have baked-in views, so yes, they will NOT WORK as expected:

I started DCS, opened the Mission Editor, created a new Marianas mission, put MiG-15 there, skill Player, saved. No baked in views. Something must have happened to put them there. Try to do this minimal mission and look into the miz file. Mine looks like this:

As you can see, no Config subdir there.

I'd like to help you, or at least say "I don't know how to, problem is somewhere else", but you have to stop complaining about the mission with baked-in views. They will NOT work with your snap views.

As I said above, first things first, be SURE the mission does NOT have baked-in views. Otherwise, we're wasting everybody's time - yours included.

Then we can figure out what else is wrong. E.g. how did the config/views appeared there. Or if it's not there, what else doesn't work. Right now we haven't moved from square one. Always follow the evidence. Otherwise things get confusing.

Fine, forget about those missions, not important anyway. But what about that Corsair one?

No baked views in that one, as you said it yourself.

As mentioned and clearly seen in the screenshots, on this mission "DCS" not "just" zooms out the default view,

but it also messes up ALL the other saved snap views!

Again as mentioned, I never use used Flight / Prepare Mission, I use always the green button “Fly mission”…..

Still astonished by ED not showing signs of life concerning this matter.....

[TheBiggerBass]

FWIW I have the same issue with F-16C. Snapviews are reset sometimes after a training mission.

Edited August 17 by TheBiggerBass

[ac5]

32 minutes ago, TheBiggerBass said:

FWIW I have the same issue with F-16C. Snapviews are reset sometimes after a training mission.

So there you have it... I am glad I am not the only one.... 

As already mentioned, I think I have found a temporary workaround to this issue, at least until 

ED notices this thread and hopefully fix this issue.......

I have marked the file SnapViews.lua as "read only", and it seems to work with all my

missions, and even in the training missions.

Ever so astonished by ED not showing signs of life concerning this matter.....

Edited August 17 by ac5

[virgo47]

ED will not show signs of life without a reproducible use case. I said previously - there were bugs related to views, some were fixed, but there may still be more. But this thread so far was more confusing than evidence based. It's not like nobody believes there are bugs, but always try to make it easy for the guys to reproduce. Provide tracks, configs, videos, evidence.

I can't test any Corsair mission as I don't have the bird, yet I wanted to help originally with other missions you provided, but these were wrong missions (baked-in views) and your replay was "but what about"... It's jsut very difficult to help in such a case. Make the case clear, I know it's sometimes really hard, but it's close to impossible to reproduce anything based on anecdotes. These things can even be different bugs caused by different things, just manifesting in a similar manner.

ED will not waste time on a report as vague as this one. They have many more quality reports and then they have their priorities as well, so even totally obvious proven bugs are not fixed for many years. Is it Marians WWII related? Is it F-16C training mission related? Is it Corsair related (is it even ED's problem in that case)? Hunt down a concrete case and document it well.

[ac5]

22 minutes ago, virgo47 said:

ED will not show signs of life without a reproducible use case. I said previously - there were bugs related to views, some were fixed, but there may still be more. But this thread so far was more confusing than evidence based. It's not like nobody believes there are bugs, but always try to make it easy for the guys to reproduce. Provide tracks, configs, videos, evidence.

I can't test any Corsair mission as I don't have the bird, yet I wanted to help originally with other missions you provided, but these were wrong missions (baked-in views) and your replay was "but what about"... It's jsut very difficult to help in such a case. Make the case clear, I know it's sometimes really hard, but it's close to impossible to reproduce anything based on anecdotes. These things can even be different bugs caused by different things, just manifesting in a similar manner.

ED will not waste time on a report as vague as this one. They have many more quality reports and then they have their priorities as well, so even totally obvious proven bugs are not fixed for many years. Is it Marians WWII related? Is it F-16C training mission related? Is it Corsair related (is it even ED's problem in that case)? Hunt down a concrete case and document it well.

Evidence is in the screenshots above, and in the fact that The Bigger Bass also has this issue,

and with the F-16, most probably not in the Marianas map.

Moreover, why would he and me invent something? To annoy you? These are not anecdotes but hard FACTS.

Proof is since I have marked the file SnapViews.lua as "read only" I don't have this issue any more,

As this bug tries to change the SnapViews.lua does not succeed because now is "read only".....

And BTW, the corsair and the huey missions I provided do not have baked in views.

 

[virgo47]

32 minutes ago, ac5 said:

Evidence is in the screenshots above, and in the fact that The Bigger Bass also has this issue,

and with the F-16, most probably not in the Marianas map.

Moreover, why would he and me invent something? To annoy you? These are not anecdotes but hard FACTS.

I don't doubt there is a problem. I'm just saying that a screenshot is not enough. Let's say the bug goes like this - this is a hypothetical scenario:

1. I have the following snapviews (file attached to the post).
2. I load the following mission (attached in the post).
   NOTES: The mission is a minimal mission for practical reproduction - that is, a single Player-skill plane, if that is enough to replicate the issue. If it's not plane-specific, use a free Su-25T or TF-51D. Of course, if it's only with some plane or some map, use those.
3. I do this and this in a mission. (Trackfile is included in the post.)
4. I leave the mission and check my snapviews and see that the modification date was updated. I can also see the differences (tools like diff or WinMerge). And again, the modified file is attached to the post.

Now somebody can try it and say "yeah, I see it now" - or, sometimes frustratingly, but happens as well - "sorry, it works on my end". And the process can follow one way or the other. This described scenario, with all the necessary config files provided, is important even if it's not the only one where it happens for you. That's OK. The important stuff is that someone else can confirm or not, and then the hunt can continue, e.g. what are your other options, etc.

Screenshots and videos are welcome additions, but not enough.

Does the process make sense?

Edited August 17 by virgo47

[TheBiggerBass]

As an engineer I don't want to join in fruitless disputes - please forgive me. I rather spend my time snooping through the DCS software jungle. After some trials it seems the issue is not based within DCS core. The "forgotten" snapview settings only appears with certain mission files. These missions seem to ignore the snapview settings as previously stored in SnapViews.lua. Leaving these missions to and start another mission the stored snapview settings are still available. I guess these special missions are older and do not fully respect the latest DCS requirements.

This procedure is repeatable. After I found out how to store that in track file I will upload it.