Miguel21
-
Posts
943 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Miguel21
-
I think I found part of your problem, when you edited the.cmp file, you "truncated" the end of the main lines, these lines must end with : ", If this still doesn't work, post here the DCS log file. Be careful, when editing.lua or.cmp files, always use notepad++ and make sure that the encoding remains in UTF8 However, there are still some points to be clarified regarding the F-16, I think that if you enable random failures in DCE, it will not work, you should modify the Init\base_mission.miz I modified your.cmd file: https://www.dropbox.com/s/d6mhc84tx1tjtbd/Falcon%20over%20PG.cmp?dl=0 Translated with www.DeepL.com/Translator
-
Hi, We will already try to integrate the LSO script in a future release.
-
Almost everything is configurable in the Init/conf_mod.lua file To activate the labels: Line 35: ["labels"] = 0, 0 or 1, or 2, or 2, or 3 The PruneScript options have also been deported to conf_mod.lua, line 10 to 13 Place: PruneScript = true, and PruneStatic = true,
-
We're looking for... ^^ I didn't follow, did someone give the "exact" name of the F-16 file? such as the one in F-14 DCS World OpenBeta\Mods\aircraft\F14 or Harrier DCS World OpenBeta\Mods\aircraft\AV8BN Thanks
-
No, not the one of the CEF campaign, but the one (if there is one) of the "official" F-16 DCS campaign
-
If you have a.cmd file concerning an original F-16 campaign in (for example) Missions\Campaigns Can you post this.cmd file here Thank you. Thank you.
-
Hi;) I "hid" the failure lines during mission generation, because we're not supposed to know our future failures^^ If you want the credits, remove the 2 characters "--" in front of line 83 of Scripts\ATO_FlightPlan.lua You must also select in Init\conf_mod.lua: line 19 failure = true, ATTENTION, these changes are made with notepad++ AND checking that the encoding of the .lua file(s) remains in UTF8 (or possibly in ANSI, but here I have a doubt)
-
Otherwise, while waiting to fix this end-of-mission problem, you can continue the campaign by using : DEBUG_DebriefMission.lua
-
Can you see that the encoding of the DCS World OpenBeta\Scripts\MissionScripting file is in utf-8 (as well as all LUA files that you have modified in DCE) You can see it with notepad++ EDIT: 2nd possibility: Disable your anti-virus to fly and generate your next mission with SkipMission.bat
-
We are working on it, but Cef is busy elsewhere, for now.
-
Ok, so I'll put the option ^ ^
-
Hi Tomsk, thanks again for your script;) Actually, we changed different things on 11.0.7, and it does not work as we would like ... We are currently working on 11.0.8 to correct that. We have, for the moment, mainly 2 problems: - The planes planned to take off later on CVN are already in flight and go around in circles. - Cef wanted the "static" planes to not be disabled, as it was the target of some bombers.
-
Hello What plane? What a campaign Which version of script? Thanks
-
Can you send me the log of dcs after crash : For example, here: wetransfer.com
-
like this?: https://forums.eagle.ru/showpost.php?p=4019029&postcount=773
-
Hi This is normal, it means that you have "commented" the line and it is no longer "active" for the script. If you don't want to do this manipulation with each update of DCS, I propose to use OvGME or JSGME as indicated in the readme
-
Very very strange your problem .... Until we find a solution, after each mission you can launch DEBUG_DebriefMission This creates your DCE debriefing and generates a new mission.
-
OK Normally, you only have to add the 2 dashes once. Then they must stay in place. If you have to add them every time, it's because a process prevents you from writing to the file. Or, I did not understand everything.
-
To be clear, and for all DCE campaigns it is necessary that: in DCS World OpenBeta\Scripts\MissionScripting.lua (if you play with OpenBeta) or in DCS World\Scripts\MissionScripting.lua (if you play with DCS World) There is this: [b]--[/b]sanitizeModule ( 'OS') [b]--[/b]sanitizeModule ('io') sanitizeModule ( 'lfs') require = nil loadlib = nilMandatory. Otherwise, you get the error message at the end of each mission. I don't think I can be clearer ...
-
activate the "Prune" option in Init/conf_mod.lua Like this: -- mod Tomsk V9 Integration de Prune Script PruneScript ={ present = true, -- reduce a mission by removing units }
-
you added the - - recently? Rename your file in .lua and not in .lua.txt The good paths is C:\program files\eagle dynamics\dcs open beta\Scripts And not C:\program files\eagle dynamics\dcs open beta\scripts Now it should work only when you play OpenBeta
-
I confirm that it is a problem of DCE_Missionscript_mod incorrectly installed -1- give me the exact path of your MissionScripting.lua file -2- make me here a copy of the file MissionScripting.lua -3- Do you play on the OpenBeta or DCS world?
-
Yes, a screen plz ;)
-
Is it really a log dcs following the end mission crash? Moreover, we do not see the entire log, I need you post on a sharing site and you give the link here. Finally, I read again your problem and for me, although DCS crashes, the new mission DCE has been well generated. The first and the second mission already exists (campaign_first.miz, campaign_ongoing.miz), after a mission, look at the dates of creation in windows, campaign_ongoing.miz must have changed date and time of creation To reveal the bug, you do not have to complete a mission, you can launch the mission and leave it after 5 to 15 minutes.
-
Hello ;) If you have the error box: You did not install the DCE_Missionscript_mod or you have installed the wrong place or the OpenBeta updates we broke In all cases, the file DCS World OpenBeta\Scripts\MissionScripting.lua Must have --sanitizeModule('os') --sanitizeModule('io') sanitizeModule('lfs') require = nil loadlib = nil
