fixed Loading Debriefing Error-Can not open debriefing file

[Chesster]

I sometimes add the Airbase name to the groupname of clients like:
"Tha'lah F-16 Hot" or whatever.

This apostrophe causes the following error in dcs.log when the mission is run from ME:

2024-02-29 11:17:55.042 ERROR   LuaGUI (Main): ERROR loading debrief.log: [string "C:\Users\MyName\Saved Games\DCS\Logs\debrief.log"]:685: ']' expected near 'lah'

Line 685 in debrief.log:
['20 Tha'lah Blue F-16C-4 (Cold)'] =
 

fairly obvious why the error occurs, but an error never the less, which could be remedied fairly easily ?


 

[GeoS72]

For a while, I had an issue in the South Atlantic map when exiting a base capture map. I would get the following pop-up error after exiting the map in Single Player or from the Mission Editor: Can not open debriefing file (see image).

After reviewing the DCS.log file, it indicated an error in the debriefing.log at a specific line item. When I looked at that line item, it pointed to a Client slot that I added to the O'Higgins airfield. The Group and Unit names included an apostrophe, O'Higgins. This is what the debriefing.log file showed:
['OV-10A Aerodromo O'Higgins'] =
    {
        time    =    10.001,
        value    =    100,
    }, -- end of ['OV-10A Aerodromo O'Higgins']

I concluded the apostrophe in the unit name caused problems with the LUA naming convention.

I changed the Group and Unit names of this client to:
['OV-10A Aerodromo O-Higgins'] =
    {
        time    =    10.001,
        value    =    100,
    }, -- end of ['OV-10A Aerodromo O-Higgins']

And the problem was solved!

For further safety precautions, I removed any apostrophes from all other Group/Unit names. This error no longer appears and the Debriefing screen is properly displayed.

[Flappie]

I don't have your issue. Can you reproduce the error with my mission? If not, please attach your .miz.

single-quote.miz

[GeoS72]

@Flappie,

I downloaded your miz file and didn't experience the problem. I also made 2 new miz files in an effort to reproduce the results. I was able to reproduce the error! The problem is caused by a slot blocking script. In the original post, the value of 100 is a clue. I use that value in my slot blocking script.

I've included 2 versions of the South Atlantic map miz file, one with slot blocker and one without. I also attached my DCS log and debrief log. Line 1411 in the DCS log calls out the error in Line 35 of the debrief log.

The debrief log at Line 35 displays:
['Su-25T O'Sheehans-1'] =
    {
        time    =    0.801,
        value    =    0,
    }, -- end of ['Su-25T O'Sheehans-1']

Because the debrief log uses single quotes for the string, it generates the error after Su-25T O. Therefore anything after the second single-quote breaks the debrief log. So it doesn't know what to do with Sheehans-1.

single-quote-DH_edit.miz debrief.log dcs.log single-quote-SA_Map.miz single-quote-SA_Map-SlotBlocker.miz

[GeoS72]

@Flappie,

Here is another example of the slot blocker breaking the debrief log in the basic map.

DCS log and debrief log included for your review.

DCS log calls out the failure on Line 1129:
2024-04-27 04:09:53.782 ERROR   LuaGUI (Main): ERROR loading debrief.log: [string "C:\Users\GeoS\Saved Games\DCS.openbeta\Logs\debrief.log"]:41: ']' expected near 'Malley'

Debrief log Lines 39 - 51 have the following info:
triggers_state =
{
    ['TF-51 O'Malley'] = (this is Line 41)
    {
        time    =    10.001,
        value    =    100,
    }, -- end of ['TF-51 O'Malley']
    SSB =
    {
        time    =    1.001,
        value    =    100,
    }, -- end of SSB
} -- end of triggers_state

single-quote-SlotBlocker.miz debrief.log dcs.log

[GeoS72]

I'd like to reiterate the problem and solution here.

Problem:
An error message will appear stating, "Can not open debriefing file" when exiting a multiplayer map in single player or Mission Editor.

The cause:
1. Group Name contains an apostrophe.
2. Slot blocking script references the Group Name containing an apostrophe.

Solution:
1. Avoid using an apostrophe in Group Names. i.e. O'Malley, O'Higgins, O'Man, etc.
2. Use dash (-), underscore (_), or no special character. i.e. OMalley, O-Higgins, O_Man, etc.

Reference the above posts for examples of a MIZ file that contains a slot blocker with the apostrophe and a MIZ file that does not use slot blocker.

Thank you, @Flappie for digesting this thread and providing the space to find the root cause of this problem.

[Flappie]

Thanks for the .miz file.

The issue is now reported.

[Flappie]

@Chesster @GeoS72 Hi gents. I believe this issue has been fixed.

[GeoS72]

@Flappie, thank you for the post. I will test it shortly.