DAWS Save Mission

[chromium]

Hello :)

 

I want to SAVE on demand under Trigger / Conditions, is correct Action to be used: DO SCRIPT: DAWS.oncallworkflow()

 

Is there anything to be put inside these () brackets? No information in the manual nor in this thread, I have tried searching.

 

You should simply, inside the sim, activate radio menù, then choose f10 and select save option. No ME action is required (as described in page 5). In the recent version of DCS you can't do that exept if you are in external view or in cockpit (cause you won't see the radio menù...)

 

Anyway, if you want to save in a predefined moment using a trigger you simply execute DAWS.oncallworkflow() whitout anything in the bracket suing a DO SCRIPT trigger like you said :). I like your idea to be able to save on command. I will add further instruction in the manual for mission designers so that they will be able to save when they need. Good point!

Edited May 24, 2016 by chromium

[Shaman]

Thanks a ton for clearing this out. In case of my squadron, commander asks me only to make one single save 1 minute before mission ends and then actions to open DAWS_AutoSave.miz and continue from there.

I do hope 1 minute is enough for .miz file to be saved.

 

Another question. May I limit F10 menu function for DAWS to my selection (table) of UnitNames?

[chromium]

I hope too, usually is matter of seconds.

About saving only some units and other not.. you should name every non-want-to-save unit with the exclusion tag. Don't think there is another fast methods to achieve this, sorry :(

[Shaman]

Allright, so basically it saves within one minute, cool.

Hey man, let me rephrase my other question. I was asking if from player perspective if I may limit access to DAWS script comms menu to selection of clients through UnitNames.

Thanks for your work :)

 

Sent from my Nexus 7 using Tapatalk

[Shaman]

I have just got this error message (see attached image) the moment server launched ONCE trigger, at mission time, action DO SCRIPT: DAWS.oncallworkflow()

No mission file was created inside C:/FTPVAULT/Missions/. Here's how I have configured your script:

-- DAWS_SaveMission for DCSW 1.5
local MainVersion = "1"
local SubVersion = "5"
local Build = "2191"


-- THANKS TO (cronological order):
-- Rider (AMVI)
-- Grimes (ED community)
-- MBot (ED community)
-- xcom (ED community)
-- Ian (ED community)
-- vicx (ED community)
-- Pikey (ED community)

-- USER VARIABLES
local CreateStatics 			= false -- 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 by text.
local KeepContinousMission		= true -- if true it will set the saved mission start time at the saving command minute
local UpdateSceneryDate 		= false -- if true it will add "1" day at each mission save. Works ONLY IF KeepContinousMission is FALSE!!!
local NightMission 				= true -- 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		= false -- if set "true", it will enable the map object persistence mod (BUGGED!)
local RadioMenuVariable			= false -- if set "true", it will enable the save command by F10 radio menu. If "off", the save function shall be called by script using the DAWS.oncallworkflow()
local KeepGroupsRoutes			= true -- if set "true", the mod won't delete group routes while saving
local AutoSaveEnable 			= false -- if set "true", the mod will execute the autosave function every 10 minutes.
local AutoSaveFileName			= "DAWS_AutoSave.miz" -- this will be the name of the autosaved miz
local ExcludeTag				= "Xcl_" -- using this tag as a prefix for group name will prevent those groups to be tracked by DAWS. If killed or moved, those groups won't be affected.
local AirUnitTracked			= false	-- if set "true", if a plane gets killed the plane will be removed from the saved mission. If an entire flight is killed, it will be deleted.
--local StartingFileName			= lfs.writedir() .. "Missions/" .. "DAWS_AutoSave.miz" -- THIS SHOULD BE REMOVED

 

if allowSave == true then

		--local OldMizPath = nil
		--OldMizPath = loadedMissionPath
		
		if debugProcess == true then
			env.info(("the loadedMissionPath is " .. tostring(loadedMissionPath))) 	
		end			
		
		--local NewMizPath = theAutosaveFilename or missionfilesdirectory .. "DAWS-SavedMission_" .. saveCounter .. ".miz" -- change to writedir
		local NewMizPath = "C:/FTPVAULT/Missions/"
		local NewMizTempDir = "DAWS_TempMix/"
		lfs.mkdir(missionfilesdirectory .. "Temp/" .. NewMizTempDir)
		local OldMissionPath = missionfilesdirectory .. "Temp/" .. "mission"
		local NewMissionPath = missionfilesdirectory .. "Temp/" .. NewMizTempDir .. "mission"

 

here's my local thread for this scenario if you wish to help there:

http://forum.51st.org/viewtopic.php?f=39&t=3247&p=32697#p32697

 

Thanks!

Edited May 24, 2016 by Shaman

[chromium]

I have to check better the issue, i can Friday to Monday later this week.

 

If you want to limit to some one the access to the save command, you May try to rewrite the radio menu creating code... somewhere in the Last hundreds of Lines of the lua code

 

Inviato dal mio SM-G850F utilizzando Tapatalk

[Shaman]

Would you find time to meet up on TeamSpeak maybe? Yes, on Monday I'm available and we could talk. Maybe this way we pinpoint this error bug sooner.

[chromium]

Would you find time to meet up on TeamSpeak maybe? Yes, on Monday I'm available and we could talk. Maybe this way we pinpoint this error bug sooner.

 

I might find some time but only on saturday or sunday morning, from 10:30 to 11:30 CET. Evenings are almost impossibile... daytime even less. I hope that it's ok to you.

 

About your issue, I was not able to reproduce (it will work as expected in the release version and in the test version I sent you). Line 1058 in the release version do not point anywhere... even in the test release that I sent you it not point anywhere useful with a miz variable.

 

Did you modified the lua file? If so, can you send me your DAWS_SaveMission.lua?

[chromium]

I was asking if from player perspective if I may limit access to DAWS script comms menu to selection of clients through UnitNames.

 

Not unit, but group. I added in the test version that I hope to release soon an additional option that if set true, it will create the radio menù only for a group named "DAWS_Saver". I won't let this name available for modification, unless changing it inside the lua function (current line 1336).

[chromium]

a new version has been released today and it's already downloadable from the AMVI site (see link from the first post).

 

Changelog:

- added spawned ground vehicles units & groups tracking;

- added options to limit radio menù access to a single group;

- updated manual;

[Shaman]

Can't wait to try it out. I'll be back on Tuesday and will implement newest version in scenario I am developing and keep you informed of my progress. Thanks for requested features!

 

Sent from my Nexus 7 using Tapatalk

[chromium]

Don't think that this is going to solve some of your issues... I still can't understand where is located your problem.

 

I suggest you first to try this version whitout modification. If it works as expected, then move on. If not, Let me know what behaviour you see... I will tell you how to proceed to help me track the issue.

[chromium]

a new version has been released today and it's already downloadable from the AMVI site (see link from the first post).

 

Changelog:

- added spawned ground vehicles units & groups tracking;

- added options to limit radio menù access to a single group;

- updated manual;

 

Hello everyone, due to an error by copy&paste the version that was available for download from yesterday till 5 mins ago was bugged and is not going to work anytime.

 

Please download again the mod now, the issue has been fixed.

Thanks for your patience.

[Shaman]

DAWS_Saver doesn't work, even when renamed to actual group name of single client, and I think this is due to bug in DCS with Group.getByName(..), have you tried to rewrite code by unitname instead, like CTLD does it?

 

I am now waiting for server to reach 3h time since mission start trigger, to execute save action via do script DAWS.oncallworkflow(), will then see if this really works. All I need is to have a save at 3rd hour, then a minute more, and have server reload mission from save point.

[chromium]

DAWS_Saver doesn't work, even when renamed to actual group name of single client, and I think this is due to bug in DCS with Group.getByName(..), have you tried to rewrite code by unitname instead, like CTLD does it?

 

It could be. I'll add the option to use unit name.

[chromium]

shamandgg, I made the modification and it's online now at the same link. I decided to do not make this as a new version. Please check if it's working for you also.

 

PS1: remember that as a default option, the "single group" option is out by default.

PS2: to make this work, the unitname should be "DAWS_Saver". Group name is not important.

[Shaman]

m now waiting for server to reach 3h time since mission start trigger, to execute save action via do script DAWS.oncallworkflow(), will then see if this really works. All I need is to have a save at 3rd hour, then a minute more, and have server reload mission from save point.

 

Here's the result, error.

 

DAWS.oncallworkflow() saving hasn't worked for me

[chromium]

what you modified? in the current version the line that use zipcreate is 1270, not 1271. Also the error is due to the lack of "NewMizPath" variable, which is defined in line 1137 as this:

 

local NewMizPath = theAutosaveFilename or missionfilesdirectory .. "DAWS-SavedMission_" .. saveCounter .. ".miz"

[chromium]

PS you can test your triggger even with 300 seconds and not >9000, then when everything is in place by your side you can extend the testing.

[chromium]

shamandgg, you will have a PM in seconds.

[Shaman]

Latest findings.

 

-- DAWS_SaveMission for DCSW 1.5
local MainVersion = "1"
local SubVersion = "6"
local Build = "2224"


-- THANKS TO (cronological order):
-- Rider (AMVI)
-- Grimes (ED community)
-- MBot (ED community)
-- xcom (ED community)
-- Ian (ED community)
-- vicx (ED community)
-- Pikey (ED community)
-- ESAC_Matador (ED community)

-- USER VARIABLES

-- object creation
local CreateStatics 			= false -- 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 MapObjectPersitence		= false -- if set "true", it will enable the map object persistence mod (BUGGED!)
local KeepGroupsRoutes			= false -- if set "true", the mod won't delete group routes while saving
local ExcludeTag				= "Xcl_" -- using this tag as a prefix for group name will prevent those groups to be tracked by DAWS. If killed or moved, those groups won't be affected.
local AirUnitTracked			= false	-- if set "true", if a plane gets killed the plane will be removed from the saved mission. If an entire flight is killed, it will be deleted.
local TrackAddedGroups			= true -- if set "true", spawned groups will be saved into the new miz file
local TrackAddedInfantry		= true -- if TrackAddedGroups is "true" and if set "true", spawned units, mortar and manpads will be tracked also, except for those spawned with DAWS AI enhancement mod.

-- saved simulation time 
local KeepContinousMission		= true -- if true it will set the saved mission start time at the saving command minute
local UpdateSceneryDate 		= false -- if true it will add "1" day at each mission save. Works ONLY IF KeepContinousMission is FALSE!!!
local NightMission 				= true -- if set "false", it will prevent to set up mission in evening and night hours.

-- chat message
local theMessageState			= true -- if set "true", it will print out any save mission messages (autosave doesn't print anything)

-- save process
local RadioMenuVariable			= false -- if set "true", it will enable the save command by F10 radio menu. If "off", the save function shall be called by script using the DAWS.oncallworkflow()
local RadioMenuSingleGroup		= true	-- if set "true" and RadioMenuVariable is true, it will limit the save command by F10 radio menù only for a group named "DAWS_Saver"
local AutoSaveEnable 			= false -- if set "true", the mod will execute the autosave function every 10 minutes.
local AutoSaveFileName			= "DAWS_AutoSave.miz" -- this will be the name of the autosaved miz
local UseFixedPath				= true -- if set "true" will save anytime by any process (manual or autosave) in the exact position defined by FixedSavePath
local FixedSavePath				= "C:/FTPVAULT/Missions/DAWS_AutoSave.miz" -- lfs.writedir() .. "Missions/" .. "YourCustomFileName.miz" -- this will set the saving position for UseFixedPath variable, when it's true

 

Server paused with this error:

[chromium]

Will check in the next days, but take into account that you are the only one with the issue and you're using a test beta version not available to public. To avoid confusion, It could be better if you write me by PM.

 

It's always the same issue I see. Please send me your mission and your mod setup (any other mod running?)

[Shaman]

My PMs quickly run out of space here. Can we switch to 51st.org forum?

SLMOD is running, along side DAWS. DAWS is only mod.

I haven't modified anything in the script.

[chromium]

Can you please try a run whitout SLmod? SLmod is basically not compatible with DAWS and I don't know if the workaround I suggested you last time is sufficient. If the issue is there with DAWS only we can start to look inside your version of DAWS. As I said before, having the mission could let me test your situation in the weekend.

 

I prefer to keep here the discussion if you can't free your PMs. can't subcribe in many different forums that I won't follow properly :).

[Shaman]

Then lets keep it to this thread. I would rather keep the SLMOD, man. Without it server is just left for the sake of TK bullies.