[AGM-65] How to hit my GMT's?
-
Narrow FOV, verify locked target, verify steady cross within keyhole, verify range, bank, pitch, speed and other parameters is within limits (described in the manual).
This is it. The “new” Mavericks in 4.33 have much tighter launch parameters. I myself have launched a few into the ground relearning my Rifling.
Max realism we seek though and I wouldn’t have it any other way…bring it on!
-
Another (add on) question:
Is it possible to hit several targets with several AGM-65’s in PRE mode?TIA
Greeting
Earlybite -
Yes and no. Each missile needs to be commanded into a valid track with a valid firing solution. You cannot control more than one missile at the time on any given station/pod. You CAN however command a track, MSL STEP to the next station and repeat, to then ripple 2, 3 or 4 (depending on no. of stations carrying Mavs) missiles, but there’s not much of an advantage to that. There’s also the TGP handoff procedure which is the topic of about 50% of the threads in this sub-forum. Here the “rippling” has perhaps a slight advantage over the normal find-designate-fire-repeat procedure, but not by much, and many argue that’s it’s not really a realistic procedure either. All of this are things done in PRE-mode. The missiles will not behave as SDBs where you can toggle steers and deliver 8 bombs to different targets in 8 seconds.
-
This is it. The “new” Mavericks in 4.33 have much tighter launch parameters. I myself have launched a few into the ground relearning my Rifling.
Max realism we seek though and I wouldn’t have it any other way…bring it on!
…I wish the thermal modelling was more realistic for all of the EO sensors.
-
Yes it is but you have to keep your eyes on a swivel,
Solid Lock (In Weapon Page)
On or just below FPM (not under the nose or more then 5-8deg in azimuth, depends how close you get)
And their not about to crest a hill.
Be content with two off the rails & then go around before you get a SA 7 or similar up the pipe.
-
Hi Early bite - you made no mention of BORESIGHTING your Mavs before your attack … did You?
If you did and still missed I suggest the obvious … and Youtube :0)
-
Yes it is but you have to keep your eyes on a swivel,
Solid Lock (In Weapon Page)
On or just below FPM (not under the nose or more then 5-8deg in azimuth, depends how close you get)
And their not about to crest a hill.
Be content with two off the rails & then go around before you get a SA 7 or similar up the pipe.
Solid Lock? Is TMS-UP solid enough?
What about FPM exactly? _No terrain breaking…, clear, normal.
For further doing…_
-
Hi Early bite - you made no mention of BORESIGHTING your Mavs before your attack … did You?
If you did and still missed I suggest the obvious … and Youtube :0)
No, I havn’t!
I’ve made it like in 4.32… FCR, slew over the column, WEAPON page, uncage, fine adjust, TMS-Up, fire…, uncage, fine adjust, TMS-UP, fire…, and so on. 6 rifles, 6 hits in ~10 sec…
But it seems, that this “method” will not work any more in 4.33…Greeting
Earlybite -
No, I havn’t!
I’ve made it like in 4.32… FCR, slew over the column, WEAPON page, uncage, fine adjust, TMS-Up, fire…, uncage, fine adjust, TMS-UP, fire…, and so on. 6 rifles, 6 hits in ~10 sec…
But it seems, that this “method” will not work any more in 4.33…Greeting
EarlybiteWas your Mav- target cross flashing after lock and before you shoot?
Cheers,
LS -
Do you have a steady cross in the WPN page? did you actually read the Mav section in the BMS 3-4 to the details? because it is important to understand and remember the details.
…I wish the thermal modelling was more realistic for all of the EO sensors.
Yes that would be nice indeed, hopefully at some point in the future we will get to that… But work must be done graphics wise before then.
Hi Early bite - you made no mention of BORESIGHTING your Mavs before your attack … did You?
If you did and still missed I suggest the obvious … and Youtube :0)
Saying for the 100th time, BORESIGHTING is NOT a must if you aren’t going to do TGP Handoff. Nice yes, but not a must.
-
@I-Hawk:
I´m not pretty sure, because I hadnt an eye on it.
But, just flew ther TE again and had four hits with four AGM-65D. And yes, I hadn´t fired as the cross was flashing…
So, thanks a lot, sir!But I´m not able to shoot more then two missiles on two different targets!
It seems that the WEAPON page / seeker slips away after a shot. Even if there are still ~8nm “available” to the targets. In a worst case the seeker is pointer to an area which “miles and miles away” and til I slewed back the range will get to short to take another shoot.
(All shots are in PRE mode with FCR cursor over the targets (but not bugged) and not with BORESIGHT…)Any help for this?
Greeting
Earlybite -
Well… if you didn’t do boresighting on the Mavs stations, then every missile will be a bit “off” compared to the SPI/TD-Box position, that is expected. However “Miles and Miles away” is for sure not right, and I doubt if that is the case because if yes then I would have heard about it from many people, right?
-
Well… if you didn’t do boresighting on the Mavs stations, then every missile will be a bit “off” compared to the SPI/TD-Box position, that is expected. However “Miles and Miles away” is for sure not right, and I doubt if that is the case because if yes then I would have heard about it from many people, right?
Momentary I´m on Win-7, but as soon as I´m back to Linux Mint I will show a picture which shows where the seeker shows to (after firing a rifle) and where the column is… And IMO it is more then one, or two miles out.
First I thought it would be better if I have a better cursor position in the FCR, but no.
And then the problem is, that I do not know where to slew the AGM seeker (to the bottom and the right, to the top and the left?)…Greeting
Earlybite -
Everyone should learn and be comfortable with EO-BORE mode delivery of Maverick before concerning themselves with more integrated delivery methods. The emphasis is that the Maverick immediately before launch is entirely self-supporting. What sensors, modes, and methods used to get the Maverick in the tracking ready-to-fire state are irrelevant immediately before firing. Much like an uncaged AIM-9, it’s all about the missile and nothing else.
Maverick/rack misalignment is in angles not meters. So the distance in the ground plane from the uncalibrated LOS to the calibrated LOS is entirely dependent on the geometry of the situation. I found it’s roughly the radius of the NFOV of the Maverick. There’s a good chance your target won’t be visible in NFOV but you’ll see it in WFOV.
-
Everyone should learn and be comfortable with EO-BORE mode delivery of Maverick before concerning themselves with more integrated delivery methods. The emphasis is that the Maverick immediately before launch is entirely self-supporting. What sensors, modes, and methods used to get the Maverick in the tracking ready-to-fire state are irrelevant immediately before firing. Much like an uncaged AIM-9, it’s all about the missile and nothing else.
Maverick/rack misalignment is in angles not meters. So the distance in the ground plane from the uncalibrated LOS to the calibrated LOS is entirely dependent on the geometry of the situation. I found it’s roughly the radius of the NFOV of the Maverick. There’s a good chance your target won’t be visible in NFOV but you’ll see it in WFOV.
+1, and very well stated.
-
Sudden system-philosophical thought: Why is it that the system is able to interpret what the Mav’s doing regardless of configuration (i.e. show the seeker’s exact position on the HUD wether it is boresighted or not), but not allign it with SOI unless you go through boresighting? I mean, the system evidently has all the data it needs, why just not put one “dot” on top of the other?
Happy new year, guys (and happy new Mav-questions)! :drink:
-
If the “1” and “2” circles are exactly over their true LOSs despite non-zero calibration errors then that is a shortcoming of FBMS. In reality given misalignment the HUD elements and the true LOS of the missile would differ.
-
Sudden system-philosophical thought: Why is it that the system is able to interpret what the Mav’s doing regardless of configuration (i.e. show the seeker’s exact position on the HUD wether it is boresighted or not), but not allign it with SOI unless you go through boresighting? I mean, the system evidently has all the data it needs, why just not put one “dot” on top of the other?
Happy new year, guys (and happy new Mav-questions)! :drink:
I didn’t understood exactly the meaning here, but of course the missile LOS circle in the HUD reflects the missile LOS (which in PRE mode means SPI position + boresight error).
The Boresight error is just a delta added to wherever the missile would have looked if it had no boresight error.I guess this statement sounds dumb, but that’s what it is :mrgreen:
-
…no.
The HUD LOS symbol represents the idealized perfect missile LOS not necessarily the actual LOS. The circle represents where the airplane thinks the missile is looking but it can be wrong (think AIM-9 and wingtip flex). If the missile is crooked to the left then the video will show looking to the left despite the HUD symbols pointing straight ahead. The pointing cross will also reflect the deviation from the seeker gimbal from center of its motion. If you slew the LOS circle in the HUD over the item and look at the weapon video the view will be left of the HUD circle placement. All the airplane can know is that if the missile reports looking straight ahead that it must also paint the HUD symbol straight ahead. The need for calibration is that the missile’s straight ahead may be different than the airplane’s. When calibrated the airplane understands that missile-straight is airplane-left and to achieve airplane-straight seeker pointing to direct the missile to look right.
For example if the Maverick is slewed over a target and locked the circle in the HUD might not be over the real object. When boresight calibration is pressed it is the circle that moves, not the missile LOS.
-
…no.
The HUD LOS symbol represents the idealized perfect missile LOS not necessarily the actual LOS. The circle represents where the airplane thinks the missile is looking but it can be wrong (think AIM-9 and wingtip flex). If the missile is crooked to the left then the video will show looking to the left despite the HUD symbols pointing straight ahead. The pointing cross will also reflect the deviation from the seeker gimbal from center of its motion. If you slew the LOS circle in the HUD over the item and look at the weapon video the view will be left of the HUD circle placement. All the airplane can know is that if the missile reports looking straight ahead that it must also paint the HUD symbol straight ahead. The need for calibration is that the missile’s straight ahead may be different than the airplane’s. When calibrated the airplane understands that missile-straight is airplane-left and to achieve airplane-straight seeker pointing to direct the missile to look right.
For example if the Maverick is slewed over a target and locked the circle in the HUD might not be over the real object. When boresight calibration is pressed it is the circle that moves, not the missile LOS.
Yes yes indeed you are correct, and BMS code is wrong indeed from that aspect, I guess I just missed that, thanx!
I will fix it.