fixed Possible bug in Object.getTypeName during S_EVENT_KILL

[Raffson]

After the release of 2.9.6.57650 I've noticed issues w.r.t. Object.getTypeName while processing a kill-event in a custom event-handler that's attached to the "world" Singleton. Specifically this happens with small caliber weapons, where a call to `event.weapon:getTypeName()` crashes with the failure message "Object doesn't exist". I've checked that `event.weapon` actually has a function called `getTypeName`, and it does, so that makes me think it might be an issue in the method itself. The strange part of it all is that the kill-event has a property called `weapon_name` which holds the same value, so I'm not sure whether this is the result of an intended change, or a bug that made it's way into the scripting API.

Please let me know if I can be of any further assistance.
Kind regards.

Edited July 13, 2024 by Raffson

[tn_prvteye]

Bumping this because this still seems to be an issue.  Seems to be affecting multiple user-made mission and career generators.

[Flappie]

Hi @Raffson. Can you please attach a .miz demonstrating the issue?

[Raffson]

On 7/25/2024 at 6:06 PM, Flappie said:

Hi @Raffson. Can you please attach a .miz demonstrating the issue?

Apologies for the late answer, but I believe the issue has been solved in yesterday's patch, more specifically the fix regarding double kill events. I can imagine how that would explain the behavior we've noticed, and I've also received some feedback from a Retribution user that the error is indeed gone. In case the error presents itself again, I'll make sure to follow up more thoroughly with a .miz file attached 

Kind regards.

[Flappie]

Your feedback is appreciated.

[Grindmetal]

2024-09-01 00:28:55.976 ERROR   SCRIPTING (Main): Mission script error: [string "C:\Users\ASHIMI~1\AppData\Local\Temp\EPiC.server\/~mis00006E8A.lua"]:7402: Object doesn't exist
stack traceback:
	[C]: ?
	[C]: in function 'getTypeName'
	[string "C:\Users\ASHIMI~1\AppData\Local\Temp\EPiC.server\/~mis00006E8A.lua"]:7402: in function 'onEvent'
	[string "Scripts/World/EventHandlers.lua"]:13: in function <[string "Scripts/World/EventHandlers.lua"]:11>

Quote

2024-09-01 00:32:57.154 ERROR   SCRIPTING (Main): Mission script error: [string "C:\Users\ASHIMI~1\AppData\Local\Temp\EPiC.server\/~mis00006E8A.lua"]:7300: attempt to call method 'getCategory' (a nil value)
stack traceback:
	[C]: in function 'getCategory'
	[string "C:\Users\ASHIMI~1\AppData\Local\Temp\EPiC.server\/~mis00006E8A.lua"]:7300: in function 'onEvent'
	[string "Scripts/World/EventHandlers.lua"]:13: in function <[string "Scripts/World/EventHandlers.lua"]:11>
2024-09-01 00:32:57.154 INFO    ASYNCNET (Main): client[2] occupied unit 1047

DCS is impossible to play any time an error occurs no more missions are supported

[334th Raven]

Bumping up, issue still present in v2.9.9.24740

I have a custom event handler which tracks event.initiator and can confirm that getTypeName(), getCategory(), getDesc(), getName() are not working on event.initiator object, haven't tried the rest of Object methods.

Edited November 16, 2024 by 334th Raven