fixed TOO ripple procedure (JDAM or JSOW)

[Dr. Anti-Vehicle]

48 minutes ago, BIGNEWY said:

My understanding is TOO ( Target of opportunity ) does not save when stepping. 

 

Best option is to use PP, or sometimes I stay in TOO mode and have waypoints setup for targets and WPSDG each waypoint when deploying weapons.  

 

thanks

Wow, that's a lot more inconvenience than before. However if this is correct and realistic as of right now, I have to accept reality.

36 minutes ago, FIVE-one said:

Tryied using markpoints to designate and bypass that issue, but now we have issues with markpoint/waypoint designation. (see WPDSG issue topic)

Seems like the TPOD is now into a lot of trouble sadly

 

Is there a way to assign markpoints to individual bomb so that I can drop them quickly without choosing a markpoint each time when dropping a bomb? Because you know sometimes ground units moves when one of them is under attack. So all the bombs really have to be landing within a short time frame.

[Frederf]

Unless what I read doesn't apply to this particular version, TOO should simply overwrite the last held coordinates in the weapon whenever new target coordinates down the pipe and that/those weapons are selected. Explicitly it was stated that undesignating does not remove coordinates.

[Foka]

@BIGNEWY

1. Why do we have TOO1 and TOO2 if undasignate clears progamming? It makes no sense.

2. We can't designate target in PP via WPTs, we have to enter them manually. IRL PP is populated via data cartridege, so why did you remove the only way to quickly prepare preplaned ripple attack?

[BarTzi]

1 hour ago, BIGNEWY said:

My understanding is TOO ( Target of opportunity ) does not save when stepping. 

 

Best option is to use PP, or sometimes I stay in TOO mode and have waypoints setup for targets and WPSDG each waypoint when deploying weapons.  

 

thanks

I don't think this is correct, and it also says it is not correct in the documents ED uses to implement the JDAM interface. I can show you that via PM if that's ok.

 

[BIGNEWY]

Ive changed back to investigating we will take a closer look 

 

thanks

[vCSG3 Bloat 203]

thank you - it definitely is wiping TOO mission coords from all stations & weapons, when undesignating.

[Santi871]

This is a bug and it was correct how it was before. The TOO coordinates for TOO1 and TOO2 missions in each weapon are retained and can be recalled by selecting the weapon/mission (and having a designation while doing so will overwrite the previous set of coordinates).

[BIGNEWY]

Thanks for the DM's and reports. 

 

I have asked the team to check the behaviour. 

[BATCARLO]

OpenBeta last release on 05/27/2021.

I have assigned 4 different TOOs to my Jdams.
When I clicked on undesignate before launching them, it deleted all assigned TOOs.

[Tholozor]

Already reported: 

 

[BATCARLO]

Undesignate also deletes too assignments.

 

See the video https://www.dropbox.com/s/sf0dlp5rra57vde/BUG UNDESIGNATE.mp4?dl=0

 

[zildac]

I think this issue (JDAM?) is already known about. Has been around for a couple of OB's as I recall now.

[Recluse]

Reported here, but Haven't seen any updates.

 

 

 

[Recluse]

Regarding:

 

 

Has this been determined to be CORRECT AS IS or is there any chance it will be changed to work the way it used to work i.e. Saving coordinates during a STEP or change from TOO1 to TOO2 and not deleting all coords with an UNDESIGNATE?

[Vanguard]

Bump

[Hammer1-1]

Id like info on this as well...

[dorianR666]

+1

this is a pretty big bug

[Belphe]

I'm also very interested in this being addressed. Please, explain the correct functionality.

[dorianR666]

On 9/7/2021 at 12:15 PM, Belphe said:

explain the correct functionality.

The old behaviour was correct. Hopefully ED will revert the change.

[Recluse]

<sigh>  nothing yet in the latest Open Beta 

[BIGNEWY]

Fix should be in the next patch, please wait for change log for confirmation. 

You will be able to designate using the TDC depress. 

thanks