fixed `Controller.getDetectedTargets()` - ground units do not detect activated/spawned new units in sight

[Apple]

When testing, I found that ground units which are activated/spawned are never detected by other ground units (least the data is not coming via the API). Also, dead units are never forgotten. Demo code:

function seewhatwesee(one,time)

local unit = Unit.getByName("Recce Unit #001")

local contr = unit:getController()

local detectedunits = Controller.getDetectedTargets(contr,1,2,4,8,16,32)

for _,_unit in pairs(detectedunits or {}) do

env.info("Detected: "..Object.getName(_unit.object))

end

return time+10

end



timer.scheduleFunction(seewhatwesee, 1, timer.getTime() + 10)

 

Demo mission - units of the group Enemy-1 are never reported in the log.
Dead units (as in killed in CA by a tank) continue to be reported.

ground not detecting ground demo.miz

Edited June 10, 2024 by Apple

[Pikey]

I'll look at the miz and generate the tracks or convert to something that can be reported.

[Abburo]

@ED team ... please have a look on this critical issue

[Pikey]

So there's a lot going on. What I found is that ROE stops detection. For those not running the track, its too much to explain but there are combinations of Hold fire, invisible and late activated.

I flipped ROE to 'fire' on the M1A1. Instead of shooting the unarmed trucks that were detected by [who?] in the logs, it immediately detects the BTR and wipes them out. I conclude that if you turn ROE to not firing, it also changes the detection to "blind" or paused or something that doesnt work until released.

The combination of invisibles and ROE and inability to kill/attack contributes to the overall impression of something worse. The spawned in BTR fails to attack the MBT in its front when spawned. But this is becauyse of unit type vs unit type restrictions. If the unit is replaced with a BMP2, the turret immediately fires.

Spawning a late activated Bradley behind those BMPs, it immediatley fires on the BMP and the BMP immediately responds behind itself

I dont find a defect with detection, despite the weird ignorance of the BTR towards an Abrams in front of it. And the ROE thing is debateably a bug, but its more unexpected than a bug.

For your second report of persistent detection after death I need something a bit clearer.

Edited June 10, 2024 by Pikey

[Apple]

I would still hold the ROE/detection combo as a bug as it prevents units from detecting  newly spawned(!) units and thus being used as Jtacs. At the same time the same tank does detect units which were placed in the ME despite it’s ROE!

Edited June 10, 2024 by Apple

[Apple]

Track of Killing trucks in CA - still reported as detected in the logs

 

2024-06-10 17:04:37.428 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [2560, 1440]
2024-06-10 17:04:46.490 INFO    SCRIPTING (Main): Detected: Unit #002
2024-06-10 17:04:46.490 INFO    SCRIPTING (Main): Detected: Unit #001
2024-06-10 17:04:46.490 INFO    SCRIPTING (Main): Detected: Unit #1
2024-06-10 17:04:56.491 INFO    SCRIPTING (Main): Detected: Unit #002
2024-06-10 17:04:56.491 INFO    SCRIPTING (Main): Detected: Unit #001
2024-06-10 17:04:56.491 INFO    SCRIPTING (Main): Detected: Unit #1
2024-06-10 17:05:06.494 INFO    SCRIPTING (Main): Detected: Unit #002
2024-06-10 17:05:06.494 INFO    SCRIPTING (Main): Detected: Unit #001
2024-06-10 17:05:06.494 INFO    SCRIPTING (Main): Detected: Unit #1
2024-06-10 17:05:07.388 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0]
2024-06-10 17:05:14.481 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [2560, 1440]
2024-06-10 17:05:15.800 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0]

Trucks dead but still reported:
2024-06-10 17:05:16.487 INFO    SCRIPTING (Main): Detected: Unit #002
2024-06-10 17:05:16.487 INFO    SCRIPTING (Main): Detected: Unit #001
2024-06-10 17:05:16.487 INFO    SCRIPTING (Main): Detected: Unit #1

 

Ground detect Ground Demo.trk

[kaltokri]

+1 for solving the issues by ED

[Kirito]

+1

[leonardo_c]

+1

[Pikey]

Thanks for the report, Ive changed the original to remove the other units and planes and radars and checked the track on other DCS versions to produce a report which ive submitted.

Just for your information, the issue is slightly different with the "forgetting" Actually they do forget...eventually, long after they are dead though. Reminds me of a certain bug with the tank dead event that was never coming when the tank went bang and the unit changes from unit to static. Seems like somehow the delay in forgetting is whilst they are a unit. Im curious to see what other types do but Ive run out of time for today.


 

Edited June 10, 2024 by Pikey
corrections

[mimamema]

+1

4 hours ago, kaltokri said:

+1 for solving the issues by ED

 

[goldleader]

+1

4 hours ago, kaltokri said:

+1 for solving the issues by ED

 

[HC_Official]

+1

[BavarianPilot]

+1 

[Apple]

@Pikey Is there some movement on this pls?

[Pikey]

Hi @Appleit was reported internally, i.e. it made its way from here, to my internal report and someone dilligent took it and off it went into the great unknown . Its a pretty busy time right now, I hope I can add a bump when things calm down. I wouldn't expect anything this month, but stranger things have happened. Sometimes things sneak into patch releases and we dont know until later, sometimes we wait 3-6 months, sometimes a lot more. If you ever get examples where you can demonstrate how it affects many people, that might be useful to add, otherwise we've given it out best wishes and sent it off

[Abburo]

@Pikey I reckon ED team is receiving a lot of issues reports from most of us, however ED team have to reckon the reporting source. In this case is Applevangelist which at the moment is one of the best in understanding low level scripting and behavior in DCS, not mentioning he is the main lead of MOOSE framework. In these cases where reporting sources are well known subject matter experts, you might need to add this in your report and prioritize accordingly. 

Please work with the team and get this type of reporting on a dedicated resolution process.

@BIGNEWY @NineLine

Thank you!

Edited July 7, 2024 by Abburo

[rob10]

6 hours ago, Abburo said:

@Pikey I reckon ED team is receiving a lot of issues reports from most of us, however ED team have to reckon the reporting source. In this case is Applevangelist which at the moment is one of the best in understanding low level scripting and behavior in DCS, not mentioning he is the main lead of MOOSE framework. In these cases where reporting sources are well known subject matter experts, you might need to add this in your report and prioritize accordingly. 

Please work with the team and get this type of reporting on a dedicated resolution process.

@BIGNEWY @NineLine

Thank you!

I get where you're coming from, but a bug is a bug no matter who reports it and I'm pretty sure priority is assigned based on the importance of the bug (you may disagree with where ED places it in importance).  A bug reported by a well known modder may well have much lower priority than something reported by a 1st time poster because it only effects a small number of people (and I get that it may be a super critical bug to that subset of users) or a fix is more complex that you realize and there isn't enough dev time to dedicate to it for example.  Bug reports from people "in the know" likely naturally get more attention already because they probably contain the information required and explain the problem better.

[Abburo]

@rob10 i'm not getting you, nor want to debate into this. It was just my view for ED, being entirely up to them to decide.

[Flappie]

It should be fixed with the next update.

[Flappie]

Fixed in today's update.

[Apple]

Thanks @Flappie  I just tested that with a Humvee, and indeed, now indeed the detection state isn't dependent any longer on the ROE state. Instead, it is now dependent on the **alert state** -in GREEN state you get nada, in RED or AUTO state it works. So, problem moved but not resolved. @Pikey

 

 

Edited July 16, 2024 by Apple

[Pikey]

ugh. I can't even figure that out.

[Pikey]

I have the same reporting process as here, just in a place which has more focus, I've asked for everything I can get, I've given sweat blood, tears and I speak to the entire community and remember, when Apple joined the MOOSE team I was there, and have been since Sven and us all were in Slack over 8 years ago.  ANd im doing more I cant say, I dont know how to reassure you, I think it may be at a limit of what the community could possibly do.

On 7/7/2024 at 7:49 AM, Abburo said:

@Pikey I reckon ED team is receiving a lot of issues reports from most of us, however ED team have to reckon the reporting source. In this case is Applevangelist which at the moment is one of the best in understanding low level scripting and behavior in DCS, not mentioning he is the main lead of MOOSE framework. In these cases where reporting sources are well known subject matter experts, you might need to add this in your report and prioritize accordingly. 

Please work with the team and get this type of reporting on a dedicated resolution process.

@BIGNEWY @NineLine

Thank you!

 

and im still here.

[Abburo]

9 minutes ago, Pikey said:

I have the same reporting process as here, just in a place which has more focus, I've asked for everything I can get, I've given sweat blood, tears and I speak to the entire community and remember, when Apple joined the MOOSE team I was there, and have been since Sven and us all were in Slack over 8 years ago.  ANd im doing more I cant say, I dont know how to reassure you, I think it may be at a limit of what the community could possibly do.

and im still here.

Thank you, really appreciate your efforts !