End Mission Button not working.

[NightRider87]

Hello,

I recently came across this problem during The Serpent's Head 2 Campaign (fantastic campaign!). 

I complete the mission and land, I'm prompted in the game that the mission is complete and to exit the game. When I do the debrief screen comes up and I click 'End Mission' but nothing happens. I then have to resort to quitting without saving my progress. Really frustrating!.

 

I have attached my log if anyone can see the problem? Looks like a potential problem with me_logbook.lua.

Any help would be greatly appreciated!

Thanks.

dcs.log

[silverdevil]

13 hours ago, NightRider87 said:

Hello,

I recently came across this problem during The Serpent's Head 2 Campaign (fantastic campaign!). 

I complete the mission and land, I'm prompted in the game that the mission is complete and to exit the game. When I do the debrief screen comes up and I click 'End Mission' but nothing happens. I then have to resort to quitting without saving my progress. Really frustrating!.

 

I have attached my log if anyone can see the problem? Looks like a potential problem with me_logbook.lua.

Any help would be greatly appreciated!

Thanks.

hello and welcome to forums. i see a lot of these at end of your log. i personally have never seen them.

2024-10-03 22:19:25.750 DEBUG   LuaGUI (Main): GUI Error: [string "./MissionEditor/modules/me_logbook.lua"]:1135: table index is nil
2024-10-03 22:19:25.750 ALERT   LUACOMMON (Main): Error: GUI Error: [string "./MissionEditor/modules/me_logbook.lua"]:1135: table index is nil

before this i see this

2024-10-03 21:07:48.432 DEBUG   LuaGUI (Main): Input:    Profile[F/A-18C] key command[Force cursor to show, toggle] for device[Mouse] has different name from command[Clickable Mouse Cockpit Mode - ON/OFF] for device[Joystick - HOTAS Warthog {9552A170-4552-11ef-8008-444553540000}, Keyboard]

not sure if either of these entries is abnormal or the cause. one dumb question. did you finish all the objectives?

i am adding the content creator to this topic so maybe we can get an answer.

@Badger633 hello. any clue for this? new user cannot directly post in your sub-forum.

https://forum.dcs.world/forum/536-fa-18c-the-serpents-head-2-campaign/

thanks!

[NightRider87]

Hello,

I believe the string 

2024-10-03 22:19:25.750 DEBUG   LuaGUI (Main): GUI Error: [string "./MissionEditor/modules/me_logbook.lua"]:1135: table index is nil
2024-10-03 22:19:25.750 ALERT   LUACOMMON (Main): Error: GUI Error: [string "./MissionEditor/modules/me_logbook.lua"]:1135: table index is nil

Which shows near the end of the log is due to my trying to click the end mission button multiple times.

 

The mission in question is called 'Going for the chop' and as far as I'm aware I have completed all tasks as I get the prompt that the mission is complete after returning to the carrier.

Thanks for adding @Badger633 hopefully he can shed some light on the matter.

I did do a search and came across something similar however it seems to be a different error in the log.

However I believe this bug was fixed a while ago.

[Badger633]

Hi @NightRider87 @silverdevil

I have seen this before, unfortunately it is not related to the mission more a DCS bug or corruption of the log. 
Not that good with logs so best thing to do is report it on the forum under DCS bugs and add your log. 
Sorry couldn’t be of more help but outside the control of the campaign scripting. 
Let me know if @NightRider87cannot post onto the Badger633 section of the forums under campaigns. 

[BuzzLine]

Hello everyone, I'm the "End Mission button not working" guy. It seems indeed like a similar problem from my old 2021 nemesis but this time from a different-ish reason.

If this happens again, attach *both* the dcs.log *and* the debrief.log. Actually, the latter is the one important. Because in it, we'll find an event of type 'takeoff' and an empty/nil initiatorMissionID field (from what I can see in the code, assuming we are on the same version).
Figuring out the sequence of events that lead to this will help ED figure out where the issue is. Could be some random bug or some script issue, and it could also be an issue with the multithreading. At the very least, it *might* help people create a simple reproducible test case.

(Of course, please make sure you run the tests with no mods, no scripts, pure vanilla DCS).

Good luck, Jim

[NightRider87]

22 minutes ago, BuzzLine said:

Hello everyone, I'm the "End Mission button not working" guy. It seems indeed like a similar problem from my old 2021 nemesis but this time from a different-ish reason.

If this happens again, attach *both* the dcs.log *and* the debrief.log. Actually, the latter is the one important. Because in it, we'll find an event of type 'takeoff' and an empty/nil initiatorMissionID field (from what I can see in the code, assuming we are on the same version).
Figuring out the sequence of events that lead to this will help ED figure out where the issue is. Could be some random bug or some script issue, and it could also be an issue with the multithreading. At the very least, it *might* help people create a simple reproducible test case.

(Of course, please make sure you run the tests with no mods, no scripts, pure vanilla DCS).

Good luck, Jim

Good to see you here @BuzzLine I actually still have the debrief.log and I will attach it now. See if it holds any clues.

 

I don't think I'm running many mods aside from some echo19 sound packs. But I can check.

debrief.log

[BuzzLine]

All right, I happened to have that campaign and was able to duplicate. At least in the SuperCarrier variant , "mission 4 camp 2 SC.miz". When I run it in the mission editor, I too get the offending stacktrace in my dcs.log. Good news : just speed time up for a couple of minutes after mission start, no need to do anything. Then quit and look in dcs.log if you see the errors.

Now, *hypothesis* for root cause (might be correct or I might be completely wrong) :

Looking into the debrief.log (see below), there's something that looks a bit off at about the time the L39s take off (here it happens before, in my case it was logged a few seconds after). That event [6] looks ... different. I'd look into that first, could be a script issue in the mission. If @Badger633 uses MOOSE or any other fancy script, then that could be a source. Scripts rely on behaviors of DCS that may change with time. If so, then I'd suggest updating the script to a newer version and see if it fixes the issue.

	[6] = 
	{
		type	=	"takeoff",
		initiatorPilotName	=	"",
		place	=	"START",
		t	=	133.2,
		initiator_unit_type	=	"",
		initiator_object_id	=	16784896,
		linked_event_id	=	0,
		event_id	=	94,
		initiator_coalition	=	-1,
		initiator_ws_type1	=	200,
		initiatorMissionID	=	"_16784896", // that looks different from the usual values
	}, -- end of [6]
	[7] = 
	{
		type	=	"engine startup",
		initiatorPilotName	=	"L-39ZA",
		t	=	133.901,
		initiator_unit_type	=	"L-39ZA",
		initiator_object_id	=	16781056,
		linked_event_id	=	0,
		event_id	=	95,
		initiator_coalition	=	1,
		initiator_ws_type1	=	1,
		initiatorMissionID	=	"63",
	}, -- end of [7]
	[8] = 
	{
		type	=	"engine startup",
		initiatorPilotName	=	"L-39ZA",
		t	=	133.901,
		initiator_unit_type	=	"L-39ZA",
		initiator_object_id	=	16781312,
		linked_event_id	=	0,
		event_id	=	97,
		initiator_coalition	=	1,
		initiator_ws_type1	=	1,
		initiatorMissionID	=	"64",
	}, -- end of [8]

 

[Badger633]

Hey @BuzzLine

No specialised scripting used in the mission only standard mission editor. Just checked and yes get same result with the end button not functioning after the first set of L 39's are created.

Going to pass this on to ED as a possible bug.

Thanks

  

[NightRider87]

Thanks for taking a look at this guys. Glad you were able to reproduce the issue. Hopefully it will be fixed soon. 

[Badger633]

Just put this on the forum. 

 

[Badger633]

UPDATE: Have found a work round and issued to ED. Will be in next update. 

[NightRider87]

Thanks @Badger633 Keep up the great work!

[BuzzLine]

Out of curiosity, @Badger633 , can you share what the workaround is ?  

[Badger633]

@BuzzLine For me the work round was to omit the 3rd AI Hornet on CAT 4. It was this causing the strange number you pointed out in the debrief. Tried omitting and reinstating with a new Hornet. Same thing. So omitted that Hornet and made the first AI Hornet on Cat 2 a group of two on Cats 1 and 2. 
As in a lot of these work rounds we do not understand how or why one works and the other doesn’t. There are a lot of things in play in DCS updates that we do not know. All i know is it worked for years previously.

Have submitted both before and after missions to ED to see what has caused it and if there is a bug. 
Main thing is it will be fixed in next update

 

[BuzzLine]

DCS will never cease to amaze me. Thanks for sharing !

[NightRider87]

Many thanks for you help guys. Successfully managed to complete the mission today