[CallsignFrosty]

Hi Chromium,
I seem to be having the exact same problem with our server that Picchio is having.
The temp folder is created but no mission file. The message ‘saving mission’ comes up but no .miz file appears.

I have triple checked the permissions on both the C:\ folder and the saved games folder but to no avail.

It works absolutely fine on my client PC when mission testing, just not on the server.

Any help would be greatly appreciated, thanks.


Sent from my iPhone using Tapatalk

[CallsignFrosty]

Cancel that - it is now suddenly working!!!
Strange that I didn’t change anything!


Sent from my iPhone using Tapatalk

[CallsignFrosty]

Now I have a new problem
I took the the saved mission and edited it but when I saved it, the editor crashed and I lost all of the changes. I was able to keep reproducing this eveytime i tried
Please see the attached log file.

https://ufile.io/oxh4h

[Alpenwolf]

You there, chromium? Hope you're fine, buddy.

[chromium]

I was on holiday in the other side of the world with no forum access, folks... simply that

[chromium]

Originally Posted by Alpenwolf

Regarding the autosaved file, the way I see it the package autosaves the scenery every 5 minutes. Say a server is supposed to restart after 6 hours (the last option you've added), then the package would initiate the last autosave after exactly 6 hours, which is the time at which the server restarts. Explains why the file's in use and can't be renamed.

Won't work, cause as you reload the file the second time it will be the same file (DAWS_autosave.miz) that is loaded.. and when it's loaded, it is considered in use by windows for the entire mission time. Also, if you check the code you will notice that DAWS make an autosave right before the server restart, to be sure that you won't miss nothing in the subsequent reload. It's still a beta feature, anyway .

[chromium]

Originally Posted by dimitriov

Hi Chromium, thanks for your work, I have a little question : does this script save the flags values ? IE : on our server we will have a mission with a marker which increments everytime something is killed, to act like a score.

Uhm, To be honest I never checked out, but I don't think so, cause the idea is to leave the SSE doing it's work whitout interference and to avoid issue with other "flag-driven" code... and I never build up a flag-traking option.

I would also be a mess to consistently track them if it doesn't do by itself. I give a 0.1% that DAWS saving system tracks flag status.

Originally Posted by dimitriov

Will every triggers including flags, or "Time over XX s after mission start" be reset ?

Given what said above, the answer is 99.9% yes. I don't have my usual PC access till a coulple of days, so best is that you try with a smallest dedicated mission with one trigger: ONCE -> TIME MORE 10 -> Flag on (1). then you save after 11 seconds or more and check the saved file.

[chromium]

For both Picchio and CallsignFrosty

Issues are different. Very much.

Picchio: your issue is about saving, and as I asked you by PM I can't do nothing if you don't provide me the miz file. Also, please check that you don't have mods installed... if you have mods,
1) retry without mods to check if is the mod.
2) if the mod is causing the issue, please tell me which mod is.

In particoular something is failing when DAWS try to retrieve the info of a particoular object (unknown). I'm asking about mods cause not always those info are retrievable from mod object.

If no mod, I need to understand which object exactly is that cause the error... to do that, I need the miz file.

CallsignFrosty: You can save the mission. I have to say that it seems a DCS error, caused (don't know why) by something that have to do with DAWS. As for Picchio, I need you to send me the .miz files.

Please check for mod also.. I see, for example, that you are running LoATC. I don't know actually if there are any kind of compatibility issue (I don't think so).



I would like to point out that every time I push a release (even beta), it's tested by at least 4 people in very different situation and configuration... but obviuosly I can't guarantee the result in any situation and configuration... anyway all the last time that issue was in place, every time I needed the user support with log, miz file and sometimes (when he's using mods) test to solve it.

It's really important your direct support when an issue came out: a small issue is not sufficient sadly... I need almost always dcs.log file and the .miz file.

PS: if you rename dcs.log in dcs.txt you can upload it directly in the post, together with the miz file, whitout having to rely on an external download site

Thanks

[Alpenwolf]

Good to have you back. Got some tan, I recon

[chromium]