DAWS Save Mission

[Gaanalma]

The mod include MIST 4.0.55 if I remember correctly..

 

Mod include MIST 3.7.53

 

I'm testing on 1.5 and 1.2.16.... In 1.2.16 dont'go.

 

I change MIST version in common\code folder and it seems to be OK! :thumbup:

[chromium]

yes if you need to update mist you simply have to change the file in the common\code folder. My current test build have 4.0.55, but there shouldn't be any difference for this mod.

 

I have a working 1.2.16 version (the one I used last months), but I can't provide support with that. Is anyone effectively interested?

[Gaanalma]

THHX Chrom!

 

I recived e-mail!

 

For 1.2.16 I'm using for a little internal test campaign... We have not yet migrated on 1.5, our main activity still relies on 1.2.16.

 

See you soon!

[chromium]

Good. I'm not that sure to post here the 1.2.16 version, cause I could not provide enough support in case of errors :(.

 

I think that 1.5 and EDGE's version of DCS are the present and the future of this sim, even if still bugged in some way... therefore I'm focusing on this vesions of the mods (And I have a lot of things to convert... all the other DAWS modules need adjustment or rewriting due to the new mission file structure and modifications to the mission editor).

[Gaanalma]

of course, it's logical and accommodating ... hope the 1.5 or 2 are stable and bug free for multyplaier activity as soon as possible

[Pikey]

Hmm, can't find any autosave (on 1.5), it saves a dawssavedmission_12345etc file in the missions folder of the profile, when you manually press save, but nothing automated. Where should it go?

 

Also - I presume there is some manual operation to copy the mission and warehouse out fo that .miz and into your next mission launch? Is that supposed to be automated? No instructions on the dummy.miz or its purpose either. Coulds use some more pointers please! :) For example are you supposed to put your original mission into the same folder of the dummy.miz instead?

[Pikey]

OK, it needs the dummy.miz. But the name is hardcoded. Are we supposed to rename the original misison to dummy.miz? I'd like to get an idea of the data flow here.

[chromium]

Dummy.miz should be inside the package. I'll check.

 

EDIT:

 

the file is here:

AMVI\SaveMission\

 

I need your log to understand what is going on...

Edited October 18, 2015 by chromium

[chromium]

Also - I presume there is some manual operation to copy the mission and warehouse out fo that .miz and into your next mission launch? Is that supposed to be automated?

 

Yes it should be automated: mission and warehouse files are found in the app\temp directory. mission is overwritten, warehouse is copied. options also should be copied but I found issues with it.

 

No instructions on the dummy.miz or its purpose either. Coulds use some more pointers please! :)

 

You shouldn't need any instruction on dummy.miz, cause it's simply a "void" container used as a base for the saved mission file. What do you mean by "pointers"?

 

For example are you supposed to put your original mission into the same folder of the dummy.miz instead?

 

No, you can load and use any miz file in any location, but the saved one will be placed always in your Saved Games\DCS.Openbeta\mission directory.

 

Given your questions, I think that something is going wrong in your case. Can you please send the dcs.log? also, if as I understood you could look whitout problem into the lua files, please activate debug log before sending me the log. To do that, you must simply open the DAWS_saveMission.lua, look for debugProcess variable (line 69) and make it "true".

Edited October 18, 2015 by chromium

[Pikey]

Hi, i'll produce some logs Monday night. Just to be clear, it is only working if I manually save the mission using the F10 menuitem, there is no automatic save. I also have to take the mission and warehouse files out of the saved mission and put them into the original mission and run that. You say that should be automated. I wonder if it is a permisisons thing...will see.

[chromium]

You should be able ti open the saved file, it's a miz file. You should simply rename it as You need.

 

I didn't found any similar issue... so i really need Your logs :)

[Pikey]

Can't see any reference to any auto saving but it ran the manual save 4 times when I asked, ran it for 20 mins. no sign of the completed mission being made, just the warewhouse and mission files in those miz.

dcs.log.txt

[chromium]

The first strange things is that loading process seems to run twice, once after 156 secs and another one after almost 20 minutes!, like someone loaded DAWS Save Mission.lua after mission start.

 

Also I don't know if medevac script could modify something.

 

Can you please send me your original miz file and the saved one to try to understand what is going on?.

[Pikey]

Emailed you due to size :)

[Pikey]

OK god, now its workign but crashing my game when I take a slot! log is no clue again!

[chromium]

OK god, now its workign but crashing my game when I take a slot! log is no clue again!

 

As the log showed Save Mission two times, the second after 20 mins (strange), and some of the complexity informations that you gave to me, I think that the issue could be mission or hardware related. Anyway I'll try to look at this ASAP with the mission you send me.

 

Maybe one interesting question could be about files attached to the mission, like audio files. I don't know how those could react, probably those informations won't be kept in the saved file. I'll try to understand this, and if effectively attached files aren't kept in the new saved mission archive I will try to address this.

[chromium]

I think that the issue could be mission or hardware related.

 

And I was wrong.

I believe that the main issue regard the fact that l10n folder, which contain all the mission files, isn't copied and stored inside the saved mission. Therefore, I will look about how to move that folder in place.

 

In the meantime it seems that only mission that does not load other script and that does not contain audio or external files will work as intended.

 

I will update you as soon s possibile.

[chromium]

ok, a little update. DCS do different things when an SP mission or a MP mission is loaded. And Save Mission is ok with that.

 

An SP mission create a temporary copy of the mission file... which is what Save Mission could look at. With that, It means that the l10n directory will be kept.

 

But MP mission creates multiple temporary files: you will recognize a mission and a warehouse file in those... and Save Mission use them to retrieve the warehouse file. The bad thing is that l10n don't seems to be unpacked anywhere.

 

The best solution would obviously be to find a way to retrieve the last loaded mission path... that way, all the issues should disappear. I believe that this info is stored somewhere (surely in the ME scripts, but I don't want a solution that force any host to open the ME before launching the mission... to load a mission and/or save it again), I think that I may find a solution in the MP code.

 

Tomorroe I will go holiday till monday :), so any suggestion will be good... but for updates I need time and as said before is the only thing that I don't have that much in those weeks :).

[chromium]

Small update. Given your feedback, those are the variables that will be available in the lua file for customization:

 

local CreateStatics 			= true -- If this is set to "true", for each dead vehicle/airplane/helicopter a corresponding dead static object will be spawned in the theatre.
local HiddenStatics 			= true -- If this is set to "true", the spawned static objects will be set as hidden to declutter the mission editor.
local MaxTimeFileCheckHours 	= 72 -- when in multiplayer mission the Save function will only work whithin this limit of hour from the server start. After, it will give an error.
local KeepContinousMission		= false -- if true it will set the saved mission start time at the saving command minute
local UpdateSceneryDate 		= true -- if true it will add "1" day at each mission save. Works ONLY IF KeepContinousMission is FALSE!!!
local NightMission 				= false -- if set "false", it will prevent to set up mission in evening and night hours.
local theMessageState			= true -- if set "true", it will print out any save mission messages (autosave doesn't print anything)
local MapObjectPersitence		= true -- if set "true", it will enable the map object persistence mod (BUGGED!)
local RadioMenuVariable			= true -- if set "true", it will enable the save command by F10 radio menu. If "off", the save function shall be called by script DAWSoncallworkflow()
local KeepGroupsRoutes			= true -- if set "true", the mod won't delete group routes while saving
local AutoSaveEnable 			= true -- if set "true", the mod will execute the autosave function.
local AutoSaveFileName			= "DAWS_AutoSave.miz" -- this will be the name of the autosaved miz

 

I'm currently facing an issue highlighted by Pikey. I'm looking for a way to identify the loaded mission path... if I won't find a solution in a reasonable time, The mod will work only if the loaded miz file has a particoular filename and if it's placed in the default mission folder.

 

In the meantime, I'm testing how those variable works... and I'll try to alterate time to find few hours to update the small pdf manual. Spock, Kirk, Vader and Luke are helping me at the moment.

[chromium]

I found a solution, that is more like a workaround but it works as expected. I still need time to test it by myself and to update the manual with a much comprehensive description about the above listed variables. :)

 

Pikey, I already tested your full-of-files mission and it works as expected.

[eric963]

Sounds Great!! Can't wait to try it out.

 

Eric

[ESAc_matador]

Its time to test the mod!

[chromium]

Not yet, give me At least few days more before releasung the update.

[chromium]

In the meantime that I'm completing some test and the new manual, I got time to add a simple but maybe useful additional feature.

 

By changing a variable in lua, now you can also remove downed planes/helos if they got downed. If an entire flight is downed, it will be removed from the saved mission.

 

As I believe that those variables may be a very important features, if I got more time I will evaluate the possibility to add a menù in the mission editor to check/uncheck variables startng from DCSW 2.0.

[Pikey]

Definitely useful. One of the problems with persistence is if something activates DAWS didn't touch these.

 

Unfortunately due to the state of DCS 1.5 we have rolled back to 1.2, I'm not testing it anymore, it's just too painful and frustrating to try.

 

In the meantime that I'm completing some test and the new manual, I got time to add a simple but maybe useful additional feature.

 

By changing a variable in lua, now you can also remove downed planes/helos if they got downed. If an entire flight is downed, it will be removed from the saved mission.

 

As I believe that those variables may be a very important features, if I got more time I will evaluate the possibility to add a menù in the mission editor to check/uncheck variables startng from DCSW 2.0.