Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LUA Error when a new HARM is identified #83

Closed
baleBaron opened this issue Mar 15, 2023 · 0 comments
Closed

LUA Error when a new HARM is identified #83

baleBaron opened this issue Mar 15, 2023 · 0 comments

Comments

@baleBaron
Copy link
Contributor

Im getting LUA Error when a new HARM is identified while another SAM has one of its radars destroyed.

ERROR SCRIPTING (Main): MIST|doScheduledFunctions|1300: Error in scheduled function: $1[string "C:\Users\XXXXX\AppData\Local\Temp\DCS\/~mis00000F0C.lua"]:1896: Object doesn't exist

How I reproduce:
Destroy radar of one SAM site in the IADS network (fastest way through F10 trigger)
Launch HARM at another site
When this HARM gets identified, and the site with one bad radar gets notified, error happens

Error is triggered from SkynetIADSAbstractRadarElement:informOfHARM()

A simple radar:isExist() guard in skynet-iads-abstract-radar-element.lua appears to solve this for me.

@walder walder moved this to Next Release Backlog in Skynet IADS Jun 23, 2023
@walder walder moved this from Next Release Backlog to Ready for Release in Skynet IADS Dec 29, 2023
@walder walder moved this from Ready for Release to Released in Skynet IADS Dec 29, 2023
@walder walder closed this as completed Dec 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Released
Development

No branches or pull requests

2 participants