DAWS Save Mission

[chromium]

Check your inbox chromium.

I have sent you a pm :thumbup:

 

Looking forward for your answer.

 

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

 

Saw that. I can check it in the weekend I hope :).

[Panthir]

We checked it with =GR= Vaggos and although it saves mission through F10 menu unfortunately the saved mission doesn't includes changes (destroyed or dead units).

[ESAc_matador]

I had this problem with previous versions... is it well configured?? that was my problem.

[Panthir]

If this mod finally works, it will be one of the most important addons for DCS. IMO the most important.

[chromium]

Give me the time to look at this

 

Inviato dal mio SM-G920F utilizzando Tapatalk

[chromium]

We checked it with =GR= Vaggos and although it saves mission through F10 menu unfortunately the saved mission doesn't includes changes (destroyed or dead units).

 

Can't reproduce. Save mission functions from my side and a couple of testers work as expected. Please check writing permission and do not mess with lua files since this beta version. That could break some things :).

[chromium]

Today I will try to solve the need of a permission of writing. If I got it, I will release a small fix. Then I plan to update the pdf manual, so that I could again say to all "RTFM!" :P.

 

Have a nice saturday :)

[Panthir]

Many thanks for your great effort

[chromium]

Meanwhile confirmed the error for next mission start time, I'm looking at this. Don't know if I will be able to release shortly or next week the double fix for mission start time + writing permissions.

[Panthir]

Well, I found out that in my case the script is working only in autosave correctly. The manual save miz although it is created it doesn't have the remaining forces.

Edited March 5, 2017 by Panthir

[chromium]

Well, I found out that in my case the script is working only in autosave correctly. The manual save miz although it is created it doesn't have the remaining forces.

 

This is really incredibly weird, cause the only thing that autosave do is launching the manual save process every "n" seconds.

 

Can you please send me your mission by pm?

[ESAc_matador]

I put few AAV7 vehicles, I moved them via CA. THen stopped. And nothing happened...

 

Should I put an special name for the transport groups?? Am I doing it wrong?

 

Regards

 

(the rest, seems to work fine)

 

For the damage... I guess you are using the alarm status and ROE. Question... what if a unit is damaged, but move such group with CA. will it keep its damaged configuration?

 

Thanks!!!

[chromium]

I put few AAV7 vehicles, I moved them via CA. THen stopped. And nothing happened...

 

Should I put an special name for the transport groups?? Am I doing it wrong?

 

Is the infantry carrier option checkbox active ? with how much percentage?

PS: recheck with BTR-80. Can't remember if AAV7 has infantry carrier attribute.

 

If both are yes, please send me the mission by pm and I will try to reproduce.

 

For the damage... I guess you are using the alarm status and ROE. Question... what if a unit is damaged, but move such group with CA. will it keep its damaged configuration?

 

Thanks!!!

 

If you manually change ROE by CA yes it will change. Otherwise It would be necessary to lock any Group status as uncontrollable. This feature is intended much more for controlling AI ("AI enhancement"): if a player use CA for those groups there's nothing I can do.

 

This is also valid for suppression feature (even if suppression effects lasts only few seconds each time) and will be able for SAM activation status in the IADS feature (still to be completed).

[chromium]

Small update: figured out the date/time issue. I only need to find the f°°°ing time to fix that :P

[SUNTSAG]

Hi Chromium,

 

Thanks for this latest iteration of your Mod, I have been looking forward to this for a while so thank you.

 

I have encountered the following issue linked to the creation of Radio Beacons via CTLD..... I got this exception error:

 

 

 

using these setup parameters:

 

 

any ideas as to a potential solution at all please or have I made an error somwhere? any help you could provide would be greatly appreciated. Cheers.

[chromium]

That seems to be a CTLD error. Even if it happen only combined to DAWS Package, it's not in my code... can't do nothing :(.

[SUNTSAG]

That seems to be a CTLD error. Even if it happen only combined to DAWS Package, it's not in my code... can't do nothing :(.

 

Yes mate it only comes up with the exception error whilst DAWS is running....the CTLD scripted element work fine when I disable DAWS via JSGME.... Ah well c'est la vie and thank you for the quick response very much appreciated. :thumbup:

[chromium]

Try asking to ciribob, butta You need to provide information

 

Inviato dal mio SM-G920F utilizzando Tapatalk

[chromium]

Small update: yesterday night I was able to fix the time update issue, and managed to launch "mist" after mission start to solve the clone/teleport issue (which I can't reproduce for now).

 

I should be able to release another beta in few days. Stay tuned :)

[chromium]

This is the link for updated beta version of DAWS Package.

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

 

Known fixes:

- update time/day of the mission is ok. Keepcontinousmission will work as expected;

- integrated mist clone & teleport functions should work correctly.

 

An updated manual is on its way, even if I hope that the settings available in the "options" menù should be easy to understand :)

[ESAc_matador]

Greeeeatttt!!! I really needed this!

[chromium]

Please let me know if everything work as expected :).

[ESAc_matador]

I arrive home the weekend.

[chromium]

Okok :)

 

Inviato dal mio SM-G920F utilizzando Tapatalk

[Pikey]

Tried it and get the funny issue with Zones again. Doesn't happen without DAWS. It's a custom function that uses mist spawn static, by the way.

00494.703 ERROR   DCS: Mission script error: : [string "e:\temp\DCS\/~mis00003192"]:6719: Parameter #1 (zone name) missed
stack traceback:
   [C]: ?
   [C]: in function 'getZone'
   [string "e:\temp\DCS\/~mis00003192"]:6719: in function 'New'
   [string "E:\_Google Drive\DCS ME LUA\CampaignEngine.lua"]:32: in function 'spawnstatic'
   [string "E:\_Google Drive\DCS ME LUA\CampaignEngine.lua"]:46: in main chunk
   [string "assert(loadfile("E:\\_Google Drive\\DCS ME LUA\\CampaignEngine.lua"))()"]:1: in main chunk