cannot reproduce Slaving TADS to Location previously generated by TADS results in offset TADS LOS

[Zarma]

Unable to reproduce. Next it happens will save the track but will be a big one as it's in MP mission....

[Zarma]

OK could get a track. Used cold start Apache and flew less than 20 km to the targets.

T02, T03 and T04 are all to the right of the targets I stored when slaving back on them.

Hellfires did hit, but I think it was a lucky shot as the flew on the correct side of the target and still could see them.

cold apache laser point off.trk

Edited August 9, 2024 by Zarma

[Zarma]

And here is a track where the radar hellfire just fell short after using George to designate a target

CASCAP_Infinity_Afghanistan_by_Zarma_3.94-20240810-205351.trk

[Zarma]

Way harder to kill SA19 / SA15 / SA8 now /cry

[Floyd1212]

On 8/9/2024 at 6:00 PM, Zarma said:

T02, T03 and T04 are all to the right of the targets I stored when slaving back on them.

I replayed your track and saw the offset you were experiencing.

I replayed it a second time, and took control after you flew to the AO and lased and stored the targets myself, and had the same results. 

[Zarma]

@BIGNEWY @NineLine I attached two tracks in the previous messages.

Best regards,

Edited August 16, 2024 by Zarma

[Zarma]

Seems fine on Caucasus. Maybe linked to the new map ?

[Zarma]

Just tested on Afghanistant, still bugged

Edited November 5, 2024 by Zarma

[Zarma]

any news ?

[Zarma]

tested, now the problem is also there on caucasus......

 

[Zarma]

Come on not a single reaction from devs ???

[papaz]

I experienced the above issues myself. They are caused by INU drift, even worse if a mission/server disabled 'Unrestricted SATNAV'.
The only way to mitigate the problem is to reset INU 1, and then INU 2 alternately, every now and then, which is probably not a real procedure.