[DCE Campaigns]

strange

Download this file if you can:

 

 

 

 

https://www.dropbox.com/s/9drtz3yd29mv5j5/ATO_Generator.lua?dl=0

[DCE Campaigns]

Hi Folks,

 

Hope that I am i the right Forum and someone can help me. My issue relates to the F18 Module in connection with the DCE campaigns.

 

I finished a campaign mission and press ESC and „Quit“. For the Harrier or Tomcat DCE Campaigns everything works as expected after that which means that the Standard DCS de-Briefing screen will be displayed where I can see my mission results. At the same time the DOS window open where I can accept the mission results (or not) and the text editor also with the mission results.

 

Unfortunately this does not work in the F18 Hornet DCE Campaigns and I do not now why. When I finished a mission and press ESC and „Quit“ I see the black loading screen with the DCS Logo. In the background the DOS window and the Text file from the DCE Campaigns opens as well but that‘s it. I can accept the mission and DCE generates a new one. But I cannot press the „End Mission“ Button as i do not see it but only the Black Screen. The Game will not continue and I Need to restart DCS. I thought that maybe I accept the mission, generate a new one and restart DCS May help but unfortunately not. I still can only play the mission I flew last also DCE generate a new one.

 

As said before this only applies to the DCE campaign and F18. All other DCS modules work perfectly with the DCE Campaigns. I also do not have this issue in Single missions or the static Campaigns for the F18, i.e. Everything works perfectly there. Thus and in my opinion this must relate to the DCE Campaign. I also re-installed the Campaigns but nothing helped. I Play the DCE campaigns in the latest version actualy published on the website.

 

Hope someone has an idea as I Love the Dynamic Campaigns (and the Hornet) very much.

 

Thank you all in advance and Kind regards.

 

Hummersepp

 

 

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 )

[DCE Campaigns]

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)

[DCE Campaigns]

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

 

 

 

 

not activate the random failures

This is normal:

[DCE Campaigns]

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

[DCE Campaigns]

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

To use with any s11.0.4 or s11.0.5 version (not for s11.0.7 ! )

 

Installation :

 

 

- Extract "Images", "Init" and "Scripts" folders in all V20 campaigns (erase old files)

 

- After that extract "base_mission.lua" files in the good theater PG or Caucasus "Init" folder

 

- Finally if you use "IRIAF Tomcat over PG" campaign extract "db_loadouts.lua" file in this campaign "Init" folder

 

 

After that you only need to use Skipmission.bat file if you have a campaign running or FirstMission.bat if you want to restart a new one.

[DCE Campaigns]

It looks like with latest OB, wingman gets dumb again and unable to taxi on the carrier.

Whenerver and wherever you start moving, the wingman will move forward couple meters and then get stuck forever. I.e. until the end of the mission. Abort takeoff doesn't help.

 

 

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)

[DCE Campaigns]

THIS NEEDS TO STOP!

 

 

it will be nice to hear that ^^

 

 

 

Then we need a rallying cry. I would love to set a 10 percent blanket failure on all systems from the ramp. IRL the plane is not perfect and in a war zone less so.

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

[DCE Campaigns]

Is there any way to add random failures in without having to go in and hit the random button on the mission editor?

 

 

No, not yet, but if it interress several people, I think Cef will be happy to add this option...:pilotfly:

[DCE Campaigns]

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