correct as is MAVF can't be slewed with target designation.

[Hulkbust44]

Just as the title says, with a target point designated the IMAV seeker will not slew. This makes following the AGM-65F employment procedures in A1-F18AC-TAC-300 impossible. 
In the track you can also see another issue as the HUD designation is not being made from the point of the VV.

MAVF.trk

Edited January 30, 2022 by Hulkbust44

[BIGNEWY]

Can I just check you have realistic TDC ticked in your special options? and can you untick it and tell me if you have better success. 

 

I have reported, it seems to be specific to realistic TDC option and using WPDSG.

 

thanks

[Harker]

10 hours ago, BIGNEWY said:

Can I just check you have realistic TDC ticked in your special options? and can you untick it and tell me if you have better success. 

 

I have reported, it seems to be specific to realistic TDC option and using WPDSG.

 

thanks

I tested with realistic slew enabled and disabled. No difference. The problem is that, according to the TAC-300 manual, the seeker can be slewed while the designation is still present. Page 93 (98 of the pdf). This is not possible in DCS.

In DCS, if we want to slew the seeker manually, we need to undesignate and lose the designation (or not have one in the first place). Having to undesignate in order to regain slew capability is not described anywhere in that document (which has detailed, step-by-step checklists of all the possible ways to employ weapons).

[BIGNEWY]

11 hours ago, Harker said:

I tested with realistic slew enabled and disabled. No difference. The problem is that, according to the TAC-300 manual, the seeker can be slewed while the designation is still present. Page 93 (98 of the pdf). This is not possible in DCS.

Then our tests had different results, either way the team will look at my report

[CaptPickguard]

It may be prudent to check behavior with LITENING and ATFLIR, as the logic they follow with updating the target point differs quite drastically.

[MarcT-NL]

Wait what ?  I am confused. When I reported this on may 25th 2021 together with track and all, it was Just deemed "Correct as is". Now you are investigating ?

Am I missing something here ?

[BIGNEWY]

16 minutes ago, MarcT-NL said:

Wait what ?  I am confused. When I reported this on may 25th 2021 together with track and all, it was Just deemed "Correct as is". Now you are investigating ?

Am I missing something here ?

It was not reproduced in that report, and everything looked correct, we have now found the probable cause that was creating issues for some users. 

Now we wait while the team look into the issue 

thanks

[BIGNEWY]

Just an update on this it is correct as is, you have to undesignate to slew after designation.  

thanks