DCE Campaigns

Ok

It happens when you use Firstmission.bat after adapting files to OpenBeta ?

Changed in all 3 files path to openbeta.

Firstmission.bat - mission generated

When mission is over I see attached error.

And same thing in DEBUG_DebriefMission

D:\DCS World OpenBeta\bin\luae.exe: ..\..\..\ScriptsMod\Debrief_Master.lua:43: attempt to call a nil value

stack traceback:

..\..\..\ScriptsMod\Debrief_Master.lua:43: in main chunk

[C]: ?

C:\Users\sikor\Saved Games\DCS.openbeta\Mods\tech\DCE\Missions\Campaigns\Falcon over PG>

For Hornet i can fly mission and finish it without any errors, at the end I see file with summary.

Changed in all 3 files path to openbeta.

Firstmission.bat - mission generated

When mission is over I see attached error.

And same thing in DEBUG_DebriefMission

D:\DCS World OpenBeta\bin\luae.exe: ..\..\..\ScriptsMod\Debrief_Master.lua:43: attempt to call a nil value

stack traceback:

..\..\..\ScriptsMod\Debrief_Master.lua:43: in main chunk

[C]: ?

 

C:\Users\sikor\Saved Games\DCS.openbeta\Mods\tech\DCE\Missions\Campaigns\Falcon over PG>

 

 

For Hornet i can fly mission and finish it without any errors, at the end I see file with summary.

Hum... I'm not the Code specialist :( Miguel is sleeping I think :smilewink:

but it could be a writing permission in your folders ...

Can you verify if you are in read only with Falcon campaign folders please ?

MissionEventLog.lua Not Found?

Changed in all 3 files path to openbeta.

Firstmission.bat - mission generated

When mission is over I see attached error.

And same thing in DEBUG_DebriefMission

D:\DCS World OpenBeta\bin\luae.exe: ..\..\..\ScriptsMod\Debrief_Master.lua:43: attempt to call a nil value

stack traceback:

..\..\..\ScriptsMod\Debrief_Master.lua:43: in main chunk

[C]: ?

 

C:\Users\sikor\Saved Games\DCS.openbeta\Mods\tech\DCE\Missions\Campaigns\Falcon over PG>

 

 

For Hornet i can fly mission and finish it without any errors, at the end I see file with summary.

Good morning everyone,

by the way, you are really taking campaign on a new whole level with this great job.

I have the exact same problem starting from yesterday when I tried the Harrier PG campaign, it was a while that I wasn't playing, so I checked also the other (TF-74 Tomcat and Hornet), they have the exact same problem.

I made some investigation and the problem seems that the script cannot find the file "MissionEventsLog.lua".

The problems, to me, happens when I exit the mission and later, of course, if I try to launch the DEBUG_DebriefMission bat file.

I tried to look around on the drives, in fact the files seem to not exists, I am not sure if it is generated by DCS or by DCE.

For info, I am using it on DCS Openbeta, before, making the appropriate changing the TF-74 was working.

Thanks for the help.

Fly safe.

Nicola

but it could be a writing permission in your folders ...

Can you verify if you are in read only with Falcon campaign folders please ?

Yup, read only, same like for Hornet and Tomcat:joystick:

Yup, read only, same like for Hornet and Tomcat:joystick:

Ok can you do a simple verification :

- Start the a campaign mission

- Stop it

- before accepting result and generating a new mission look in your Falcon over PG folder : there should be 3 other files than the usual Debug, Firstmission.bat and Skipmission.bat

MissionEventsLog.lua for example ...

If this file is missing at this moment it's a bug and You will have to wait for Miguel21 to look at this because I really don't know why it doens't work :( My version I uploaded is working fine ! :doh:

It really could be a writing permission or a wrong path but all seems good ...

Can you please try to compare paths on working and not working campaigns very carefully ? :huh:

Miguel, p80 - thanks so much. Ive been having the best time.

Especially the IRIAF F14 camp.. Ive been getting the hell beaten out of me but I had two glorious succesful missions I survived. Both ironically night ones. One was so dark I had to use the NVG and I jumped some Viggens. Shot one down, friendly flights each got one. Ruined their night.

The last mission was one of those great nights where you can see well out the cockpit. I got scrambled. The BRA calls... the enemy wasnt there. There was a naval package clearly coming in. I started heading there but the EWR kept insisting someone was near me.. and my home base. I turned back.. and kept looking.

Well I ended up coming up on a 4 ship of F16s doing a strike. Idk what their target was but they were very near Lar and that mountainous area. So when my AWG9 saw them - they were low and I was too and it was close.

2 died to phoenixes. Another ate a sidewinder. I was pretty proud of myself at this point. Suddenly I was closing on the last, spotted him, and a friendly sam helped me out.

I landed and obviously combed my handlebar moustache whilst wearing my aviator sunglasses.

Miguel, p80 - thanks so much. Ive been having the best time.

Especially the IRIAF F14 camp.. Ive been getting the hell beaten out of me but I had two glorious succesful missions I survived. Both ironically night ones. One was so dark I had to use the NVG and I jumped some Viggens. Shot one down, friendly flights each got one. Ruined their night.

The last mission was one of those great nights where you can see well out the cockpit. I got scrambled. The BRA calls... the enemy wasnt there. There was a naval package clearly coming in. I started heading there but the EWR kept insisting someone was near me.. and my home base. I turned back.. and kept looking.

Well I ended up coming up on a 4 ship of F16s doing a strike. Idk what their target was but they were very near Lar and that mountainous area. So when my AWG9 saw them - they were low and I was too and it was close.

2 died to phoenixes. Another ate a sidewinder. I was pretty proud of myself at this point. Suddenly I was closing on the last, spotted him, and a friendly sam helped me out.

I landed and obviously combed my handlebar moustache whilst wearing my aviator sunglasses.

Nice :thumbup:

Ok can you do a simple verification :

- Start the a campaign mission

 

- Stop it

 

- before accepting result and generating a new mission look in your Falcon over PG folder : there should be 3 other files than the usual Debug, Firstmission.bat and Skipmission.bat

 

MissionEventsLog.lua for example ...

 

 

If this file is missing at this moment it's a bug and You will have to wait for Miguel21 to look at this because I really don't know why it doens't work :( My version I uploaded is working fine ! :doh:

 

 

It really could be a writing permission or a wrong path but all seems good ...

Can you please try to compare paths on working and not working campaigns very carefully ? :huh:

One last thing to verify : did you use Notepad++ to adapt campaigns to OpenBeta with ANSI or UTF8 codification ? Please verify the files you modified : all other codification will not work !

Yes, I have Notpead++ :)

In Hornet folder i can see 3 more files, for Falcon they're missing.

Falcon First mission:

start "Generate First Mission" cmd /k ""D:\DCS World OpenBeta\bin\luae.exe" ..\..\..\ScriptsMod\BAT_FirstMission.lua"

Hornet Firstmission:

start "Generate First Mission" cmd /k ""D:\DCS World OpenBeta\bin\luae.exe" ..\..\..\ScriptsMod\BAT_FirstMission.lua"

The same issue with TF-74 Hornet campagin

Normal Hornet over PG is working fine

PS. Later i will try to delete everything again and try with Falcon only

Ok it doesn’t come from firstmission.bat file but there’s a problem with mission ending and generation of the files needed to prepare the next mission ...

You changed Camp_init.lua file too I suppose ?

Changed in all 3 files path to openbeta.

Firstmission.bat - mission generated

When mission is over I see attached error.

And same thing in DEBUG_DebriefMission

D:\DCS World OpenBeta\bin\luae.exe: ..\..\..\ScriptsMod\Debrief_Master.lua:43: attempt to call a nil value

stack traceback:

..\..\..\ScriptsMod\Debrief_Master.lua:43: in main chunk

[C]: ?

 

C:\Users\sikor\Saved Games\DCS.openbeta\Mods\tech\DCE\Missions\Campaigns\Falcon over PG>

 

 

For Hornet i can fly mission and finish it without any errors, at the end I see file with summary.

Hi,

Miguel's awake ^^

First of all, it's normal that DEBUG_DebriefMission doesn't work if it doesn't find the 3 temporary end of mission files, that's not the problem.

The problem (I think) is that the system can't find the path of campaign folder.

There are several reasons for this:

1-

--a/ the path in the camp_init file does not match your configuration

--b/ your installation of the campaign is badly done and does not correspond to the path of camp_init ^^

--c/ you moved the saved game to a different hard drive.

2- you didn't launch the firstmission.bat before you started the campaign.

3- The DCS World OPENBETA/Script/MissionScripting file has not been modified.

4- the MissionScripting file has been modified but is not in ANSI or UTF8

5- etc... ^^

PS: your Hornet and Tomcat campaigns are also good on OpenBeta?

Miguel, p80 - thanks so much. Ive been having the best time.

Especially the IRIAF F14 camp.. Ive been getting the hell beaten out of me but I had two glorious succesful missions I survived. Both ironically night ones. One was so dark I had to use the NVG and I jumped some Viggens. Shot one down, friendly flights each got one. Ruined their night.

The last mission was one of those great nights where you can see well out the cockpit. I got scrambled. The BRA calls... the enemy wasnt there. There was a naval package clearly coming in. I started heading there but the EWR kept insisting someone was near me.. and my home base. I turned back.. and kept looking.

Well I ended up coming up on a 4 ship of F16s doing a strike. Idk what their target was but they were very near Lar and that mountainous area. So when my AWG9 saw them - they were low and I was too and it was close.

2 died to phoenixes. Another ate a sidewinder. I was pretty proud of myself at this point. Suddenly I was closing on the last, spotted him, and a friendly sam helped me out.

I landed and obviously combed my handlebar moustache whilst wearing my aviator sunglasses.

Nice Sublime, nice,

Glad you like it :thumbup:

Good morning everyone,

 

by the way, you are really taking campaign on a new whole level with this great job.

 

I have the exact same problem starting from yesterday when I tried the Harrier PG campaign, it was a while that I wasn't playing, so I checked also the other (TF-74 Tomcat and Hornet), they have the exact same problem.

 

I made some investigation and the problem seems that the script cannot find the file "MissionEventsLog.lua".

 

The problems, to me, happens when I exit the mission and later, of course, if I try to launch the DEBUG_DebriefMission bat file.

 

I tried to look around on the drives, in fact the files seem to not exists, I am not sure if it is generated by DCS or by DCE.

 

For info, I am using it on DCS Openbeta, before, making the appropriate changing the TF-74 was working.

 

Thanks for the help.

 

Fly safe.

 

Nicola

hi paspa

Actually, you have the same problem as Agrrregat.

So I suggest you to read this post, and if it doesn't work, to post here a screen of the installation of your campaigns by expanding the tree on the left.

https://forums.eagle.ru/showpost.php?p=4334520&postcount=1562

Ok, Camp_init is changed wth DCS.openbeta path.

All 3 files updated with openbeta path too on D.

OB Loadouts also moved to Init folder

But now when i'm running fristmission.bat is loading forever

*

ATO Assigning Escorts (27055)

Number of plane Before Prune: 101 PlaneStatic: 69 Nb Helic: 0 HeliStatic 1

Pruned 299, kept 386

Number of plane After Prune: 101 PlaneStatic: 0 Nb Helic: 0 HeliStatic 0

Not enough ready aircraft for all clients.

*

Saved games is on C as defeault.

Hornet is fine

did you update the ScriptsMod folder from the new Falcon campaign in the file Falcon_over_PG_-v20.33.03c.zip?

If you didn't (and to avoid "breaking" your 2 other functional campaigns)

Edit the old ScriptsMod folder to ScriptsMod_OLD

And adds the one in the file Falcon_over_PG_-v20.33.03c.zip

After talking about it with Cef, it appears that with the Falcon campaign, the problem of loops in the generation of missions happens a few times, so we must insist.

We reproduced your bug with a wrong camp_init.lua so if you changed it it should work now ...

Insist to regenerate with first mission it should work. I will study the campaign to help mission generation ;)

Envoyé de mon iPhone en utilisant Tapatalk

@PB0_CEF, just testing the new TF74 Tomcat on latest Open Beta, all working well, however, I noticed the B-52 strikes fly their route, but never launch their JSOWs at the "Attack" waypoint. They just turn around and depart. This when doing CAP or Escort missions.

Cheers!

Sent from my SM-G950F using Tapatalk

Hi guys,

Just a bit more info to PB0, Miguel and the users.

Today I tested my 4th DCE campaign instalation. The described bellow happened in all 4 I have here running.

First of all, I followed the instruction on the dot for the DCS openbeta installation. The FirstMission.Bat ran smooth.

Now, trouble begin (and solved itself).

On the first mission, I flew and after the QUIT mission screen I got the Scrip pop up for the new mission generation (the black one) and the pop up for the mission results (the white one). While I get these pop ups, the black DCS loading screen hungs up and stays displayed.

I had to Task Manager it off.

When I came back to DCS, campaign was still considered Inactive. Flew again and got the same result.

I flew for the third time, same result.

On the Fourth time the campaign worked itself out and is up and running.

This happened on all four.

“Craziness is to repeat the same process expecting different results.”

The ones I got up and running:

Hornet over PG;

Harrier over PG;

Falcon over PG (latest 33c vs);

RAF Harrier over Caucasus.

Good luck to you all,

Sydy

@PB0_CEF, just testing the new TF74 Tomcat on latest Open Beta, all working well, however, I noticed the B-52 strikes fly their route, but never launch their JSOWs at the "Attack" waypoint. They just turn around and depart. This when doing CAP or Escort missions.

 

Cheers!

 

 

Sent from my SM-G950F using Tapatalk

Thanks for your report !

Few questions :

- what was the B-52 target ?

- did you used Mission planner to change you weapons ?

- did you change the conf_mod settings : Triggerstart : false to true ?

Envoyé de mon iPhone en utilisant Tapatalk

Hi guys,

 

Just a bit more info to PB0, Miguel and the users.

 

Today I tested my 4th DCE campaign instalation. The described bellow happened in all 4 I have here running.

First of all, I followed the instruction on the dot for the DCS openbeta installation. The FirstMission.Bat ran smooth.

 

Now, trouble begin (and solved itself).

On the first mission, I flew and after the QUIT mission screen I got the Scrip pop up for the new mission generation (the black one) and the pop up for the mission results (the white one). While I get these pop ups, the black DCS loading screen hungs up and stays displayed.

I had to Task Manager it off.

When I came back to DCS, campaign was still considered Inactive. Flew again and got the same result.

I flew for the third time, same result.

On the Fourth time the campaign worked itself out and is up and running.

 

This happened on all four.

 

“Craziness is to repeat the same process expecting different results.”

 

The ones I got up and running:

Hornet over PG;

Harrier over PG;

Falcon over PG (latest 33c vs);

RAF Harrier over Caucasus.

 

Good luck to you all,

 

Sydy

Thanks for your report : it’s a bad bug we never solved really... :(

Envoyé de mon iPhone en utilisant Tapatalk

Thanks for your report !

 

Few questions :

- what was the B-52 target ?

- did you used Mission planner to change you weapons ?

- did you change the conf_mod settings : Triggerstart : false to true ?

 

 

Envoyé de mon iPhone en utilisant Tapatalk

1. The B-52 target was the SA-2 N2 site.

2. I did not touch Mission Planner at all, just "FLY" straight into the mission.

3. TriggerStart is set to FALSE.

Cheers!

Sent from my SM-G950F using Tapatalk

Hi guys,

 

Just a bit more info to PB0, Miguel and the users.

 

Today I tested my 4th DCE campaign instalation. The described bellow happened in all 4 I have here running.

First of all, I followed the instruction on the dot for the DCS openbeta installation. The FirstMission.Bat ran smooth.

 

Now, trouble begin (and solved itself).

On the first mission, I flew and after the QUIT mission screen I got the Scrip pop up for the new mission generation (the black one) and the pop up for the mission results (the white one). While I get these pop ups, the black DCS loading screen hungs up and stays displayed.

I had to Task Manager it off.

When I came back to DCS, campaign was still considered Inactive. Flew again and got the same result.

I flew for the third time, same result.

On the Fourth time the campaign worked itself out and is up and running.

 

This happened on all four.

 

“Craziness is to repeat the same process expecting different results.”

 

The ones I got up and running:

Hornet over PG;

Harrier over PG;

Falcon over PG (latest 33c vs);

RAF Harrier over Caucasus.

 

Good luck to you all,

 

Sydy

I too have had this problem in the past and have noticed a few other members have the same.

Try the following:

1. Right-click your DCS shortcut and select "Properties".

2. Select the "Compatibility" Tab.

3. Tick the "Disable full-screen optimisations" box: as shown in the attached picture.

Now I'm not saying this is a verified cure or work-around, but I have not had the screen freeze on any missions (I've played about 10 of the TF74 Tomcat on latest OB) lately. It may just be coincidental, and I have not tested on any other campaigns as yet.

I hope it helps,

Cheers!

Sent from my SM-G950F using Tapatalk

Hey Sydy,

 

I too have had this problem in the past and have noticed a few other members have the same.

 

Try the following:

 

1. Right-click your DCS shortcut and select "Properties".

2. Select the "Compatibility" Tab.

3. Tick the "Disable full-screen optimisations" box: as shown in the attached picture.

 

Now I'm not saying this is a verified cure or work-around, but I have not had the screen freeze on any missions (I've played about 10 of the TF74 Tomcat on latest OB) lately. It may just be coincidental, and I have not tested on any other campaigns as yet.

 

I hope it helps,

 

Cheers!

 

Sent from my SM-G950F using Tapatalk

Tks for the tip. I will follow it as well!