fixed End mission button not working

[nbpenguin]

Hey, this also just happened to me for the first time.
I saw in another thread (or maybe this one, I forget) that it would be useful if it was found _not_ in a DLC mission, well mine was in the default Georgian Oil War, Mission ATO A.05.4 to be precise.

I was not using BuzzLine's fix.

Line 779 in dcs.log file.

2023-01-22 18:26:15.907 ALERT   LUACOMMON (Main): Error: GUI Error: [string "./MissionEditor/modules/me_logbook.lua"]:1128: attempt to index local 'unitTarget' (a nil value)
GUI debug.traceback: stack traceback:
	[C]: ?
	[string "./MissionEditor/modules/me_logbook.lua"]:1128: in function 'updateUserStatistics'
	[string "./MissionEditor/modules/me_debriefing.lua"]:361: in function 'updateStatistic'
	[string "./MissionEditor/modules/me_debriefing.lua"]:385: in function 'endMission'
	[string "./MissionEditor/modules/me_debriefing.lua"]:351: in function 'onChange'
	[string "./dxgui/bind/Button.lua"]:22: in function 'callback'
	[string "./dxgui/bind/Widget.lua"]:368: in function <[string "./dxgui/bind/Widget.lua"]:363>

From what I remember (no idea if this will be helpful), the only slightly unusual things about the mission was that I hit a Helo FOB with two TV guided missiles, and accidentally locked a train carrage when trying to hit a tank.

Losing an entire missons progress sucks...

 

errorMisson.log dcs.log

[d0ppler]

I'm doing a user campaign now (made in the previous open beta release) and nothing happens when I click "End mission" in the mission debrief window.

I am only able to close the window and therefore I'm stuck at the same point in the campaign.

[Fisherman82]

This happened to me today, I dont have a track or log now, I may be able to find the log tomorrow though.

I was not using BuzzLines fix. 

It has newer happened to me before and it is probably linked to a unusual thing I saw in the log before I hit quit: 

I got a kill on a AIM_120 with my AIM-120, dont know if the one I killed was fired by a AI F15 or if I killed my own missile (I fired two).

[BuzzLine]

On 1/24/2023 at 8:27 PM, nbpenguin said:

accidentally locked a train carrage when trying to hit a tank.

Indeed, that seems to be the offending part in your debrief.log (a kill event by the player with a zero/empty/null targetMissionID) :

[1955] = {
			["initiatorMissionID"] = "393",
			["initiator_coalition"] = 1,
			["initiator_object_id"] = 16910080,
			["initiator_unit_type"] = "Su-25T",
			["initiator_ws_type1"] = 1,
			["t"] = 3001.842,
			["target"] = "coach a platform",
			["targetMissionID"] = "0",
			["target_coalition"] = 0,
			["target_object_id"] = 6002022,
			["target_unit_type"] = "coach a platform",
			["target_ws_type1"] = 2,
			["type"] = "kill",
			["weapon"] = "",
},

There used to be another issue with trains but it does not seem to be the case here. This is the standard vanilla bug, my fix should protect against it.
BTW, no changes came with yesterday's openbeta, so you can keep using the file I posted previously.

Interestingly enough, there is no trigger attached to that unit, nor is it in a trigger zone (I seem to see you were shooting the T-72s northwest of recon objective 1). I used to have a theory that it happened when objects were tied to a trigger (reason for my asking for a full mission file, not hidden/encrypted).

[BuzzLine]

Alright, here's a short track and miz file. Just shoot the first autogenerated train you see. It seems to trigger the problem :

2023-01-26 21:37:56.365 ERROR   Lua::Config (Main): Call error onShowMainInterface:[string "./MissionEditor/modules/me_logbook.lua"]:1129: attempt to index local 'unitTarget' (a nil value)
stack traceback:
	[C]: ?
	[string "./MissionEditor/modules/me_logbook.lua"]:1129: in function 'updateUserStatistics'
	[string "./MissionEditor/modules/me_debriefing.lua"]:361: in function 'updateStatistic'
	[string "./MissionEditor/modules/me_debriefing.lua"]:413: in function 'show'
	[string "./MissionEditor/MissionEditor.lua"]:655: in function 'openReturnScreen'
	[string "./MissionEditor/MissionEditor.lua"]:671: in function <[string "./MissionEditor/MissionEditor.lua"]:667>.

@Flappie, this one's for you my friend.  

Switching my fix back on. Fly safe everyone ! 

BUG_endmission_train2.trk endmission_bug_train2.log debug_endmission_bug2_train.miz

[Flappie]

1 minute ago, BuzzLine said:

Alright, here's a short track and miz file. Just shoot the first autogenerated train you see. It seems to trigger the problem :

2023-01-26 21:37:56.365 ERROR   Lua::Config (Main): Call error onShowMainInterface:[string "./MissionEditor/modules/me_logbook.lua"]:1129: attempt to index local 'unitTarget' (a nil value)
stack traceback:
	[C]: ?
	[string "./MissionEditor/modules/me_logbook.lua"]:1129: in function 'updateUserStatistics'
	[string "./MissionEditor/modules/me_debriefing.lua"]:361: in function 'updateStatistic'
	[string "./MissionEditor/modules/me_debriefing.lua"]:413: in function 'show'
	[string "./MissionEditor/MissionEditor.lua"]:655: in function 'openReturnScreen'
	[string "./MissionEditor/MissionEditor.lua"]:671: in function <[string "./MissionEditor/MissionEditor.lua"]:667>.

@Flappie, this one's for you my friend.  

Switching my fix back on. Fly safe everyone ! 

BUG_endmission_train2.trk 215.27 kB · 0 downloads endmission_bug_train2.log 11.45 kB · 0 downloads debug_endmission_bug2_train.miz 10.73 kB · 0 downloads

Many thanks, @BuzzLine.

I made a campaign our of your mission and I can at last reproduce the issue. I'll ask devs to consider your fix.

[d0ppler]

Update : When I restarted the campaign, I could continue by clicking "End mission".

Edited February 9, 2023 by d0ppler

[BuzzLine]

Check this (these) thread(s) : 

 

[BIGNEWY]

threads merged

[Gryzor]

Same bug in 2.8.2. Cannot end user campaigns.

[Wiggo]

On 1/29/2023 at 6:19 PM, Gryzor said:

Same bug in 2.8.2. Cannot end user campaigns.

Same bug here. Triggered today (NOT SURE!, about this further..). I shot train.. Dunno if was still the locomotive. Weirdly when I go dcs main menu -> campaings -> my campaigns (where it goes automatically first) it does not show any progress BUT when i click some of airplanes to see their "own" campaings progress is shown and THEN  back to -> my campaings -> it shows progress but the end mission button does not work. What is weird that somehow IF i go straight to that non progressed my campaings and start mission, the end mission button works. How is this even possible? Is there something wrong in my logbook.lua? Though it did not help with Backups either. Even 6 months old did not help on it. I have played for a couple of weeks for F/A 18´s own campaigns so dunno when this has triggered, but did not have problems couple of weeks ago. If I create new user, no probs (but no progress ofc either :P). That me_logbook.lua fix did not help for me.

Edited February 9, 2023 by Wiggo

[BuzzLine]

@Wiggo: Grab those two files with my fixes and give it a try. Your logbook should not have been damaged.

The good news is  @Flappie told me ED had fixes for all those issues, I hope they will be in the next patch.

me_logbook.lua me_campaign.lua

[Wiggo]

2 hours ago, BuzzLine said:

@Wiggo: Grab those two files with my fixes and give it a try. Your logbook should not have been damaged.

The good news is  @Flappie told me ED had fixes for all those issues, I hope they will be in the next patch.

me_logbook.lua 59.57 kB · 0 downloads me_campaign.lua 42.58 kB · 0 downloads

This was actually solved for me by your other fix I did not first notice thear was different thread about that my campaign inactive campaings / "doubleslash in code"- error. I took your fix in there, and it was just what I needed. Today realized that I just havent played custom campaings for a while, so hadnt notice that there even was this kind of bug in latest (or any) version. (the my campaign "inactive" bug, which also broke my end mission button). Now they both work  Thanks. EDIT: to be clear. Solution for me was that me_campaign.lua, that you had made for that other thread for fix. Prob really seemed only for me to be that my campaign inactive bug...

Edited February 9, 2023 by Wiggo

[Wiggo]

Again have to say. DCS shows its best on its supportive forum ppl. Like: Me 8 hours ago ""#"#%"#%"% my logbook is broken #%%"#% everything is broken, i will sell my hotas and burn my computer" 8 hours later: "HIIIGHWAAAY TO DA DANGER ZONE!!!!"

[BuzzLine]

5 minutes ago, Wiggo said:

Again have to say. DCS shows its best on its supportive forum ppl. Like: Me 8 hours ago ""#"#%"#%"% my logbook is broken #%%"#% everything is broken, i will sell my hotas and burn my computer" 8 hours later: "HIIIGHWAAAY TO DA DANGER ZONE!!!!"

The further on the edge
The hotter the intensity

it's also true for openbeta...  

[DimSim]

Happened again. Looks like recent update un-did my fix since this is a game file, not user save game folder file.

[BuzzLine]

4 hours ago, DimSim said:

Looks like recent update un-did my fix since this is a game file, not user save game folder file

Yes, you have to re-apply the fix after updates. I usually post my updated version whenever they change the file.

Good news is that all should be fixed in the next official patch. If not, then I'll post a new file in this thread.

[LordOrion]

On 2/9/2023 at 7:16 PM, BuzzLine said:

@Wiggo: Grab those two files with my fixes and give it a try. Your logbook should not have been damaged.

The good news is  @Flappie told me ED had fixes for all those issues, I hope they will be in the next patch.

me_logbook.lua 59.57 kB · 2 downloads me_campaign.lua 42.58 kB · 3 downloads

This seems to fix the problem for me too.

Thank you!

[Wolfman289]

I'm having the same issue and it's been driving me nuts! Good to hear that they have a fix coming.

[BuzzLine]

On 2/9/2023 at 7:16 PM, BuzzLine said:

The good news is  @Flappie told me ED had fixes for all those issues, I hope they will be in the next patch.

Well what do you know. Official fixes seem to be in today's patch.  

From reading the code, I can see:

• The very first "End Mission" bug from way back when : fixed
• The one caused by trains : fixed 
• The custom campaigns : probably fixed  (They wrote a different fix than mine so I don't know, but let's assume it works too)

Note : this is for todays openbeta. If someone reads this and is still on stable, either wait, upgrade, or use the two files I fixed (a few messages up). Even better : use the official me_logbook.lua and me_campaign.lua files from today's patch, the only differences with the stable branch are the fixes for those bugs.