chromium

In questi casi penso sia importante basarsi su fonti certe. Ora, io non ho manco provato a cercare perchè un me frega nulla nello specifico, ma non c'è un diamine di manuale di volo in giro da scaricare? C'è per una bordata di velivoli pre 2005... Da lì è facile capire l'andazzo. Però seriamente non sottovaluterei il vantaggio di avere una possibilità biposto in un aereo da bombardamento moderno anche per la sola divisione dei compiti... soprattutto perchè quando era stato pensato il sistema in essere il volo a bassissima quota era cosa prevista abbastanza spesso. Non mi stupisce che il pilota da solo possa fare tutto, che lo possa fare con la stessa SA ed efficacia che in due, di notte, etc... beh, dubito.

Picchio, I sent you a PM. The issue is probably due to normandy / WWII asset pack... which I can't test cause I don't own them... I will give a try as soon as possible with a friend... but it's better if you please test daws on any mission running caucasus, nevada or persian gulf and confirm it's ok (to confirm that is a normandy/wwII issue and not something else related to you in specific)

:)

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 :)

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. 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.

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 .

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

Done, option added and start time fixed, you will find the new start time options in option menù ;)

Dont' build the package, but if you don't find the daws saved file seems to be a write protection issue. to be sure... send me the dcs.log (you might see a VFS error or something similar about writing something)

yeah you found a bug due to new timing system. As it's corrected I will post. Currently any mission would start after midnight if "keepcontinous" is not chosen.

No, can you please send me the mission you're using? Any other mods? Does the save thing works anyway?

Is your main folder protected? if so, it wont' work.

hai ragione, anche noi abbiamo oramai adottato ufficialmente l'UH-1H, CA per i JTAC e siamo in sperimentazione con l'hornet. ma il post è di Khamul, penso possa editarlo solo lui ed i moderatori. I moderatori potrebbero recepire eventuali richieste di variazione da parte dei singoli gruppi? Poi se uno non vuole aggiornare amen.

good point. I will add a third option with random starting hour between 8:00 and 15:00 (always the day after).

Nono, only how to solve the double mission load trick necessary for weather update ;)

that's the point. I'm trying also to solve in the How To forum... let's see if someone can help

Hello everyone. Given a mission loaded on a server, let's say "testmission.miz", I need to get this after "n" hour of execution: Step 1 - a custom mod edit "testmission.miz", change things and save as "testmission_edited.miz" Step 2 - server stops by custom hooks code; Step 3 - custom hooks code delete testmission.miz and rename testmission_edited.miz in testmission.miz Step 4 - custom hooks code load again "testmission.miz" (which has been edited) Well, DAWS provide step 1, other step are ok if: 1) I don't stop the server 2) I don't try to delete/overwrite/rename "testmission.miz" (cause it's used by DCS). If I stop the server, any reload thing makes DCS crash Do you know a way to perform those steps without external program, using DCS SSE & API lua code? thanks, it's important for future persistent server mod developement.

1) ok 2) it's in the special options: check "create dead static object". it's flagged by default, if you want to remove 3) it's in the special options: check manual to disable aicraft deletion by remove the check in "remove dead planes & helicopter when dead" (the wreckage will be there anyway if create static is checked); 4) you can't, as also every auto restart file will be named "DAWS_Reload_a" and "DAWS_Reload_b" or something similar. You might tell the mission name not using the file but in the mission description. 5) No, I don't thing DAWS could interact in such way inside the sim engine. For any doubt I'm here and thanks for the feedback :) EDIT: I would really like to overcome that odd "auto rename file" issue, but I can't cause the point that when a mission is loaded (let's say "gnagna.miz") I can't touch that file cause windows and DCS say it's currently in use. I was thinking to create a simple function that will rename the autosave file and the normal saved file keeping the original name and adding a _DAWSautosave or _DAWSsave## (#=number) in the next release but it won't save me from the server reload issue.

i.e., me. I'm not voting "no", but I vote that I prefer to see helos (AH-1) before F-4E. I might tell plenty of reasons (one for example is that currently with the situation of Ka-50 we don't have a real attack helo fully and correctly working) As far as you create a poll, you will see how most of the people think.. and you might notice that even if F-4 is a really great and iconic aiframe... many won't it before everything else. And you won't consider all those people that are even not interested in voting about the F-4 or reading this thread about it.

Tutti lo preferiscono. I primi tempi (anche anni). Poi ci si rende conto che magari per fare A/A è la stessa roba, ma per AG ed integrazione con lo scenario di terra è su un'altro livello... di dettaglio, di complessità e di grandissime rotture di c. per ottenere quello che vuoi... nonchè di tempo perso. Il vero problema è che se vuoi poter sfruttare decentemente l'editor di DCS serve avere conoscenze basilari di lua (molto basilari) e usare strumenti come MIST e MOOSE. Poi se vuoi ci sono anche codici già pronti e seguiti per determinate funzioni, tipo CTLD e DAWS, che possono essere usati per semplificare in maniera significativa il tempo necessario all'editing o aggiungere funzioni che sostanzialmente non sono presenti.

Planned one is an S.

Per ottenere un TOT preciso è sufficiente: - creare un WPT a poche centinaia di metri dall'aeroporto, mettendo un tempo di sorvolo definito (i.e. ora di decollo desiderato) - creare un WPT sul punto in cui si desidera TOT con flaggata l'ora desiderata (e vi cancellerà il flag sulla velocità, calcolandola da sè) - creare i WPT intermedi levando le flag sia da tempo che da velocità. Così se le calcola da sè. - aggiustare il primo WPT in modo che la velocità su tutti gli altri (uguale) sia compatibile con il velivolo usato - Mettere il primo WPT in uncontrolled o late activation con tempo 5 minuti prima del WPT iniziale sopra creato. Così io fino alla 1.5 ho sempre ottenuto timings magari non perfetti ma ottimi. PS occhio che le velocità sono tutte ground speed, quindi fate attenzione che le velocità calcolate per i velivoli siano compatibili con il velivolo in questione (Se no fa casino... ma dopo un po' vi trovate delle velocità standard tipo 550 per i caccia e 450 per gli A-10 e via così)

It is. The link is the same as DAWS Package: https://forums.eagle.ru/showpost.php?p=3229846&postcount=1

+1 How should I do that?

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.