Maverick Crosshair blinking and blinking
-
An issue with the mavericks I’ve been having is that they keep blinking (ie they have no lock) until it’s too late (ie I get too close and am rewarded with a SAM). I know about the “keyhole”, but it doesn’t seem to do help that I keep the blinking crosshair in the (imaginary) keyhole, it still keeps blinking. I was told that keeping the wings level helps, but as I approach it’s very difficult to do so. Any advice? Maverick locking seems to be very haphazard, sometimes you get solid crosshairs immediately, sometimes you have to wait indefinitely.
Thanks in advance for any advice! -
We’ve all been there and share your pain. Mavericks require more patience and practice than most other weapons (IAMs). What altitude are you attacking from… are you coming from too high… too much of a dive… if your unsure of the run, turn cold and try again…
-
Ionnnis, Quasi is right. If the cross hair doesn’t stop blinking, back off and try again. You have baby Mav’s, including not too pulling too many g’s on you way to the target. I try to avoid >4g, but that may be a bit conservative. Also, try launching wings level and at 1g and in a 5-10 degree dive. Also avoid long range shots. About 8 miles seems to be the sweet spot.
-
An issue with the mavericks I’ve been having is that they keep blinking (ie they have no lock) until it’s too late (ie I get too close and am rewarded with a SAM). I know about the “keyhole”, but it doesn’t seem to do help that I keep the blinking crosshair in the (imaginary) keyhole, it still keeps blinking. I was told that keeping the wings level helps, but as I approach it’s very difficult to do so. Any advice? Maverick locking seems to be very haphazard, sometimes you get solid crosshairs immediately, sometimes you have to wait indefinitely.
Thanks in advance for any advice!when everything else is fulfilled and it is still blinking go to expand view on the Mav screen, and see if it will stop blinking once you expand. It doesn’t make any sense to me why it should but it does and target will be hit upon firing then.
-
Ionnnis, Quasi is right. If the cross hair doesn’t stop blinking, back off and try again. You have baby Mav’s, including not too pulling too many g’s on you way to the target. I try to avoid >4g, but that may be a bit conservative. Also, try launching wings level and at 1g and in a 5-10 degree dive. Also avoid long range shots. About 8 miles seems to be the sweet spot.
G’s have nothing to do with the pointing cross. 3 factors can cause the pointing cross to flash
- You are not in the keyhole prior to launch
- You exceed lock on limits
- FOV.
In order to get a valid track, the bank angle during lock on (the time you TMS up) should not exceed 30 degrees . If you do, it will l result in an invalid track.
If the pointing cross flashes while you are within the AGM65 keyhole, you have exceed the lock on limitations. Break lock and try again.
Also, the missile should be launched in NFOV whenever possible.
Launching at WFOV may cause a loss of track after launch.As for the range, the MLE works just fine. If you are within the MLE and have a steady cross, launch away.
-
when everything else is fulfilled and it is still blinking go to expand view on the Mav screen, and see if it will stop blinking once you expand. It doesn’t make any sense to me why it should but it does and target will be hit upon firing then.
From the BMS -34 (\Falcon BMS 4.33 U1\Docs\Falcon BMS Manuals folder):
“There is a significant increase in probability of hit for missiles launched in NFOV over missiles launched in WFOV.
Advantages of NFOV are improved target identification and increased launch range. Missiles should be launched in
NFOV whenever possible. Launching at WFOV may cause a loss of track after launch.” -
… including not too pulling too many g’s on you way to the target. I try to avoid >4g, but that may be a bit conservative.
From memory I think the limit (during testing for 4.33) is about 6.5G, when you start to get H(ung) indications on the SMS page when you pickle; although the damn things create so much drag you would be hard-pressed to pull 6.5G except in an emergency, when you certainly don’t want them under your wings.
-
G’s have nothing to do with the pointing cross. 3 factors can cause the pointing cross to flash
- You are not in the keyhole prior to launch
- You exceed lock on limits
- FOV.
In order to get a valid track, the bank angle during lock on (the time you TMS up) should not exceed 30 degrees . If you do, it will l result in an invalid track.
If the pointing cross flashes while you are within the AGM65 keyhole, you have exceed the lock on limitations. Break lock and try again.
Also, the missile should be launched in NFOV whenever possible.
Launching at WFOV may cause a loss of track after launch.As for the range, the MLE works just fine. If you are within the MLE and have a steady cross, launch away.
Please clarify me what is: “You exceed lock on limits” and what is MLE. Thanks
-
MLE : missile launch envelope BMS-34 3.2.7.8
Lock on limits : During time of lock on do not exceed 30 degrees of bank angle. This will result in a invalid track.
-
make sure you don’t tank or pitch too hard.
-
Again, so much information I was unaware of. It seems that my decision to register was good.
Indeed, I seem to be coming from quite high when attacking, as I try to be off the range of flak etc. Furthermore, I was completely unaware of the NFOV engagement. Will try all that first chance I get! -
Everything you need to employ Mavericks successfully is in the –34 AGM-65 chapter; I really recommend it. Trying to use Mavericks without reading this chapter is just asking to be frustrated.
-
G’s have nothing to do with the pointing cross. 3 factors can cause the pointing cross to flash
- You are not in the keyhole prior to launch
- You exceed lock on limits
- FOV.
In order to get a valid track, the bank angle during lock on (the time you TMS up) should not exceed 30 degrees . If you do, it will l result in an invalid track.
If the pointing cross flashes while you are within the AGM65 keyhole, you have exceed the lock on limitations. Break lock and try again.
Also, the missile should be launched in NFOV whenever possible.
Launching at WFOV may cause a loss of track after launch.As for the range, the MLE works just fine. If you are within the MLE and have a steady cross, launch away.
Leach, I wasn’t speaking of over g’ing the missile as directly affecting the cross. However, in the past I have seen Mav’s become unusable due to over stressing. If you break the missile, it ain’t going to lock. Whether that is still modeled is a good question
-
Leach, I wasn’t speaking of over g’ing the missile as directly affecting the cross. However, in the past I have seen Mav’s become unusable due to over stressing. If you break the missile, it ain’t going to lock. Whether that is still modeled is a good question
When the station has failed, the SMS missile status from RDY will change to MAL after an attempt to launch. This does not affect the pre launch track. The missile will lock but it will not launch
-
Thank you all for your answers. The “zooming in” information did it for me. It really made the crosshairs stop blinking. Have a happy new year, guys!