Miguel21
-
Posts
952 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Miguel21
-
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
-
Glad it's finally working ... ^^ Good flight with DCE :pilotfly:
-
It's a shame to have to restart the campaign at the beginning, I hope you saved it;) I think you have an encoding problem with Notepad + https://scriptinghelpers.org/questions/68044/unexpected-symbol-near-how-to-fix
-
If the DOS window closes without giving any info, you have to right click on the file firstmission.bat (and skipmission.bat) edit with notepad, delete the word "& exit" start "Generate First Mission" cmd / k ".. \ .. \ .. \ .. \ .. \ .. \ .. \ bin \ luae.exe Scripts / BAT_FirstMission.lua & exit" like this start "Generate First Mission" cmd / k ".. \ .. \ .. \ .. \ .. \ .. \ .. \ bin \ luae.exe Scripts / BAT_FirstMission.lua" saves Sorry for the file above, I juggle with a script exclusively for you and the same script (modified) for DCE
-
Oups, bad file, Upload a new file https://www.dropbox.com/s/qk13ckkf7vkquoa/ATO_Generator.lua?dl=0
-
Haha, pretty the formalism of DCS, you think it's always the same way, well no ... ^^ Most failures have a resumed identifier (ID) and others, no ... So reload the file and it should do it, sorry for the tests ... EDIT: new file https://www.dropbox.com/s/qk13ckkf7vkquoa/ATO_Generator.lua?dl=0
-
strange Download this file if you can: https://www.dropbox.com/s/9drtz3yd29mv5j5/ATO_Generator.lua?dl=0
-
Can you post the log of dcs following the crash of your end of mission Then, can you give us the version of the campaign and especially the version of the script? (S11.0.7?) Finally, when the mission generation fails at the end of a mission, you can relaunch it via DEBUG_DebriefMission.bat ( It takes the temporary files of your last mission into account : camp_status MissionEventslog Scen_destroyed )
-
Ok, change these lignes local id_failed = math.random(0, n) local m = 0 Like this local id_failed = math.random(1, n) local m = 1 Then generate a new mission with SkipMission.bat If it starts again, copy here the line incriminated by the error (In your case, the error was on line 44 of ATO_Generator.lua)
-
If you see failure lines at mission generation, it should work To be sure it works in flight, for your first mission: adjust the values: failureProbMax = 100, failureNbMax = 10, It would be very surprising that you have no breakdown in flight :) This is normal:
-
temp = { failure = true, -- (true or false) Miguel21 modification M20 failureProbMax = 100, -- (1 à 100)probabilité maximum sur une panne -- Miguel21 modification M20 failureNbMax = 10 , -- ( 1 à ...57?) nombre de panne maximum par mission --Miguel21 modification M20 } if not mission.forcedOptions then mission.forcedOptions = {} end mission.forcedOptions.accidental_failures = true if temp.failure and not coopFlag01 then -- not multiplayer local n= 0 for _id, failure in pairs(mission.failures) do n = n+1 end for f = 1, temp.failureNbMax do local hh = math.random(0, 1) local mm = math.random(1, 59) local prob = math.random(1, temp.failureProbMax) local mmint = math.random(1, 59) local id_failed = math.random(1, n) -- print("numeroPanne "..id_failed) local m = 1 for _id, failure in pairs(mission.failures) do if id_failed == m then mission.failures[_id]['hh'] = hh mission.failures[_id]['mm'] = mm mission.failures[_id]['prob'] = prob mission.failures[_id]['enable'] = true mission.failures[_id]['mmint'] = mmint print("NouvellePanne ".._id.." "..hh.."H"..mm.." ".." Duration "..mmint.." Prob: "..prob) end m = m+1 end end end
-
S11.0.4 ???? it still exists ??? ^^ If it does not work with the last OB, I strongly advise you to install S11.0.7 EDIT: https://forums.eagle.ru/showpost.php?p=3984603&postcount=695 https://www.dropbox.com/s/5k3swyk6ms7ch1h/ScriptMods-AD-S11.0.7.zip?dl=0
-
On one of our test campaigns in F-14, it works very well. Which campaign, what aircraft, which version of the campaign and which version of the script are you talking about? Last point: did yesterday's patch solve your problem? (DCS 2.5.5.34864 Open Beta hotfix)
-
it will be nice to hear that ^^ Are you able to wait a month or two? If not, I have 2 quick fixes: One especially for you: ****************************************************** ATTENTION, I did not test anything, so ... before changing anything, save your campaign. ****************************************************** It is necessary to change with notepad ++ the file "mission" in Init \ base_mission.miz Find the chapter ['failures'] = { And change the values you want, as in the mission editor: Normally, you will always have the same values for each mission generation ['failures'] = { ['Failure_Fuel_Tank1Transfer'] = { ['hh'] = 0, ['prob'] = 100, ['id'] = 'Failure_Fuel_Tank1Transfer', ['mmint'] = 1, ['enable'] = false, ['mm'] = 0, }, ['Failure_Ctrl_Aileron'] = { ['hh'] = 0, ['prob'] = 10, ['id'] = 'Failure_Ctrl_Aileron', ['mmint'] = 5, ['enable'] = true, ['mm'] = 17, }, ['Failure_Ctrl_FCS_Ch3'] = { ['hh'] = 0, ['prob'] = 100, ['id'] = 'Failure_Ctrl_FCS_Ch3', ['mmint'] = 1, ['enable'] = false, ['mm'] = 0, }, EDIT: And you must add this line (["accidental_failures"] = true,) in the mission file ["forcedOptions"] = { ["accidental_failures"] = true, }, Save mission And save base_mission.miz And generate a new mission The second is a script on random breakdowns, do you want to test it? But you can't specifically choose one or more Failure ****************************************************** BUT ATTENTION, I did not test anything, so ... before changing anything, save your campaign. ****************************************************** PS: I think the failures do not work in multiplayer
-
No, not yet, but if it interress several people, I think Cef will be happy to add this option...:pilotfly:
-
To increase the chances of being in the same package, you have to choose For the flight 1 A task asking for support So that the flight 2 can provide a task support So, concretely, in your case: F-14: select Strike f-15: The script found me a mission after 3 tries. if it still does not work, I would have another more radical solution, but that CEF will not approve ... ^^
