-
Notifications
You must be signed in to change notification settings - Fork 44
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
IADS doesn't detect targets when late activation is used in the Mission Editor #24
Comments
can you post the mission here? |
Here you go. In the LUA it's the SKYNET() function. Hopefully this useful to help. |
thanks will look into it |
Is there any progress on adding dynamically spawned SAM,EW, Command and power sources to the IADS? |
@Shazzer1951 check out the discord channel: Some users have done workarounds. It's still on my backlog. |
Listen to this event: |
Seem like only birth of units can be tracked not whole groups: On birth of Unit check to which group it belongs, then add that group to Skynet, also add check that unit/group name corresponds to prefix that was previously set for the IADS. only if that matches add the EW / SAM site to the IADS. When adding a sam site or ew site, check via the groups units, if this site is not late activated, if so don't add it. Ensure Group can not be added multiple times to Skynet. Probably best checked in addSamSite / addEWRadar Function globally for Skynet. |
DCS Mission LUA code is here: https://paste.ofcode.org/c22keLj5z7RQFHnXHLYMPp
This work perfectly if the EW and SAM sites are NOT spawned in the mission code.
I tested this with EW being EWR 1L13, EWR 55G6 and an A-50 AWACS.
SAMs were SA-2 and SA-11, manually added to ensure object was was the SR.
However, if the same code is executed after late activated spawns of the EW and SAM no detection occurs.
DCS.LOG extract here: https://paste.ofcode.org/35evyrAw6rFW4LULubWjqJD
The text was updated successfully, but these errors were encountered: