DAWS Save Mission

:)

Inviato dal mio SM-G850F utilizzando Tapatalk

Ah i'm just a little late. hope it goes well tonight.

FYI looking to integrate https://forums.eagle.ru/showthread.php?t=179522 this mod to a DAWS persistent server in order to provide a 24/365 persistent server. I'm hoping to persuade the author to build in a rescan of units at start with consistent naming so that AutoGFT can persist its tasking through a DAWS saved state and thus automate a large part of the "continuous warfare" over extended play. Quite excited to build that into a DAWS enabled mission.

Already saw that and I'm working on a DC since a couple of years. At the moment I have a consistent code that provide automatic movement planning and territory owning logic for each coalition, but I don't have proper AI that should take decisions: an if-then-else process won't make it properly cause it's very heavy (even as a finite state machine implementation) and the resulting decisions aren't smart enough. I'm not going to integrate a different code cause it would be more difficult than that... also, before trying to implement the ground DC I need to set some AI enhancement at group level which I'm already working on. It's a matter of years, I think.

The next DAWS release, which I need time to complete due to real life work, will see:

- (RELEASE) Option menù integrated in DCS (no need to lua edit for options);

- (BETA) Integrated MBot suppression script with a little modification (it will work either with arty or area weapon on every unit which is not heavy armoured, SAM included);

- (BETA) Integrated MBot dismount script with little modification (no need to set the unit names, it will apply on an options defined percentage of unit that will need to have "infantry carrying" attributes);

- (BETA) Improved SAM logic: Sam that are under AWACS/EWR covered area will stay off till an enemy air asset come into WEZ range.

- (ToBeWritten) Automatic mission restart with the autosaved mission file;

- (ToBeWritten) Automatic arty fire: when allied units detect anamy in range of an arty section with no allied unit proximity will set a fire mission, communicated by chat;

- (ToBeWritten) Automatic AI withdraw: when enemy unit is under fire and its group does not have whitout having valid targets to engage, they will try to run away from that position heading to the nearest safe position (instead of disperse in the same area becoming stationary targets).

- (ToBeWritten) Simplified troop trasportation logic with no setup needed: any squad of 6-8 infantry will be considered as a valid cargo for transportation helos, retaining compatibility with CTLD by my side (it will work if CTLD is not active. If so, CTLD will do the transportation logic);

Any of the above is enabled or not by DCS integrated options menù by one click.

Once this is in place I will restart AI working for a proper DC AI integration... I'm looking at GOAP logic, but it's complicated for me that I'm not a programmer. I know that there aren't many updates since months, but I strongly prefer to complete this step forward at least in beta release before public something: this will help me to keep a simple support processs as know that will allow fast response to any issue.

Sounds very exciting!

- (BETA) Improved SAM logic: Sam that are under AWACS/EWR covered area will stay off till an enemy air asset come into WEZ range.

I guess you already know the IADS Grimes script.... but just in case... I needed to mention.

I know it, but as ctld It's plain integration is complex and also require setup by mission designer. I only want code like save mission: no mission setup required. Everything have to work as it is, additional effort should be done only for exeptions. That's our plan.

EDIT: also consider that:

1. SAM logic is already done, so unless for debugging it won't Take time. What It's said as "BETA" is ready and tested SP and MP, but only in my computers.

2. As CTLD with the transportation logic, if Grimes IADS code is detected the SAM logic will be disabled as I consider Grimes code better than mine. Anyway (as CTLD) compatibility of other people code can't be gusranteed by me and even if I try to keep DAWS code to not interfere with other effect any AI interaction that I don't understand in every single line could broke something by DAWS or other mod side.

Inviato dal mio SM-G850F utilizzando Tapatalk

That is great then! Very good job yours!

Once this is in place I will restart AI working for a proper DC AI integration... I'm looking at GOAP logic, but it's complicated for me that I'm not a programmer. I know that there aren't many updates since months, but I strongly prefer to complete this step forward at least in beta release before public something: this will help me to keep a simple support processs as know that will allow fast response to any issue.

Been reading the literature on GOAP and believe it will meet the needs for DCS AI better than an FSM, given the significant number of different unit types (agents) in DCS, their large number of actions and ED's habit of changing things with updates, which means that modular code with the DCS hooks all in one place is a necessity.

My thought process, given the CPU intensity of the DCS engine, would be to export the DCS world state using JSON to another server, which would then run the GOAP scheduler and planner and then give back actions to the DCS units.

Ultimately this second master server could provide the world map updates, similar to those of http://gadget.buddyspike.net/ and maybe even be able to operate as a mission planning tool prior to the simulator start, a command tool during the run and a debriefing tool thereafter. While this might well be an easier project than getting the AI units to behave more naturally, I believe the latter project would be more impactful to the users' experience.

Given that the low level AI behavior is handled inside the DCS code, I do not think that the latency of the planner will be too great a problem.

I would love to assist you in your endeavors Chromium, but I warn you I am weak at both Lua and C++, so if I was doing it would run the dB in SQL Server and the application in C#, where I spend most of my work programming life.

Look forward to linking up with you at your convenience.

Durham

Hi Chromium,

First of all, congratulation and thank you for this savegame modules. We started using it in the squadron, along with the real weather module.

While most of the testing went fine, it seems to have an issue with long running missions. When i leave server open for an hour or two, it works.

When server runs for longer period, neither manual or autosave works.

I will try further testing tommorow with automatic save command, but i though maybe you already knows something about that ?

Greetings !

Pierre.

Been reading the literature on GOAP and believe it will meet the needs for DCS AI better than an FSM, given the significant number of different unit types (agents) in DCS, their large number of actions and ED's habit of changing things with updates, which means that modular code with the DCS hooks all in one place is a necessity.

 

My thought process, given the CPU intensity of the DCS engine, would be to export the DCS world state using JSON to another server, which would then run the GOAP scheduler and planner and then give back actions to the DCS units.

 

Ultimately this second master server could provide the world map updates, similar to those of http://gadget.buddyspike.net/ and maybe even be able to operate as a mission planning tool prior to the simulator start, a command tool during the run and a debriefing tool thereafter. While this might well be an easier project than getting the AI units to behave more naturally, I believe the latter project would be more impactful to the users' experience.

 

Given that the low level AI behavior is handled inside the DCS code, I do not think that the latency of the planner will be too great a problem.

 

I would love to assist you in your endeavors Chromium, but I warn you I am weak at both Lua and C++, so if I was doing it would run the dB in SQL Server and the application in C#, where I spend most of my work programming life.

 

Look forward to linking up with you at your convenience.

 

Durham

Thanks for the support but DAWS is going to work whitout having external servers or similar by design choice :)

Hi Chromium,

 

 

First of all, congratulation and thank you for this savegame modules. We started using it in the squadron, along with the real weather module.

 

While most of the testing went fine, it seems to have an issue with long running missions. When i leave server open for an hour or two, it works.

When server runs for longer period, neither manual or autosave works.

 

I will try further testing tommorow with automatic save command, but i though maybe you already knows something about that ?

 

Greetings !

 

Pierre.

I tried with pretty heavy mission for 4 hours. If you confirm this behaviour please send me the DCS log file :)

Hi Chromium,

I can't reproduce anymore. I'll keep the log if this happen again. maybe something that i added/removed from mission solved the issue. Thanks again for your great work. :)

In 1.5.6 Save mission is not working. I will fix asap.

Update: I'm beta-testing a working version with some people. As soon some small troubles are fixed I should be able to release a public version (Maybe I'll call that beta for a while)

Hello everyone. This update has been complex cause I strongly wanted to integrate at least few of the new AI enhancement features that I'm (slowly) coding. The main release will be in a separated thread and with a link in the AMVI download page, as previous version, with a new name: DAWS package.

Before I can release I need your help: I'm asking you to try this beta version:

http://www.amvi.it/download265-daws-package-for-dcs-157.html

This beta release of DAWS package will include:

DAWS Save Mission, with all its feature.

(PS: Checked compatibility with MOOSE and made some test with CTLD also.)

In the next release, will be available again:

DAWS AI Enhancement, with 3 features:

- Suppression fire: this is a modification of the fantastic Suppression fire script by MBot. It doens't need setup: it simply put in "hold fire" condition any non-armoured or light-armoured ground groups that is hit (any of the unit) by shell or rockets fire. Artillery fire included. (PS: SAM are by DCS definition light armoured, so this will work);

- Vehicle damage enhancement: each time a vehicle is hit by something, it will calculate a slighly probability that some functionality is damaged. Probabilities will change with armour grade obviously. There are 3 possibile events: wheel or engine damage: the vehicle won't move anymore. Weapon damage: the vehicle won't fire anymore. Driver dead: the vehicle will stop and hold fire. This is a small try to add behaviour to seriously damaged vehicles that, as for DCS now, can behave almost as fully functional vehicles until they goes dead.

- Infantry dismount: this is also a MBot Dismount Script modification. It will check any ground vehicle with "infantry carry" attributes and set a percentage of them (see menù) as "dismountable", so each time the vehicle stop it will dismount a certain infantry types that could be rifleman, manpads or mortar. The type is defined once at mission start, and the probability to get manpad are lower than mortar and much lower than rifleman. PS: dismounted infantry CAN'T be controlled: it will move nearby the vehicle and fight.

To customize DAWS Package options and features you now have a dedicated options menù:

Wuao!

Outstanding work Chromium, I have been waiting for this mod to be updated to begin the campaign on Georgian Spring 1955.

One question; has it been tested with Slmod?

Yes and it's has never been compatible, cause SLmod will check every time if missionscripting.lua is modified and overwrite it with its own. Therefore to enable SLmod compatibility you need to modify one of the SLmod core file to add the line that will activate DAWS. But then, you will anyway have to check this every time an update at daws is done or everytime you disable DAWS.

Another advice: for those that will use dismount options, consider that it may impact performances cause adds a lot of spawn and despawn even each time the ground group is moved by something. For that reason I add the percentage slider, so that if you have a many-hundreds ground unit scenario you might want to set it between 10-15%, while if you have a total of <100 infantry carrying ground units and a good PC/Server you could set it to 90-100%.

You can break your singleplayer mission, and resume it later?

What make the triggers active/ passive.

Check your inbox chromium.

I have sent you a pm :thumbup:

Looking forward for your answer.

:helpsmilie: :helpsmilie: :helpsmilie: :helpsmilie: :helpsmilie: :helpsmilie: :helpsmilie:

You can break your singleplayer mission, and resume it later?

What make the triggers active/ passive.

No. It simply Save the scenery status. Check old manual q&a for more info

Inviato dal mio SM-G920F utilizzando Tapatalk

Is the number of killed dismounted units kept? Because the original script didnt.

I ll try to work on it today.

Negative. It work similar to the original script

Inviato dal mio SM-G920F utilizzando Tapatalk