"Snapviews not saving" Update 2, not bug. Snapviews embedded in miz file (delete Config inside miz file to fix)

[-0303-]

Update 2, not bug, Snapviews embedded in miz file, see reply #3 Rudel

Update, file corrupted again, see next post below.

 

Apparently miz file can be corrupted to only show the default snapviews.

 

Manifests as: Snapviews saves and works while in mission but next spawn, back to default snapviews. But, saving snapviews while inside corrupted miz file mission does show up on running non-corrupt miz file mission or running multiplayer. So bug seems restricted to inside specific corrupted miz file.

 

I (vaguely) remembered it was the miz file years ago. Then, I nuked Saved Games folder. Not this time, just deleted corrupt miz file. Time will tell if this is it. Attached corrupted miz file (single Mig-29 on ramp). Test: Save snapviews, Quit, respawn and notice default snapviews.

 

Same thing may have happened to other player, "Snap View doesnt saves"

Obviously ensured clean install, fresh Saved Games folder (to which I imported old corrupted miz file for testing).

Created "miz file" tag (will/would create "lua file" and "trk file" tags given opportunity).

corrupt Caucasus.miz

 

Very rare bug. Except maybe if someone built a large miz file without previous version backups and have to chuck all of it.Still rare though.

 

~

 

 

Going crazy with tagging: created "trk file" in old topic (deleted/replaced "attached track", indicates trk file attached or discussed). Will probably create "lua file" tag in old topic. Systematic symmetry trk miz lua...

Edited February 8, 2021 by -0303-

[-0303-]

.... and it happened again.

 

I had chucked my old "corrupt" miz file and created a new one. And now again, snapviews doesn't stick after new spawn on my new miz file either.

(Note, neither miz file were anything special, just a small file with a dozen different plane spawns to experiment with takeoffs landings, wind conditions etc ...)

 

I really don't want to redo the entire SAVED GAMES folder but it seems I'll have too after all, to get rid of this bug wherever it is.

 

Snapviews saves but does NOT show while in my newly created replacement miz file.

Snapviews DOES save and show when I go online multiplayer.

 

Last attempt. Created caucasus3.miz (after caucasus.miz & caucasus2.miz quickly went corrupt). Seems snapviews are saving again. For how long? Why does two files corrupts within weeks when it last it happened was ~1.5 years ago? Unless something is corrupt outside just the miz file. ~1.5 years ago I chucked all of SAVED GAMES.

 

Attached file, not purged to single plane (unlike above).

 

 

corrupt Caucasus2.miz

 

Noticed it starts a replay if "opened". Disregard, load mission in started game, spawn any plane and try to save snapviews.

Edited February 3, 2021 by -0303-

[-0303-]

... and snapviews doesn't stick offline again.  miz file #3 corrupts.

Created caucasus4.miz that works but for how long?

I give up. Delete Saved Games and start over.

Edited February 7, 2021 by -0303-

[Rudel_chw]

The mission is not corrupted.

 

The issue is that whoever first created the mission, placed in there a specific view configuration .. so your in-flight changes get saved on your /Saved Games/Config/ Folder, not on the mission's.

 

 

The solution is to use WinRar or similar tool to delete the Config folder that is within the MIZ file. While you are at it, delete also those Track files, to make it smaller.

[-0303-]

Thanks Rudel,

Happily I didn't delete, just renamed Saved Games (was going to harvest snapviews settings).

 

I deleted Config and Track folders (using "7-zip"). Seems to have worked.  I know a very similar if not identical problem exists for some Instant Action missions (separate snapviews saved with the mission causing trouble). Maybe I should have remembered that.

 

I don't fully get it yet, but I expect it'll get into focus ... eventually. *I* created all the files. What I don't get is at what point did it decide to place default snapviews in the miz file? When I save miz file in Mission Editor to go to flight mode? It seem to pattern with "new" planes I hadn't flow before or not in a long while (meaning I had not done any snapview saving before saving miz file).

~~~

 

Wonder more folders / files I can delete to save space (Track_data?) mission, theatre, options, scripts sounds like required files. Files that exist (after deleting Config and Track folders):

Quote

corrupt Caucasus.miz

07/02/2021  16:37    <DIR>          l10n
07/02/2021  16:30           176,530 mission
07/02/2021  16:30             9,898 options
07/02/2021  16:37    <DIR>          Scripts
07/02/2021  16:30                 8 theatre
07/02/2021  16:37    <DIR>          track_data
07/02/2021  16:30            27,832 warehouses

 

 

Edited February 7, 2021 by -0303-

[Rudel_chw]

3 minutes ago, -0303- said:

*I* created all the files.

 

Strange .. those Track folders are usually the result of converting a Multiplayer Track file (that you get after playing online on a server) into a MIZ file. I used to do that a lot, back before I got fed up with MP, to practice the MP missions on Single Player (so that no one got to kill me while I was learning/practicing)

[-0303-]

So ... happened twice again. I wish I knew what action causes "now I'm gonna save default snapviews and only these will be usable for the mission". So I used 7-zip twice again to remove the config and track  (and track_data).

 

Why is it happening so frequently now when I haven't encountered it for literally more than a year?

 

I can see the point of customized snapviews for specific miz files (kind of, but NOT arguing for any resources spent on this). But then they should be editable.  I only ever seen the default views, so what's the point? And how do you create them?

Edited February 9, 2021 by -0303-

[Rudel_chw]

14 hours ago, -0303- said:

Why is it happening so frequently now when I haven't encountered it for literally more than a year?

 

 

The missions are your own and edited from scratch? .. or are you starting by modifying a previous mission?  ... in the latter case, check the mission that you used as base ... most likely it has those Folders and so you ar replicating the problem whenever you edit a new mission based on it.

[-0303-]

Always from scratch. For that reason, from scratch to avoid copying "bugs".

 

They're very simple. I set spawns for a dozen different planes, experimenting with takeoffs, landings, winds and weather. Would be a real pain if I actually tried to do big missions.

 

[Rudel_chw]

1 hour ago, -0303- said:

Always from scratch. For that reason, from scratch to avoid copying "bugs".

 

I’m afraid that I don’t know what may be causing this, perhaps a config option that I don’t know about. Let’s do a test:

 

- rename your /saved games/dcs/ folder, say to dcs.bak

- run dcs, it will create a new default folder. It will ask for your login credentials.

- dont play or try to config, exit DCS once it has shown its main menu.

- using windows, copy (not move) the /dcs.bak/config/ folder from your backup pnto the new /saved games/dcs/ folder, to recover your basic dcs config.

- run dcs again, it should look like your previous version.

 

test the Editor again, does the problem persist?

[-0303-]

Painfully remove bit by bit until finding what it is ... Yikes. Know the routine though. Maybe I'll try something next time.

 

A question that seem more fruitful. Embedding snapviews is a feature (supposedly). Someone somewhere knows how to trigger it, should have documented it. How to avoid it.

 

 

Edited February 10, 2021 by -0303-