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

IADS doesn't detect targets when late activation is used in the Mission Editor #24

Open
johnferrier opened this issue Jul 24, 2020 · 7 comments
Assignees

Comments

@johnferrier
Copy link

johnferrier commented Jul 24, 2020

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

@walder
Copy link
Owner

walder commented Jul 25, 2020

can you post the mission here?

@johnferrier
Copy link
Author

Here you go.
This is a much larger mission we use for training. The function is working now as I've disabled Late Activation. Skynet is setup in the East side of the map.

In the LUA it's the SKYNET() function.
It'll need the Late Activation re-enabled on the EWR and SAM sites and a SPAWN lines uncommented in the function.

Hopefully this useful to help.

Persian Gulf Mutiple Scenarios.zip

@walder
Copy link
Owner

walder commented Jul 28, 2020

thanks will look into it

@walder walder self-assigned this Aug 16, 2020
@Shazzer1951
Copy link

Is there any progress on adding dynamically spawned SAM,EW, Command and power sources to the IADS?

@walder
Copy link
Owner

walder commented Nov 17, 2020

@Shazzer1951 check out the discord channel:
https://discord.gg/nT2UFeDX

Some users have done workarounds.

It's still on my backlog.

@walder walder moved this to Release 3.1.0 Backlog in Skynet IADS Feb 10, 2023
@walder walder removed the status in Skynet IADS Feb 10, 2023
@walder
Copy link
Owner

walder commented Feb 10, 2023

Listen to this event:
https://wiki.hoggitworld.com/view/DCS_event_birth

@walder
Copy link
Owner

walder commented Feb 10, 2023

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.

@walder walder moved this to Release 3.1.0 Backlog in Skynet IADS Feb 10, 2023
@walder walder moved this from Next Release Backlog to In Progress in Skynet IADS Feb 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

3 participants