track replay windows error after releasing ordenance

[vgilsoler]

When replay a track, I tested with different tracks,  and there is a release ordenance (bombs, missiles or tanks) a windows error is showed. The track replay can continue. It happened with both stable and last beta using MT. I didn't tested with ST.

I attach error screenshot, dcs log, mission, and a track replay example. Error produced about 1200s after start.

practice_f86_bombing_no_mpc.trk dcs.log

CFragps_Marianas_Proving_Grounds.miz

Edited December 20, 2023 by vgilsoler

[Flappie]

Let's see. The error springs from this part of the script:

    if event.id == 1 then -- shot event, from player
        if not event.weapon then return end 
        local uComms = bombRange.unitComms[uName]
        if bombRange.mustCheckIn and (not uComms.checkedIn) then 
            if bombRange.verbose then 
                trigger.action.outText("+++bRng: Player <" .. pName .. "> not checked in.", 30)
            end
            return 

DCS says uComms equals nil.

This looks like a custom script issue.

[vgilsoler]

On 1/3/2024 at 4:44 AM, Flappie said:

Let's see. The error springs from this part of the script:

    if event.id == 1 then -- shot event, from player
        if not event.weapon then return end 
        local uComms = bombRange.unitComms[uName]
        if bombRange.mustCheckIn and (not uComms.checkedIn) then 
            if bombRange.verbose then 
                trigger.action.outText("+++bRng: Player <" .. pName .. "> not checked in.", 30)
            end
            return 

DCS says uComms equals nil.

This looks like a custom script issue.

Just to understand how it should work. Should the script have a condition to control if it is running the mission or is it replying track? Something like “if missionreplay == true then …”
Is this property available by default? Or needs to be coded?

Edited January 4, 2024 by vgilsoler

[Flappie]

16 hours ago, vgilsoler said:

Should the script have a condition to control if it is running the mission or is it replying track?

I don't think so, no. I have no clue how the issue only springs when the track is replayed.