Jump to content

DAWS Save Mission


chromium
 Share

Recommended Posts

Meeeeehhhh i'm almost sure that daws is loaded after mission start :(

 

Inviato dal mio SM-G920F 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

  • Replies 442
  • Created
  • Last Reply

Top Posters In This Topic

Yes if possibile

 

Inviato dal mio SM-G920F 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'll get that to you, i found some other things.

1. So DAWS loads around 4 seconds before mission start and looks for Mist and cannot find it (Mission environment hasn't been created)

2. After mission start DAWS tried to load MIST, but its around a second too late if you run something immediately. But here's the weird thing... if you run a MIST command immediately...it cannot find Mist.

3. You can delay the running of Mist by a seocnd or two and then it loads and runs fine.

 

So it seems there are some timing challenges there.

 

I'm going back to the mist error on zones now, since I used teleport in zone initially and that worked. But recently it was mist's mist.dynAddStatic() that produced the zone error and I need to work out if there is a timing issue there originally too.

Yes if possibile

 

Inviato dal mio SM-G920F utilizzando Tapatalk

Capture.thumb.JPG.1f072d68ae3306c2b14bc18b19fa45cf.JPG

___________________________________________________________________________

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

Link to comment
Share on other sites

OK, attached is a mission you can use for testing. Unfortunately the issue is more widespread than MIST, it affects MOOSE also and can range from errors to immediate crashes without a dump. So this is quite severe. It seems to affect anything looking for a vector 2/3 coord and zones. I don't even have a guess as to why.

 

TEST PROCESS

 

1. Unload DAWS and load the mission attached.

2. When loaded, enter vehicle, press tab, see an F10 menu with three options:

a) MOOSE - smoke in Polygon zone

b) MIST creatic static

c) MIST teleport unit

 

A) press this and see orange smoke appear in the polygon zone in front of the unit

B) Press this and see a Comms tower appear in a random location in the poly zone

C) Press this and see the tank in front of you teleport to a random place inside a traditional zone.

Quit and load the DAWS package

 

Repeat the tests. I recommend reverse order!

C) The DCS.log will give "attempt to index local 'zone' (a nil value)"

B) Nothing happens (if you are lucky)

A) DCS will crash.

 

You can optionally unload the added MIST, I didn't test this.

 

Hope this helps, took ages. DAWS is critical for work i am doing so I hope you get lucky.

DAWStest.miz

___________________________________________________________________________

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

Link to comment
Share on other sites

Pikey, 2 things:

1. never load mist after daws. as mist do not have a self-present check, you will overwrite it and this is bad. I'm trying to manage to load mist exactly at mission start.

2. that 120 sec was a refuse, the actual code load mist at timer.getTime() + 1 which seems to be 1 sec after mission start (can't understand why honestly). If I correctly understood, your teleport command from the previous post was at mission start, 1s earlier than DAWS. I modified in +0 now but I might need from you the miz file of the previous issue to test it.

 

About the severe bug: I can reproduce, but I can't understand... probably is due to something ongoing with original files modified by DAWS, which are still before the last stable release.

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

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

 

T it does not work with teleport to me.

Link to comment
Share on other sites

Canon You send me the log?

 

Inviato dal mio SM-G920F 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 can switch them around or remove MIST seperately, it's the same result. I don't know either, I don't even have a guess why.

 

Pikey, 2 things:

1. never load mist after daws. as mist do not have a self-present check, you will overwrite it and this is bad. I'm trying to manage to load mist exactly at mission start.

2. that 120 sec was a refuse, the actual code load mist at timer.getTime() + 1 which seems to be 1 sec after mission start (can't understand why honestly). If I correctly understood, your teleport command from the previous post was at mission start, 1s earlier than DAWS. I modified in +0 now but I might need from you the miz file of the previous issue to test it.

 

About the severe bug: I can reproduce, but I can't understand... probably is due to something ongoing with original files modified by DAWS, which are still before the last stable release.

___________________________________________________________________________

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

Link to comment
Share on other sites

Pikey, I finally tried your mission test whitout daws. It worked as you said , but Still there is this error while loading:

 

00092.236 INFO    SCRIPTING: *** MOOSE INCLUDE END *** 
00092.243 INFO    SCRIPTING: Mist version 4.3.74 loaded.
00137.940 INFO    SCRIPTING:   4791(    13)/E:               EVENT00000.onEvent(S_EVENT_BIRTH)
00137.940 INFO    SCRIPTING: Static moved
00146.007 ERROR   DCS: Mission script error: : [string "C:\Users\loren\AppData\Local\Temp\DCS\/~mis0000657F"]:3348: attempt to index local 'zone' (a nil value)
stack traceback:
[C]: ?
[string "C:\Users\loren\AppData\Local\Temp\DCS\/~mis0000657F"]:3348: in function 'teleportInZone'
[string "mist.teleportInZone ("group", "z1", true, 100)..."]:1: in main chunk

 

This is your mission, whitout mods and DAWS.

Can you confirm?

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 think there is a typo with the zone name in the 3rd test, change the zone name to the same name or change the z1 to g1. Either way, it moves the vehicle to a random place in the zone without DAWS and crashes with DAWS. Let me know if you need any more info. I'm out of ideas.

Pikey, I finally tried your mission test whitout daws. It worked as you said , but Still there is this error while loading:

 

00092.236 INFO    SCRIPTING: *** MOOSE INCLUDE END *** 
00092.243 INFO    SCRIPTING: Mist version 4.3.74 loaded.
00137.940 INFO    SCRIPTING:   4791(    13)/E:               EVENT00000.onEvent(S_EVENT_BIRTH)
00137.940 INFO    SCRIPTING: Static moved
00146.007 ERROR   DCS: Mission script error: : [string "C:\Users\loren\AppData\Local\Temp\DCS\/~mis0000657F"]:3348: attempt to index local 'zone' (a nil value)
stack traceback:
   [C]: ?
   [string "C:\Users\loren\AppData\Local\Temp\DCS\/~mis0000657F"]:3348: in function 'teleportInZone'
   [string "mist.teleportInZone ("group", "z1", true, 100)..."]:1: in main chunk

This is your mission, whitout mods and DAWS.

Can you confirm?

___________________________________________________________________________

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

Link to comment
Share on other sites

Ok I'm back.

I'm going to proceed in this way:

 

1. Try to solve the teleport issue ESAC_Matador has. Please send me the miz file, so that I can test in proper conditions.

 

2. As DAWS Package do not cause crashes alone, but only if coupled with moose in your mission, I can't assume that the issue is about DAWS. It could be about MOOSE also. So once solved the timing/teleport issue of Matador I'll retest again and if the issue is still there I will write to Flightcontrol to try to do something together cause I have no clue of what it's going on that could cause a crash: I'm not a programmer and I don't have sufficient knowledge.

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 am using Mist, not Moose.

 

I lo try to send everything tonight, mission and log.

 

I understand, but Pikey is using Moose, I think that there are different issues, and I'm hoping to solve those that belongs entirely to DAWS code.

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

Thank You i'll look asap:)

 

Inviato dal mio SM-G920F 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

Sad update.

Bug confirmed. There is something DAWS related, that I can't understand, that prevent clone & teleport function of mist to work properly. I'm investigating it.... I also tried to "separe" mist and DAWS mist by renaming the mist function, so that you can run mist & DAWS together.... but mist itself seems to get corrupted by DAWS install for those functions.

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

Just want to offer a word of thanks and encouragement Chromium. I really appreciate the work you're doing here mate - this will be a huge game changer. Keep up the great work!

 

Thanks.

But I have to say that it's hard. I'm literally trying to understand WTF could be in DAWS that prevent SSE function "trigger.misc.getZone" to work as expected, because it's likely that the main issue that cause mist teleport & clone and moose also is there... or near there.

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. I found that the issue-creating code isn't in Save Mission module but in AI enhancement module, and it's there even if none of the AI enhancement feature is active.

 

I was thinking to release a new beta, whitout AI enhancement, yesterday evening... but sadly I found that for some unknown reason the Save Mission code is unable to index the dictionary file anymore, creating weird issue in the saved mission. Once solved that thing, I will post an update.

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

Hate to ask and I am sure it is in this thread somewhere, but, is the CTLD thing still a bug? :(

Don't think so. CTD's are a DCS thing only, it should handle all script errors gracefully.

 

Hope you are getting closer to it Chromium! Good luck, its not an easy one for sure.

___________________________________________________________________________

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

Link to comment
Share on other sites

Don't think so. CTD's are a DCS thing only, it should handle all script errors gracefully.

 

Hope you are getting closer to it Chromium! Good luck, its not an easy one for sure.

 

I am sorry, didn't clarify. The Complete Transport and Logistics Deployment (CTLD) Script.

 

I use the script in almost all my missions and sadly, and I mean sadly, I can't seem to get DAWS to work with it.

Link to comment
Share on other sites

CTLD bug is related to mist clone & teleport bug. Anyway as said above DAWS can't be used till bugs are solved.

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

 Share

  • Recently Browsing   0 members

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