1.2.3 DSMS Loadout problem after editing mission

[Geskes]

Today I noticed the following:

 

I had created a mission with a specific loadout which I flew a couple of times. Then I decided to change the loadout in the mission editor on the player a-10 to one of the default loadouts which has 4xGBU-10 and 2xAGM-65K.

 

It shows OK in external view but the DSMS has a different loadout on mission load. Screenshots attached.

 

The loadout shown on the DSMS is actually my wingmans loadout and is the loadout I had on my plane upon first creating the mission. Changing my loadout in the editor again doesnt fix it, I will have the selected loadout on my plane but the DSMS still shows another loadout.

 

I can reproduce it by loading attached mission, but not by creating a new mission and choosing that same loadout or by flying and then editing it, changing the loadout, saving and reflying. So somehow the mission attached got corrupted.

 

Nothing game-breaking here but I decided to report this anyways because potentially it could be an annoying problem if one edits missions and its loadouts occasionally.

 

Edit: I would like to add that in the attached mission, reloading the DSMS does not load the correct loadout. After reloading the incorrect loadout will still be displayed.

a10attackwarehouse.miz

Edited March 1, 2013 by Geskes

[SmokeyTheLung]

Did you use the prepare mission function?

 

Once you do, the DSMS will be "locked" so to speak. AFAIK the only way to fix the issue is to unzip the mission and edit some code (unfortunately I'm not sure what to edit)

[Ghanja]

- rename your mission from *.miz to *.zip

- go inside of this file and delete the DSMS-folder

- rename your mission back to *.miz

 

After that it should be back to "normal" in the mission

[Hamblue]

I postd a similar issue. Did an Alt ' loadout. When I did a second loadout I used one of the standard ones. It ignored the standard loadout and re-did the ealier Alt ' custom one.

At least someone recognized yours. Mine was brushed over.

[Geskes]

Yes I did use prepare mission, it was a miss-click but I did use it.

 

Also, Ghanja, thx for the tip on deleting DSMS section in the mission file.

 

 

 

Did you use the prepare mission function?

 

Once you do, the DSMS will be "locked" so to speak. AFAIK the only way to fix the issue is to unzip the mission and edit some code (unfortunately I'm not sure what to edit)