FlightControl-Master / MOOSE

Mission Object Oriented Scripting Environment (MOOSE) for lua mission scripting design in DCS World
http://flightcontrol-master.github.io/MOOSE/
GNU General Public License v3.0
291 stars 98 forks source link

getTypeName errors spamming logs #2143

Closed thebgpikester closed 4 months ago

thebgpikester commented 4 months ago

Excerpt example:

2024-07-05 14:35:43.252 INFO    Scripting (Main): event:type=score,initiatorPilotName=M48 Chaparral,t=30813.774,linked_event_id=10707,initiator_unit_type=M48 Chaparral,event_id=10708,initiator_object_id=16926209,amount=50,comment=air,initiator_coalition=2,initiator_ws_type1=2,initiatorMissionID=2072,
2024-07-05 14:35:43.252 ERROR   SCRIPTING (Main): Mission script error: [string "C:\Users\root\AppData\Local\Temp\DCS.testing\/~mis00007660.lua"]:13094: Object doesn't exist
stack traceback:
    [C]: ?
    [C]: in function 'getTypeName'
    [string "C:\Users\root\AppData\Local\Temp\DCS.testing\/~mis00007660.lua"]:13094: in function 'onEvent'
    [string "Scripts/World/EventHandlers.lua"]:13: in function <[string "Scripts/World/EventHandlers.lua"]:11>
2024-07-05 14:35:43.253 INFO    SCRIPTING (Main): 206199(185686)/I:                   FLIGHTGROUP150328.onafterElementDead((FLIGHTGROUP 1st Egyptian Air Superiority Squadron_AID-1095 | Element dead 1st Egyptian Air Superiority Squadron_AID-1095-01 at t=30813.774))

The theory is that these are weapons or shells and they are changing in their lifespan to some other object a bit like what a tank cooks off from a unit into a static, in order to save resources.

It was Lurcher from 4YA that offered some of this and its mostly conjecture but rmeoving it would help keep logs cleaner.

Applevangelist commented 4 months ago

What‘s the Moose script used?

Applevangelist commented 4 months ago

Would be nice to know a bit more, like CLASS

funkyfranky commented 4 months ago

@thebgpikester can we close this with the isExist check?