[INVESTIGATING]Debriefing File can not be opened

[DST]

I get this message when ending a mission after new update. Not every time, but it´s all single player missions I created myself a time ago. This really is getting quite annoying.

[BIGNEWY]

Hi

 

can you confirm this is with the F-14?

 

Thanks

[SandMan23]

Hi Big

 

Yes, only occurring with the F14 on my side. Tested with SP F-16 and F-18. Mission ends to briefing screen just fine. Getting the error described by OP when exiting F14 missions.

[Sgt_Fresh]

Debriefing File can not be opened

 

I just got this after my update download? Does anyone know how to view the mission end Debrief?

 

Thanks in advance for any help.

[Sonoda Umi]

It lasts in F-14B since 2.5.6 released.

[Hummersepp]

I have this error in the F14 and F18 so far

[Sgt_Fresh]

Same error after todays update.

[pegasus1]

Have this with the AV8B

[tflash]

I can confirm, have this problem with F-14 and JF-17 since latest open beta patch 2.5.6

[dorianR666]

its still happening for me too

latest OB and JF-17

[Sgt_Fresh]

Any plans to correct this......? After the latest update I still get the "debriefing file cannot be opened" :(

[dorianR666]

still an issue.

i cant progress in the JF-17 campaign because of this.

[BIGNEWY]

Please attach a short track replay and your dcs logs,

 

This is proving to be a difficult issue.

 

Please also ensure you have no unofficial mods and have run a cleanup and repair or verify for steam users.

 

Thanks

[dorianR666]

hi newy

 

i have discovered following interesting things:

a) whether the error message will be shown can be predicted by attempting to open the window while flying ("score window" binding). if the window opens, mission will be properly debriefed. if the window doesnt open, the error will be shown after mission.

b) sometimes the debriefing event list contains bizarre entries, event column being "score" with details column being "inf" (infinity?) or a random floating-point number with many decimal places (particular example: 3.2198989391327). pic is attached.

c) i found this in my log

2020-03-09 16:53:49.664 ERROR Lua::Config: Call error debriefing.show:[string "./Scripts/UI/debriefing.lua"]:953: table index is NaN.

apart from this message, nothing else unusual.

 

no mods, ran repair just to be sure.

 

so far i wasnt able to generate short enough track for it to reliably happen. i might add it later.

i hope this helps a bit.

[dorianR666]

furthermore, debrief.log contains these interesting items:

[63] =

{

amount = inf,

t = 29282.76,

type = "score",

initiatorMissionID = "45",

}, -- end of [63]

obviously the event described in previous post's b) point.

 

 

but i also found this:

[56] =

{

amount = -nan(ind),

t = 29250.514,

type = "score",

initiatorMissionID = "45",

}, -- end of [56]

as you can see, the amount is nan (="not a number"). this is probably what triggers the error in log as described in previous post's c) point.

 

 

so the whole problem appears to be caused by these random "score" events with invalid amount field.

case closed it seems :thumbup:

[draconus]

another track and log when bug happened:

https://ufile.io/vby10mif

 

btw: there's this nan too in the debriefing log

dcs.log.txt

debrief.log.txt

[grant977]

Where do I post the Logs from as I am getting this issue as well.