TADS-designated SHOT marks appear offset

[GCRev]

I was testing out the new C-SCOPE feature and I may have encountered a bug with the positioning of laser-designated TADS SHOT marks. In a cold-start scenario and after a full four minute ground EGI alignment, there still seems to be an offset. I also tried resetting the INUs in flight, but I didn't see a change in behavior. This behavior occurs regardless of missile type, so I think that it's related to the TADS logic and not the 114Ks or 114Ls.

I can't remember whether this is a known issue (a general offsetting problem with the TADS) that is under active investigation, or it's a new issue that popped up with the recent release. Hopefully the attached track + miz files provide a repro. I was able to play back the track file and observed the same outcome.

Hot starting doesn't seem to have the same issue - I tested on the "Live Fire" instant action mission on Caucasus and didn't see the same offset. Fortunately, FCR targets and SHOT marks don't have this issue and are spot-on.

The following post could be related to this, since it also has to do with a TADS-derived global coordinate. I didn't see a solution yet in the linked post.

I think this issue also manifests in this "INU tracking" problem that was identified earlier in the sense that the position fed to the Lima from the designator can be so far from the intended target that the Lima effectively "misses" it. Having the ability to see the shot marker makes it simpler to visualize. I'm optimistic that resolving this will also fix some of the tangential issues.

ah64_tads_offset.trk ah64test.miz

Edited May 31, 2024 by GCRev

[FalcoGer]

I've had similar experiences, the shot at cues sometime even appearing in the air and several tens of meters away from the target.

[Zarma]

I guess it's the same problem as the stored targets are offset in MP.