DAWS Save Mission

[PVI_Eagle]

:)

I only have one life.

[FlightControl]

What i don't get is ...

 

How to merge static campaigns using DAWS from session to session

with dynamic mission and task creation in MOOSE?

 

I mean, MOOSE does a dynamic task creation and task governance, and all this is initialized at mission start. It will create new objects dynamically, create new tasks dynamically, create new missions dynamically while the mission is running in a true multi-player environment.

 

How to bring DAWS into this process? It is apples and pears, no?

 

When the mission would be brought up again using DAWS, it would load the units last known positions.

But the whole process and governance is lost of the tasking and mission creation. The only way I see such possible, is to implement a DAWS-like function within MOOSE itself. But that is a whole other exercise.

Or link MOOSE with DAWS.

 

It would be nice though to have, I agree, but that is for next year.

Let us first get MOOSE tasking stable and working correctly.

 

Step by step buys, really. Instead of having wishlists, it would be more beneficial if you would contribute and help to test out what is currently in development. And provide feedback from an end-user perspective.

 

Chromium and myself will get into contact with each other when time is ripe. It is a promise from my part.

 

Sven

[chromium]

Daws lets you save the situation on the battlefield, even in multiplayer missions: this way you can create and manage multiplayer campaigns that last for a while, that can last for days or months...

The problem is that daws is not fully compatible with the moose: Daws prevails over the moose, leaving the moose only the creation of planes and helicopters, not even ground forces.

Also daws does not allow moose to handle the radio menu, so I can not create those attack missions managed through the FACS ...

If it was possible to make DAWS fully compatible with the moose, then we would finally have real multiplayer campaigns even in DCS ... it was a shame!

 

uhm, last time i checked the only issue between daws and moose was about AI enhancement.

Save mission alone (current download link) worked perfectly with MOOSE in the test mission me and Pikey tried.

 

Can you please provide test mission and crash logs?

Which sim version?

[chromium]

I only have one life.

 

Me too, sadly

[chromium]

What i don't get is ...

 

How to merge static campaigns using DAWS from session to session

with dynamic mission and task creation in MOOSE?

 

I mean, MOOSE does a dynamic task creation and task governance, and all this is initialized at mission start. It will create new objects dynamically, create new tasks dynamically, create new missions dynamically while the mission is running in a true multi-player environment.

 

How to bring DAWS into this process? It is apples and pears, no?

 

When the mission would be brought up again using DAWS, it would load the units last known positions.

But the whole process and governance is lost of the tasking and mission creation. The only way I see such possible, is to implement a DAWS-like function within MOOSE itself. But that is a whole other exercise.

Or link MOOSE with DAWS.

 

It would be nice though to have, I agree, but that is for next year.

Let us first get MOOSE tasking stable and working correctly.

 

Step by step buys, really. Instead of having wishlists, it would be more beneficial if you would contribute and help to test out what is currently in development. And provide feedback from an end-user perspective.

 

Chromium and myself will get into contact with each other when time is ripe. It is a promise from my part.

 

Sven

 

Once I saw MOOSE I started to split single functions in DAWS Package, like Save Mission and AI enhencement features. So that you could choose to use one of them (like save mission) leaving the other disabled, and use MOOSE or other AI interacting mods.

 

Save Mission code do not mess up with moose, it may lack of features (i.e. cargo, for example) cause DCS core code change over time and also change object creation methods and structure or file mission structure. Instead, AI enhancement was messing up with moose and therefore disabled.

 

But Eagle, you're asking MOOSE to do a whole new thing: create a "situation report" thing outside DCS that is not erased from mission to mission, some sort of information pipe between the end of a mission and the reload of the next one. Like MBot does for its dyn campaign but way more complex.

 

Not much easy to be implemeted. I will, when my free time allow, talk to FlightControl... but I think that the best way could be to save tables in .csv format inside the mission files (in the same folder lua code is placed) so that MOOSE can load those info at next mission start with a simple parsing function. But... last time I tried for the Dyn campaign module of DAWS Package sadly I found that once you open the miz file in editor and save it again, those files are deleted.

 

So for now it seems that this kind of solution works only in 2 way:

- You don't touch the miz files from mission to mission (almost impossible but in very few cases);

- You save the tables locally in Saved Games DCS dir. Then, if you send the miz to another person, It won't work as expected. Bad thing.

[Pikey]

I didn't have a problem either with the core DAWS, but there were some testing builds in between so I lost track of version. Probably the last one is ok.

 

For MOOSE and DAWS, of course they are completely different. What DAWS promises, is a way to save the state of unit positions whilst the server is being restarted. MOOSE unfortunately has no persistence, so any of your scripts that need to remember something won't work, objects are lost in memory. However, you can design around this, one of the things i've been trying to puzzle is exactly that. If DAWS saves the names of groups and units, then on first run, MOOSE can recreate your objects, as long as nothing changes. For anything major you can save global variables to disk. So really, everything is in place, it's just the design of the finer points.

[Pikey]

I did a "save phase" technique when DAWS wasn't working. Rather than save unit positions, it just writes global variables to disk every so often, to a single file. At the start of the mission it checks for the file, if it exists, it reads it and executes it first, then all the rest of the mission scripts run and in this way you can make a kind of offline state. It's quite good for things like airbase saving or if you have say one mission and want to merge to another mission, run them from two different scripts and procede to the next one...that type of thing.

Once I saw MOOSE I started to split single functions in DAWS Package, like Save Mission and AI enhencement features. So that you could choose to use one of them (like save mission) leaving the other disabled, and use MOOSE or other AI interacting mods.

 

Save Mission code do not mess up with moose, it may lack of features (i.e. cargo, for example) cause DCS core code change over time and also change object creation methods and structure or file mission structure. Instead, AI enhancement was messing up with moose and therefore disabled.

 

But Eagle, you're asking MOOSE to do a whole new thing: create a "situation report" thing outside DCS that is not erased from mission to mission, some sort of information pipe between the end of a mission and the reload of the next one. Like MBot does for its dyn campaign but way more complex.

 

Not much easy to be implemeted. I will, when my free time allow, talk to FlightControl... but I think that the best way could be to save tables in .csv format inside the mission files (in the same folder lua code is placed) so that MOOSE can load those info at next mission start with a simple parsing function. But... last time I tried for the Dyn campaign module of DAWS Package sadly I found that once you open the miz file in editor and save it again, those files are deleted.

 

So for now it seems that this kind of solution works only in 2 way:

- You don't touch the miz files from mission to mission (almost impossible but in very few cases);

- You save the tables locally in Saved Games DCS dir. Then, if you send the miz to another person, It won't work as expected. Bad thing.

[chromium]

So really, everything is in place, it's just the design of the finer points.

 

-> this.

 

Be at 80% of the necessary code in both mods means usually be at 25% of the project completion but... I'm optimist :)

[Spanker79]

Hey Chromium...

 

After the latest update to 1.5.7 DAWS doesnt work and i have a script error. I am not using any mods.. Vanilla installation.

 

Waiting for your (or anyonelse) feedback.

 

Thnx

Edited July 14, 2017 by Spanker79

[chromium]

I'll look at that next week, sadly I can't this weekend :(

[Spanker79]

I'll look at that next week, sadly I can't this weekend :(

 

Any news regarding DAWS?

[chromium]

Negative, life is too busy in those weeks.. I hope for holidays soon

[chromium]

Any news regarding DAWS?

 

Link and mod updated, seems to work as expected :)

[chromium]

Trying to anticipate future problems with new mod structure of DCS 2.1.1 and following. If someone is skilled in module integration, please have a look here: https://forums.eagle.ru/showthread.php?t=192261

 

At the moment DAWS Package work in 1.5.7 and current mod structure but it's not going to work anymore in the future steps, unless I'll find a way to load the core file right after mission start. And I'm not going to accept that the user will need to ad a trigger or similar like other SSE mods to get this in place. I need to find a proper solution that will ensure DAWS to be a "one-shot" for every user, like now.

Edited August 17, 2017 by chromium

[chromium]

Hello everyone,

 

with Grimes and Skatezilla help I found a way to make DAWS to properly work with the new mod structure of DCS World 2. The install procedures is the same but you have to change one simple but very important thing:

 

you have to install this in your DCS Saved Games Folder.

(i.e. "C:\Users\loren\Saved Games\DCS.openalpha")

 

installing this mod in the DCS main folder will cause it to do not work as expected.

 

Link: http://www.amvi.it/download299-daws-package-for-dcs-world-2x.html

 

PS:

it's a beta, please take it as it is. Any reported error will help me to improve structure before 2.5 will come.

 

PS2:

this version will work only with DCS 2.1.1. For DCS 1.5.7, stick to the previous version mentioned above.

[chromium]

Current 2.1.1 release has a major issue that could cause the mod to do not work with who didn't had installed DAWS before. The issue is already fixed, but I'm working to improve furtherly the structure using the excellent API provided by ED.

 

I think that I might release a fixed version in few days, and then I might be able to restart AI enchancement module developing for 2.x only. Probably the new mod structure given by ED will also fix the MOOSE compatibility issue that lead me to disable AI enhancement features.

[Pikey]

Wow this seems unusually positive!

[chromium]

It is. I have an updated manual for both version and an updated pack for 2.1.1. I'm going to post them asap, in a new thread and restart there mod discussion. DAWS "Save Mission" definition has done its time, I need cleaup to let people discuss future features also.

[chromium]

Thread up:

https://forums.eagle.ru/showthread.php?p=3229846#post3229846

 

Please do not reply to this one anymore :)