Jump to content

DAWS Save Mission


chromium
 Share

Recommended Posts

Well it's matter of time. As soon as I can, I'll post a testing version. But I have to say that in this version, any spawned units will have a new ID and name, as groups, in the saved files. Therefore, I could be that saved spawned groups created with CTLD (any thing you will transport) won't keep their names in the saved file.

ChromiumDis.png

Author of DSMC, mod to enable scenario persistency and save updated miz file

Stable version & site: https://dsmcfordcs.wordpress.com/

Openbeta: https://github.com/Chromium18/DSMC

 

The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.

Link to comment
Share on other sites

  • Replies 442
  • Created
  • Last Reply

Top Posters In This Topic

Well, in my opinion, it is important to save the names of the groups, because there are scripts that depend on their names. It is easier to manually edit the mission and move the spawned units, than to put the name of all of them. We are talking about lots of groups.

 

We can test it, but, in my onpinion, it has its own pro and cons.

 

Let see!

Link to comment
Share on other sites

Everithing rely on MIST dynGroupsAdded database (in the end it's not suitable in this couple of years an upgrade to a non-mist version).

 

if that database store the correct name, the spawned units would have that name. If not, I don't believe that could be a viable solution to this issue.

 

Anyway, I'm going to try... cause if even not viable for CLTD, it would add the capability to track spawned units.

ChromiumDis.png

Author of DSMC, mod to enable scenario persistency and save updated miz file

Stable version & site: https://dsmcfordcs.wordpress.com/

Openbeta: https://github.com/Chromium18/DSMC

 

The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.

Link to comment
Share on other sites

Yes it works the same (weird) Way as before.

 

Inviato dal mio SM-G850F utilizzando Tapatalk

ChromiumDis.png

Author of DSMC, mod to enable scenario persistency and save updated miz file

Stable version & site: https://dsmcfordcs.wordpress.com/

Openbeta: https://github.com/Chromium18/DSMC

 

The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.

Link to comment
Share on other sites

Update:

DCS W 1.5.2 patch changed something that lead me to a small update to ensure DAWS Save Mission to work properly.

 

So, please download again the mod for snapview and config compatibilty in miz files.

ChromiumDis.png

Author of DSMC, mod to enable scenario persistency and save updated miz file

Stable version & site: https://dsmcfordcs.wordpress.com/

Openbeta: https://github.com/Chromium18/DSMC

 

The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.

Link to comment
Share on other sites

Small update:

I achieve adding the spawned group to the mission, but at the moment it doesn't work as expected and the position of the group isn't correctly tracked.

 

Anyway, it's a small step to this result.

ChromiumDis.png

Author of DSMC, mod to enable scenario persistency and save updated miz file

Stable version & site: https://dsmcfordcs.wordpress.com/

Openbeta: https://github.com/Chromium18/DSMC

 

The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.

Link to comment
Share on other sites

Hi Chromium, Just stopped by again to pass on all our thanks from 42nd for your mod. We have now been using it successfully now in a large campaign that I wrote especially with DAWS in mind. We are now 8.5 hours into the campaign and at this rate should be complete in around another 22 hours, assuming they keep the same progress at night, which is unlikely! The save mission function works flawlessly, we do not use the autosave, 1.5.2 has been stable enough to just save towards the end of the session. We keep ground units movements (they have driven so far from Zugdidi to Ochamchira port) we do not save map features - I may keep this if we ever defend and need to blow bridges.

 

I have one minor ask that would make this complete and that is to see if you can get spawned objects to save, which i know you are working on. This is important for our CTLD script which can spawn infantry and JTAC and so on. The territory capture method works by detecting units presence in zones, so when the mission is run again the next time it needs to check for presence of bluefor and ofc if we dropped spawned troops into these zones it means we lose captures when the misison restarts. It's easy to work around really, dropping just one item into the zone, but just saying it would be complete for that.

 

Thanks again, I'll send you a copy of the campaign once a few minor things are resolved.

___________________________________________________________________________

SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING *

Link to comment
Share on other sites

Little (sadly) update:

 

I achieved a correct spawned units save feature. But as soon as I try to move the newly spawned group in the saved mission, all units but the first disappear.

 

The only real difference between the saved spawned groups and the original editor groups are the dictionary keys: saved groups has names... real names. Editor groups has only dictionary ids.

 

I don't know how to create new dictionary keys... and it seems that I'm stuck in this issue. _G table hasn't some kind of "reverse" function of env.getValueDictByKey.

 

Therefore I don't know how to solve the issue. If someone has some kind of idea, I'll be happy to hear. :).

ChromiumDis.png

Author of DSMC, mod to enable scenario persistency and save updated miz file

Stable version & site: https://dsmcfordcs.wordpress.com/

Openbeta: https://github.com/Chromium18/DSMC

 

The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.

Link to comment
Share on other sites

:( If there was a way to explain it, there are some awfully clever folks here, just needs a way to make it an appealing problem to solve. Maybe provide a sample mission that reproduces this for people to play with?

 

Thanks so far!

___________________________________________________________________________

SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING *

Link to comment
Share on other sites

I think that the best explanation is in the previous post. But to be simplier, what I need is a way to create new Dictionary entries for the spawned units. If it's not possibile, I think it won't be possible to add this feature.

 

PS: I'm with the flu this evening, so I might be not that much sharp.

ChromiumDis.png

Author of DSMC, mod to enable scenario persistency and save updated miz file

Stable version & site: https://dsmcfordcs.wordpress.com/

Openbeta: https://github.com/Chromium18/DSMC

 

The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.

Link to comment
Share on other sites

  • 3 weeks later...

I'll check asap.

 

Inviato dal mio SM-G850F utilizzando Tapatalk

ChromiumDis.png

Author of DSMC, mod to enable scenario persistency and save updated miz file

Stable version & site: https://dsmcfordcs.wordpress.com/

Openbeta: https://github.com/Chromium18/DSMC

 

The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.

Link to comment
Share on other sites

Hello Chromium, i cant download the last version. The link doesnt seem to work. Can you update it?

 

Yeah it seems that due to the new AMVI site the link didn't work anymore.

I updated and verified it, so now you should be able to download properly. :)

ChromiumDis.png

Author of DSMC, mod to enable scenario persistency and save updated miz file

Stable version & site: https://dsmcfordcs.wordpress.com/

Openbeta: https://github.com/Chromium18/DSMC

 

The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.

Link to comment
Share on other sites

  • 4 weeks later...
Just to be clear, it is only working if I manually save the mission using the F10 menuitem, there is no automatic save. I wonder if it is a permisisons thing...will see.

 

@Chromium,

 

I am having the same symptoms as Pikey did, I can manually save the mission state if I have enabled the F10 Menu item and it works flawlessly in both MP and SP missions, however, I can not seem to get the autosave to function. This it true for all installs on both of my computers.

 

I am running a server and would love to be able to utilize the autosave feature so I can leave it running and have it saving continuously.

 

I am also seeing some strange things in the logs, I can confirm that unless I manually choose to save a mission, there will be no DAWS entries in the log file so it is not being initialized. When I do manually save it I get this strange series of entries in the log at the time I initially save it:

 

00047.760 INFO SCRIPTING: mist not found, load from -code- directory

00047.786 INFO SCRIPTING: Mist version 4.0.57 loaded.

00047.786 INFO SCRIPTING: --> MOSSReset() ha resettato le variabili e completato il processo

00047.793 INFO SCRIPTING: --> mission file in tempdir opened

00047.793 INFO SCRIPTING: --> MOSSStartMission() ha creato gMOSSMix, che non è nil

00047.794 INFO SCRIPTING: DAWS Save Mission version: 1.5.2178 loaded

 

then a few lines latter:

 

00085.533 INFO SCRIPTING: Mist version 4.1.61 loaded.

 

since Mist is the first thing loaded in the mission I find it strange yet if I do not enable the F10 radio menu item to save it, Mist loads normally and DAWS never does.

 

an additional piece of information that may be relevant is the path in the mixpath.txt file is:

 

C:\Users\lorenzo\Saved Games\DCS.openbeta\Missions\demoSX_1.miz

 

no matter where I have installed it or what name I have given the autosave file in the configurations section of the script. I have opened this file manually and changed it to match my situation and I still have no luck.

 

Ideally I would love to figure out reason and correct the problem that both Pikey and I are having with your amazing script.

 

For the short term however, I read that you had come up with a solution for Pikey that gave him an autosave, could I have a copy of that script so I can test on my server?

 

Thanks for the great script!

Georgian Spring Server: Join the Revolution!

http://georgianspring.enjin.com/

 

Training for Sabre Pilots

http://1-fighter-otu.enjin.com/

 

http://www.il2aceshigh.com/

Link to comment
Share on other sites

It seems a permission issue imho. Can't understand Why it prevent to work the autosave only, cause Most case it would prevent any working (and you have to ensure that no permission is needed to write into the dcs folder and the save games folder).

 

I Will look better into this info But i think that i can't do much.

 

PS pikey solved the issue By lauching the save process by trigger, And i worked if i recall correctly. No additional script is required

 

Inviato dal mio SM-G850F utilizzando Tapatalk

ChromiumDis.png

Author of DSMC, mod to enable scenario persistency and save updated miz file

Stable version & site: https://dsmcfordcs.wordpress.com/

Openbeta: https://github.com/Chromium18/DSMC

 

The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.

Link to comment
Share on other sites

Rob, the log entry Aren't Strange, They are normal and They run before everything. Please note that sec. 47 is not the 47th second of the mission. Try to load a mission, let it run 1 sec and then Close whitout using save functions. You Will see those entries anyway. If not, write that here.

 

The mizpath.txt is a placeholder file modified by daws during its run. You should and won't modify that.

 

Imho the issue seems bound to the fact that for some reason 2 thing could happen:

1- something is preventing the scheduling function to run properly,

2- something is preventing your pc to write the saved file in your folder.

 

Anyway, please ensure that all your dcs folder, including the amvi one, ha free access for writing. The Most weird thing is that the script work properly once called manually.

 

Why don't you send me your mission to let me check if i could see any issue about it?

 

Inviato dal mio SM-G850F utilizzando Tapatalk

ChromiumDis.png

Author of DSMC, mod to enable scenario persistency and save updated miz file

Stable version & site: https://dsmcfordcs.wordpress.com/

Openbeta: https://github.com/Chromium18/DSMC

 

The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.

Link to comment
Share on other sites

Rob could you plase let me know about the log entry whitout trying to save and about your mission file?

 

I could make some tests before monday and I would really like to undestand if there is a chance to investigate your issue :)

ChromiumDis.png

Author of DSMC, mod to enable scenario persistency and save updated miz file

Stable version & site: https://dsmcfordcs.wordpress.com/

Openbeta: https://github.com/Chromium18/DSMC

 

The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.

Link to comment
Share on other sites

Maybe a good news. I was able to reproduce the issue in our new server and I have a small idea... if it's right, the autosave issue could be solved fast.

 

EDIT:

seems solved. I will put a test version online before tuesday... but in the meantime, please remove your mist loading at mission start: mist 4.0.57 is already loaded with DAWS Save Mission. It should be ok that way.

 

the issue seemed due to the fact that once you load your mist version, it will overwrite the MIST one. And it's ok to me.. but sadly this would reset the mist.schedule function table... that had the autosave call inside. So I'm replacing mist.scheduling function with timer.schedule, that won't be affected by any mist overwriting itself issue ;)


Edited by chromium

ChromiumDis.png

Author of DSMC, mod to enable scenario persistency and save updated miz file

Stable version & site: https://dsmcfordcs.wordpress.com/

Openbeta: https://github.com/Chromium18/DSMC

 

The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.

Link to comment
Share on other sites

Best thing you could try is run your mission whitout loading mist as a trigger, And confirm that everything is ok

 

Inviato dal mio SM-G850F utilizzando Tapatalk

ChromiumDis.png

Author of DSMC, mod to enable scenario persistency and save updated miz file

Stable version & site: https://dsmcfordcs.wordpress.com/

Openbeta: https://github.com/Chromium18/DSMC

 

The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.

Link to comment
Share on other sites

I managed to find a moment to run the mission without Mist. Unfortunately, the various scripts such as GIACAP , CSAR etc did not work so I replaced the Mist version in the AVMI folder with the latest version and still had issues.

 

I ran a simple mission that did not require MIST and it ran as expected, autosave worked flawlessly.

 

So MIST loading twice is confirmed as the issue. Hopefully a solution can be found.

 

Thanks for all the hard work on this script

Georgian Spring Server: Join the Revolution!

http://georgianspring.enjin.com/

 

Training for Sabre Pilots

http://1-fighter-otu.enjin.com/

 

http://www.il2aceshigh.com/

Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...