Jump to content

Small issue with table saving inside miz file...


Recommended Posts

Posted

... I managed to save table files into the .miz archive in DAWS save mission. This was a key needs to achieve some future improvements. Now, I need to find a way to load those file, if present, each mission start and mostly to avoid them to be removed from the .miz file while editing the mission in the ME.

 

I got a solution if I load the saved (by DAWS) .miz file in multiplayer. But still:

 

1. If I edit and save the saved .miz file in the ME, the ME will delete my custom tables.

2. If I load the saved .miz file in the ME, it will use the "tempMission.miz" file created in the local appdata folder, not using the custom tables

 

Any suggestion to preserve my custom files to be deleted inside the MIZ archive?

 

(attached an example mission, you will see it contains a "DAWS-------" file inside the archive. If you load and save it in the ME, it will delete that file).

DAWS-SavedMission_1.miz

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.

Posted
... I managed to save table files into the .miz archive in DAWS save mission. This was a key needs to achieve some future improvements. Now, I need to find a way to load those file, if present, each mission start and mostly to avoid them to be removed from the .miz file while editing the mission in the ME.

 

I got a solution if I load the saved (by DAWS) .miz file in multiplayer. But still:

 

1. If I edit and save the saved .miz file in the ME, the ME will delete my custom tables.

2. If I load the saved .miz file in the ME, it will use the "tempMission.miz" file created in the local appdata folder, not using the custom tables

 

Any suggestion to preserve my custom files to be deleted inside the MIZ archive?

 

(attached an example mission, you will see it contains a "DAWS-------" file inside the archive. If you load and save it in the ME, it will delete that file).

 

Only way I could see of doing it, is similar to putting a place holder in the trigger system for sound files that are used in custom .lua scripts so they aren't discarded on mission editing.

 

This may work if you can have your table with a .lua extension, not sure how you or why you are using a table ???

 

Trigger -> Condition -> Action

=======================

Table ---> Random (0) -> Do Script file (DAWS_mountedInfantryTable_SM.lua)

 

Regards, Ian

Asus p877v-pro, Intel I7 3770k 4.2ghz, 32gb Ripjaw X ram, Nvidia RTX-2070 Super, Samsung 32" TV, Saitek x52 pro Joystick and Combat rudder pedals, TrackIR 5, Win8.1 x64 with SSD and SSHD protected by (Avast AV).

 

DCS Tech Support.

Posted

I can Have that extension whitout issue. But It's difficult to create triggers by script

 

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.

Posted
I can Have that extension wihtout issue.

 

But It's difficult to create triggers by script

 

 

I don't fully understand what you are getting at or trying to do.

 

I was talking about just making a trigger within the mission editor that never activates anything in the mission but references the DAWS file as a .lua and acts as a placeholder for the file. This way the ME sanitizer will not delete the DAWS file from the .miz file.

 

Sample .miz file of my idea supplied.

 

Question about that DAWS file, do you:

 

  • Somehow inject that file into the .miz file with an external source on each play of the mission in a server ????
  • Does in only have to be included with the original mission file and never changes ???
  • What does the table do, and what references its contents ???

Regards, Ian

DAWS-SavedMission_1 with table.miz

Asus p877v-pro, Intel I7 3770k 4.2ghz, 32gb Ripjaw X ram, Nvidia RTX-2070 Super, Samsung 32" TV, Saitek x52 pro Joystick and Combat rudder pedals, TrackIR 5, Win8.1 x64 with SSD and SSHD protected by (Avast AV).

 

DCS Tech Support.

Posted

DAWS Save Mission isa mod that save the scenery in its current situation while the server is running.. but "Save Mission" is only a part of a package I'm working on. One of the main thing I need to achieve is to achieve persistency of some simulation information created by the additional modules of DAWS. This is suitable saving inside the miz archive some files that contain lua tables. Those tables will contain information created by additional modules (done). Those files should be checked and loaded each time the mission is loaded in presence of DAWS code (done also).

 

Details my be complicated to explain now: the files that is inside the miz archive uploaded yesterday is a table of dismount spawnable units associated to some units in the scenery relying on a modification of MBot dismount script. My modification will randomly add the dismount property to units that could carry personnel whitout having to use Editor, and I want those information to be kept from mission to mission.

 

Now the issue is simple: the file that is saved inside the newly created .miz file during the simulation are removed any time you use the Mission Editor and anytime you try to load the mission in single player. It will work only loading the saved file in a multiplayer environment whitout modification. I need to overcome this issue and I need to overcome it whitout having to do nothing in the ME or everywhere else.

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.

Posted

Found a solution, created an issue XD: If I save the file inside the "Scripts" subfolder into the miz archive, it isn't removed. But I'm having trouble saving the code right there XD. Anyway, I'll figure this out for sure :)

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.

Posted
Found a solution, created an issue XD: If I save the file inside the "Scripts" subfolder into the miz archive, it isn't removed. But I'm having trouble saving the code right there XD. Anyway, I'll figure this out for sure :)

 

It may sound bazar, but I thought about doing it that way last night whilst I couldn't go to sleep, using one of the directories that the prepare mission option creates, such as scripts, etc.

 

I guess great minds think alike, all the best for getting it sorted.:detective:

 

Regards, Ian.

Asus p877v-pro, Intel I7 3770k 4.2ghz, 32gb Ripjaw X ram, Nvidia RTX-2070 Super, Samsung 32" TV, Saitek x52 pro Joystick and Combat rudder pedals, TrackIR 5, Win8.1 x64 with SSD and SSHD protected by (Avast AV).

 

DCS Tech Support.

Posted

ahahahah XD

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.

  • Recently Browsing   0 members

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