BUG Report: Maverick FOV broken
Reported before: Maverick field of view can be broken at times.
I don’t know the exact sequence to reproduce this, but to me it is easy: I have a KOTAR Range mission, where I have (practice bombs,) Mavericks (65D) and GBU12s. I use both TGP, FCR and WPN to pick targets. I use also MARK steerpoints on the target, and use PRE mode to find the target I have picked earlier. I fly over the range, turn back and over the range etc. With this configuration it is easy to see that at times the Maverick is looking aft or some other strange direction.
Probable scenario (can’t confirm right now, will do later if need): find target with radar and or TGP, MARK it, use the new STPt for re-finding the target if turnin back. Switch to WPN, especially when tracking target on TGP, and Maverick may be seeing places it shouldn’t.
if your maverick or tgp are in slaved mode (pre) then they will point to wherever your radar is looking.
If you use a mark-point, and the radar is in stp mode, it’ll center on the mark-point, and so will your TGP and Maverick, if they are not ground-stabalized
The maverick isnt slaved to the TGP if I recall correct? Only to FCR. Or did it point elsewhere anyway?
There are two items in this issue:
1. the maverick LOS limits. My bug report considers this. At times it is possible to have the maverick look where it shouldn’t. Like backwards. However the breaking condition may be related to #2 below.
2. Maverick or TGP slave to FCR (which can be guided together with TGP help… thus in practice slaving mav to TGP). This seems to be relatively clear: if you do not have FCR visible on an MFD, it will give strange problems both with FCR cone update on the HSD and Mav/TGP slaving to FCR or STP. If you put the FCR again visible, then it’s focus will be guided correctly. So the FCR guidance is depending on the FCR visibility on the MFD, which obviously is not correct.
An old thread from 2011, but the problem still exists. Today I had a Maverick looking backwards at Kotar range (BMS 4.33.5). This is physically impossible. Is this issue addressed in the past?