Santi871

I've attached the gbu-38 track to the already existing gbu-38 accuracy bug report, thanks.

It is reported

There's no "WPDSG mode". WPDSG creates a designation at the selected waypoint, nothing else. From there you can do as you please with the designation.

TWS isn't providing midcourse updates atm, it's reported. LTWS AMRAAM guidance is possible, but to ensure not losing the L&S, firing an AMRAAM in RWS should cause it to automatically switch to TWS with AUTO centering (it's missing, so it's reported). From there, going back to RWS is still possible, obviously for now you don't need to go back since it doesn't switch to TWS in the first place.

No, I'm not part of ED, I just help test.

Well, I don't know exactly what ED's plan is. Like I said, everything I said is "as far as I know" and based on my own research.

What should happen afaik is that while the FLIR is in area track, it's not possible to no-action slew it (slewing without depressing the TDC). It would be necessary to hold the TDC down while slewing it, and once you release the TDC the designation will be updated to the new aimpoint and the pod will enter area track again. If it worked that way then the TGT would always coincide with the FLIR LOS. For point track the designation should "move" by itself with the tracked aimpoint.

Np, I should've commented it earlier. I don't have the power to edit post titles but if one of the community managers sees it I'm sure they will change it.

Hi, it's not a bug. The FLIR is slaved to the designated target at all times. VVSLV is not available while designated. Thanks for the track though.

No need, it's already reported. Thanks though.

Yes, it's correct.

Actually, it's not a matter of ownship vs offboard, but rather radar-only vs non-radar-only. Although given that right now the radar is the only onboard sensor that can create MSI tracks, those are equivalent.

I don't know why the manual says different, but friendlies should get ranked.

I brought this up a while ago and it is correct, what's not correct in this case is SA page.

This is not a bug, currently the HUD TD box HAFU indicates offboard ID.

Reported, thanks.

Yes, you'd have to wait until you've pickled the last bomb to WPDSG. It's not a matter of agreement nor opinion. If you have any reputable source that says otherwise, feel free to forward it to any ED team member and it will get looked at. I've checked about 4 times now and the wording is very clear.

Markpoints mark the current A/G designation if it exists, or the overfly point if it doesn't. The current undesignate functionality is correct as is. It doesn't matter if you can come up with a better way to implement that functionality - ED modules are modeled according to the documentation. PS: if it makes you happy I can ask Wags to review it too

You can create a waypoint at the target area and WPDSG to observe after pickling. When markpoints are there you could do the same by saving one of the targets into a markpoint then WPDSG'ing the markpoint. You can also use VVSLV to get the pod on the target area again too.

It shows correctly for me, could you try a repair and let me know if that fixes it?

The current implementation is correct. The pod will snowplow in an undesignated condition. To avoid snowplow when designating TOO targets, don't undesignate until after having designated the target for your last station in your sequence.

A track would be greatly appreciated.

What is your source for this?

No, the selected stations (the current station + any other station selected in QTY) are automatically continuously updated with the A/G designation in TOO mode.

It is not necessary to undesignate before STEPping to the next station, unless you are at the last station and doing it will take you back to the 1st one (to prevent overwriting the 1st station TOO target with your current designated target). Undesignating will return the FLIR to snowplow, it's not a bug.