DAWS Package for DCS World - discussion and bug report

If you use JGSME than it should be in Saved Games folder:

https://forums.eagle.ru/showthread.php?t=190778

Then please note the double folder issue... if you won't you can re-download now the mod, it's solved (I reupladed that few minutes ago)

ok we;ll i now have the menu in 2.5 so it appears to work ( we use this versio for our campaigns)

but i am still unable to get it to work in 1.5.8 we use 1.5.8 during the week as it uses less system rescources so tryig to use jsgme in the saved games for 1.5 just sends game to cdt on start up

using jsme in main folder with mods in there game starts fine the program shows as installed but nothing onthe radio menu but if im correct it does not run on 1/5/8? and only works on 1.5.7 correct?

arggggg

ok in 2/5/2 its inthe relvant folder as you state it shows as istalled i even have the menu

yet once again when i start a mission and go to f10 all i see is f1 CDLT and F2 jatac status but nothig relating to dawes there or in any of the other F number choices within the cdlt or jtac

am i supposed to put something onthe map for ti appear? cos i cant find anything inthe docs

RTFM :)

1) DAWS World for 2.5.x .... is for 2.5.x version of the sim. Here:

https://forums.eagle.ru/showpost.php?p=3551008&postcount=101

I said that you need 1.5.7... but IN THAT CASE, you need to install in the main directory cause DCS 1.5.x works differently.

2) "yet once again when i start a mission and go to f10 all i see is f1 CDLT and F2 jatac status but nothig relating to dawes there or in any of the other F number choices within the cdlt or jtac " that is because you need to be in external view or cockpit view to se DAWS menu. This is in point 5 of the manual:

"Get into external or cockpit view".

Else, if you can't see the menu in external or cockpit view, please:

a) check writing protection of main DCS folder (both 1.5.x and 2.5.x version)

b) if protection isn't enabled, re-send me the log.

ok well tried it all but despite setting the folder to uncheck writ protection it still wotn work for me

so looked at my 1.5.8 tried to rever it to 1.5.7 ¬¬ says 1.5.7 not available so i cant eveb roll back 1.5.8 to 1.5.7???? wrf

anyways back to the write protection i uncheck it it does something to the files and shoes as no longer wrtie protected i close the window when i oprn same window again to check and see,,,,guess what the damd box is checked again so it seems somethingis blocking me form unchecking it and i have looked at my adnpermission etc on the pc and all is in order

guess what the damd box is checked again so it seems somethingis blocking me form unchecking it and i have looked at my adnpermission etc on the pc and all is in order

As said before you must be system administrator with full rights, or any "unchecking" operation will work only partially. That's a windows issue, not DAWS issue. Once you get around that, let me know if it works (I can't ensure: honestly don't know what's the difference between 1.5.7 and 1.5.8 in DAWS modified files)

rgr am working on it

rgr am working on it

solved? :)

not yet

Quick Feedback:

- Server's performance is not affected by the package. NOT at all.

- Checked and unckecked some options and they seem to be working just fine. If an option malfunctions I'll report that. Next week I'll have more time for testing other features.

S!

Quick Feedback:

 

 

- Server's performance is not affected by the package. NOT at all.

- Checked and unckecked some options and they seem to be working just fine. If an option malfunctions I'll report that. Next week I'll have more time for testing other features.

 

 

S!

:thumbup:

PS

JFCshloss, solved?

no every time i uncheck the write protection box it does its thing then i close the window wheni reopen and hit properties to check see if its worked guess what the damd box is checked again its like i cant undo thw write protection or something

So how does the dead units erasing/hiding option work?

Destroyed a group of vehicles and waited for like 40 minutes. The fire has died by then and no smoke columns to be seen. Does it take longer for the wreckage to disappear? Do I have to trigger that in the ME?

Another issue:

Say I run a dynamic campaign (which I do), and want the server to restart every 4 or 5 hours. The data is supposed to be saved (I still need to check that out) so when the server restarts players don't need to capture what already has been captured, among other things. But when the mission is reloaded, I need a mission file for that to add in a trigger action in the ME or else it's the original mission file without any changes. Can't figure out how to do it, if you get my point.

So how does the dead units erasing/hiding option work?

Destroyed a group of vehicles and waited for like 40 minutes. The fire has died by then and no smoke columns to be seen. Does it take longer for the wreckage to disappear? Do I have to trigger that in the ME?

Should have been described in the manual. You are misunderstanding the function. With that option you decide if in the saved mission file the new "dead object" that is created each time a unit dies will be set as hidden or not, merely for "declutter" mission editor reason. Obvioulsly that has effect only if you check the option to create a dead object in place of the units that die in the mission.

The purpose is that destroyed units are landmark of previous battles, and also if a plane is downed you will have a dead plane in that spot.. you might use it to set up a medevac action (by editing it in the ME).

Say I run a dynamic campaign (which I do), and want the server to restart every 4 or 5 hours. The data is supposed to be saved (I still need to check that out) so when the server restarts players don't need to capture what already has been captured, among other things. But when the mission is reloaded, I need a mission file for that to add in a trigger action in the ME or else it's the original mission file without any changes. Can't figure out how to do it, if you get my point.

Can't understand the question. Can you please better explain?

As I can tell you I made a version of DAWS that is created to reload each "n" hours the mission using an updated savefile (it's a little tricky to code cause you can't load the file in use itself), whitout having to add a trigger. That file, as it's a DAWS saved file, should take into account any changes... coalition one also, but I never checked about the "capture" thing.

PS

each trigger is retained in the saved file. So if you have a trigger that perform an action after "n" seconds, you will have the same in the DAWS saved file.

I understand.

I want my campaign to run for 6 hours. After that what ever changes took place they will be saved according to what options (boxes) I check/uncheck. So when the 6 hours are over I'll have to manually shut down the server, upload the newly saved mission file (autosave happens every 5 minutes or by saving the mission through the radio F-10) including all the changes that took place, and then start the server for another 6 hours and so on.

My question was; is there a way to have it done automatically by setting up some triggers with particular script lines so that I don't have to do it 4 times a day manually? I think not, but I thought I'd ask.

I'm testing more of the package right now for more feedback.

S!

My question was; is there a way to have it done automatically by setting up some triggers with particular script lines so that I don't have to do it 4 times a day manually? I think not, but I thought I'd ask.

No. but that's exactly what I achieved before in a previous, never released I believe, version.

As said, it's tricky cause you have to cycle between 2 differente autosave files or, else (and that's what I think I was doing) work like that:

- Autosave every n minutes

- Copy command in DAWS that create a copy of the autosave file, like DAWS_autosave_toload.miz

- function that autoload the mission after "n" hours that will load the "toload" file.

I will evaluate if I could add that again in the future.

EDIT no negative I was cycling between 2 files cause the point is that you can't overwrite the loaded file. So you need to make a DAWS_autosave_a, then a DAWS_autosave_b, and load each time the different one. Not extremely complicated, only time consuming to create.

What if we had the autosave work one time only? Say in my case, the campaing runs for 6 hours, so after 5 hours and 59 minutes a file is autosaved and launches right after restart, which will be 1 minute later. Only then after additional 6 hours we'd be having yet another file...

Negative, the issue is that DCS can't load the same file in use. Anyway, you might need to:

1. stop the server

2. disconnect

3. reopen it.

so I think a completely different piece of code... but I like the Idea, so I will investigate. good point.

Mod updated with two main new feature that you can choose in the options menù:

- Automatic server restart function

- DAWS Weather integration: automatic weather update based on current real-time metar (DCS static weather system): at each server restart it will update weather.

So the automatic server restart option is what we've talked about in the post above? If so then it's official: I love you!

Note: When the file is extracted, it's put in a folder that contains a folder that contains the package, which doesn't work in the JSGME unless one takes the files out of the second folder within. You know, the issue we had once. Might wanna fix it so others don't get confused and start posting questions :thumbup:

So the automatic server restart option is what we've talked about in the post above? If so then it's official: I love you!

Hope it works as expected and also the weather update thing is something quite good.

Note: When the file is extracted, it's put in a folder that contains a folder that contains the package, which doesn't work in the JSGME unless one takes the files out of the second folder within. You know, the issue we had once. Might wanna fix it so others don't get confused and start posting questions :thumbup:

You should extract directly in DAWS Package folder itself... oh god, what a ****ing mess making those stupid zips.

I'll test the 2 new options in my dynamic campaign and let you know.

yes, while save scenery functions are all in place and almost rock solid, those new things are to be tested more extensively.

In particoular the "hack" necessary for the weather update is tricky: once a mission is going to be loaded, it will check if last metar used is the same as now (-> no, if everything goes as expected)... so it will save an updated miz file and reload it another time after 0.01s of the mission start. This might or might not break something in other scripts that try to move information from a mission to another... obviously it doesn't break DAWS itself and I can't predict influence on other code in advance.

AFAIK it shouldn't create mess with MOOSE and CTLD, which are the only priority with other mods compatibility.

I see. I'll have the server running over night with these 2 options checked. We'll see...

Test results:

1- After the server ran for 4 hours, it restarted automatically and the weather did change plus the mission's time as well.

2- Dead ground units remained dead, however the wreckage was still there (not hidden/erased)

3- The Ka-50 unit I used for testing has disappeared after the restart! It's like the option deletes the slot completely from the mission's file rather than just hide/erase the wreckage of the destroyed Ka-50.

4- The saved mission's file had the name "DAWS weatherchanged" or something. Can you please tell me where I could change that so players don't get confused, when they want ro rejoin the server and find a different mission's name?

5- When using external views such as F2, the spectator can't move around the object he's spectating or zooming in and out. Maybe the package is blocking that?

Cheers!