reported earlier Jdam TOO multiple targets

[KotPilot]

Hi guys, i try to test multiple jdams on different targets.

If i turn the jdam to TOO and slew the TGP over a target and press TDC down i can see that the coordinates were safed to the first bomb.

if i now hit undesignate, and go to the next bomb (step) all coordinates are gone, also for the first one.

i watched some videos and somehow if the people press undesignate the coordinats are still safed for the first jdam.

do i do something wrong ?

[Shimmergloom667]

That method does not work anymore, at the current state there is no possibility to do so without using mark points etc. - this has been discussed ad nauseam already in here, and it seems to be how it works IRL (at least no one had a definitive answer in the contrary, yet).
 

 

[KotPilot]

Thank you, ich will check this out later.

have a nice day

[BarTzi]

5 hours ago, Shimmergloom667 said:

That method does not work anymore, at the current state there is no possibility to do so without using mark points etc. - this has been discussed ad nauseam already in here, and it seems to be how it works IRL (at least no one had a definitive answer in the contrary, yet).
 

 

That's not accurate and I'm not sure why this is still a thing. Available documentation suggests that undesignating should not wipe out all previously assigned JDAM TOO targets.
 

 

It's not correct as is. I'm not sure why it's tagged as such.

Edited December 16, 2021 by BarTzi

[Foka]

Why this topic is marked as "correct as is" if ED is not sure of that, what was stated in previous thread, and there are multiple evidence, that it isn't correct?

[wicked.fox]

Thanks for the response. Was looking just for that. I wonder what TOO1 & TOO2 in the MSN Page are for, if not for storing coordinates

[Shimmergloom667]

2 hours ago, BarTzi said:

That's not accurate and I'm not sure why this is still a thing. Available documentation suggests that undesignating should not wipe out all previously assigned JDAM TOO targets.
 

It's not correct as is. I'm not sure why it's tagged as such.

 

It's still a thing because no one so far managed to give hard black-on-white evidence to @BIGNEWY or @NineLine that TOO should work differently. Mind you: *I* certainly agree that the current implementation is wrong, but ED thinks otherwise, and unless someone comes up with evidence it will be marked "correct as is" and dismissed.

So, in case you have evidence on how it should work correctly: share a track file and documentation with the team. Or maybe @Santi871 can talk to the team internally again, since he confirmed as well that the current implementation is wrong.

Edited December 16, 2021 by Shimmergloom667

[BIGNEWY]

I do have one report open for TOO behaviour when stepping, I overlooked it when searching. 

I think for now I will mark this reported, if anyone has evidence PM me directly.