Miguel21

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