investigating P-51D bundled missions containing Config (snap views), tracks, etc...

[virgo47]

I randomly chose an Instant action mission and was puzzled by the snap views that were not mine... so I went to look into the mission files. It seems that from all the missions, three Instant action missions contain Config with snap views, tracks and other unwanted stuff.

The affected files that should be cleaned up:

QuickStart/P-5125 - Caucasus - Train Strafe.miz
QuickStart/P-5130 - Caucasus -Train Strafe.miz
QuickStart/P51D-IA-Caucasus-Low Level Hell.miz

[Insonia]

The tracks, settings are for the mission intro/cinemas. Snapview sometimes used for adjusting cinemas view. or the developer just forget. 

 

Edited February 3, 2024 by Insonia

[virgo47]

OK, I don't know about tracks usage, thanks for the additional info - but embedded snapviews make player's snap views useless (just like forgotten ones), which is probably not good.

[virgo47]

3 hours ago, Insonia said:

The tracks, settings are for the mission intro/cinemas.

I check the thread and I don't believe this is the case. The mission starts immediately. I'd say these are forgotten tracks that can be cleaned.

Edited February 3, 2024 by virgo47

[virgo47]

I've bought P-47 and Spitfire, and they also have missions with similar issues with the included SnapViews, so this is probably some copy/paste problem also between modules:

In Mods/aircraft:

$ for i in */Missions/*/*.miz; do unzip -l "$i" | grep -iq SnapViews.lua && echo $i ; done
FA-18C/Missions/QuickStart/IA-FA-18C-Syria-Gauntlet.miz
Flaming Cliffs/Missions/Campaigns/CWW-Outro.miz
P-47D-30/Missions/QuickStart/P-47D - Caucasus -Train Strafe.miz
P-47D-30/Missions/QuickStart/P47D-IA-Caucasus-Low Level Hell.miz
P-51D/Missions/QuickStart/P-5125 - Caucasus - Train Strafe.miz
P-51D/Missions/QuickStart/P-5130 - Caucasus -Train Strafe.miz
P-51D/Missions/QuickStart/P51D-IA-Caucasus-Low Level Hell.miz
SpitfireLFMkIX/Missions/QuickStart/Spitfire - Caucasus - Train Strafe.miz
SpitfireLFMkIX/Missions/QuickStart/Spitfire(CW) - Caucasus -Train Strafe.miz
SpitfireLFMkIX/Missions/QuickStart/SPITFIRE-IA-Caucasus-Low Level Hell.miz

I can repeat the report under those module sections, but I'll wait after this is acknowledged (or explained) first.

[NineLine]

I'll investigate, thanks. 

[virgo47]

It seems this was remedied to some degree. I don't have all modules, but the current output from the command above is much shorter:

F-16C/Missions/Training/Lesson 20 - AGM-65 Maverick.miz
M-2000C/Missions/Training/M2K Training 04 FINAL ILS.miz
Su-25A/Missions/Campaigns/CWW-Outro.miz

I'm not sure about F-16C and M-2000C, whether the missions were updated, if I don't own the plane and just trialled it in the past. They seem to be as the date on the F-16C mission is 2025-03-19, so it's quite up to date.

In any case, it's much better - as for P-51D, it's actually fixed. Maybe the command above can be run occasionally as some part of testing process by someone having all the modules:

for i in */Missions/*/*.miz; do unzip -l "$i" | grep -iq SnapViews.lua && echo $i ; done

BTW: this uses bash from Windows Git, not cmd.

In any case, I thank you for the fixes.

Edited 6 hours ago by virgo47

[TheBiggerBass]

vor 23 Minuten schrieb virgo47:

for i in */Missions/*/*.miz; do unzip -l "$i" | grep -iq SnapViews.lua && echo $i ; done

If put into a shell file does it delete all SnapView.luas from all missions in a directory?

[virgo47]

5 minutes ago, TheBiggerBass said:

If put into a shell file does it delete all SnapView.luas from all missions in a directory?

EDIT: I forgot to point out this uses bash from Git for Windows, it's not a cmd command.

No, that command merely detects the missions that have SnapViews anywhere in the mission (but that will likely be under Config/View). In most case the whole Config folder from inside the *.miz file can go away (my experience, of course, somebody more qualified can clarify or point out exceptions).

Don't do this for the missions in the DCS installation directory - instead, copy the mission into your Missions (under Saved Games), fix it there and leave the default one be. It would be overridden by the next update anyway. So just play your fixed mission instead of the one from the training.

Edited 6 hours ago by virgo47

[TheBiggerBass]

Ok. I was just hoping for some kind of automated repair because I have nearly all modules and hundreds of missions. Too much to fix them all manually.

btw: I meant the windows .ps1 command line files with shell file.