Bayonet last edited by
I built a mission to interdict a column of tanks moving from steer point 3 to 4. I’m carrying AGM 65s. When I approach, they have moved away from 3 which I had locked up on the FCR in GM mode. So, they do not show up in the TGP.
I can, however, see them visually to the right of my nose. All switches are armed and ready to go.
As I can easily roll in on them, I press the OSB to switch from PRE to bore. But, it changes to PTR which is something I haven’t seen before. Repeated pressing of the OSB has no effect, it stays on PTR.
Can you tell me what PTR is and what I’m doing wrong please.
drtbkj last edited by
Not sure what PTR is. The Maverick modes are PRE, Bore(my personal favorite), and VIS.
The best way to cycle through the 3,btw, is with the cursor enable.
From BORE, you TMS forward to ground stabilize, then you’re good to go on your WPN display.
I hope that helps!
Dracfalcon last edited by
@Bayonet - Do you mean WPN or TGP display? If you mean TGP, that may be where your problem is.
Agave_Blue last edited by
Frederf last edited by
PTR I assume is “pointer” as in the NVG-compatible laser wavelength that allows NVG-wearers to see a line of laser light from the TGP to the surface. But that’s not a feature in BMS but might be modeled as the text label as it is a feature of the real article. So the designator-pointer is set to be a pointer (the other options being the designator and both pointer and designator). So “PTR” is meaningless and is not a mode of anything in BMS.
Or it could be INR as in “inertial” which is a method of pointing the TGP LOS at a given location without using image analysis (image analysis being fundamental to POINT and AREA modes).
What’s wrong is:
1. Having expectations of how to use various targeting modes of the aircraft, TGP, and Maverick.
2. BMS not modeling accurately and completely the various targeting modes.
In the real F-16 PRE means FCR initial aiming, VIS means HUD initial aiming, and BORE means direct WPN format manipulation. There is also a method that cues the Maverick to track what the TGP is tracking. We don’t get that last one in BMS at all. The classic frustration in BMS is trying to use Mavericks and the TGP together which highlights the giant hole in the avionics modeling in BMS. The thing that makes the TGP and Maverick work perfectly together is simply missing from the sim. So realize if you want to use the TGP to improve Maverick delivery you must go about it in the wrong, backdoor, and less easy to use way compared to reality.
PRE modeling in BMS is pretty accurate to the real thing. It wants you to find (and lock) an FCR return and then shifts control over to the Maverick for fine control, tracking, and shooting. For most BMS pilots this mode is sufficient for 99% of all FCR-related Maverick employment. Even incorporating the TGP as an improved sensor to VID on the Maverick LOS is pretty straightforward. The only important fact to know is that the Maverick is not able to be slewed until after the FCR is locked onto a return.
VIS modeling in BMS isn’t too bad either. It pretty much works like DTOS for bombs but the HUD box cues the Maverick.
BORE is badly modeled in BMS. In BMS you can make HUD SOI and slew the bore cross around like VIS which is completely impossible in the real jet. In reality the bore cross never moves no matter what and the HUD can never be SOI. BMS’s BORE mode is instead some really weird mix of PRE (FCR in mapping) and VIS (HUD designation).
Assuming the case of attacking stationary or moving vehicles starting from potential targets acquired FCR and verified with TGP prior to firing these are my suggested actions:
1. Prepare the whole mess, FCR GM/GMT as appropriate, TGP deployed TV or IR as appropriate, Mavericks on timed out and covers removed for all missiles to be employed in the attack.
2. Set MFDs as FCR and TGP on left and WPN on right. Start with the MFDs in FCR and WPN shown.
3. Put the FCR cursors on a likely target and lock one up. The Maverick should now be SOI automatically.
4. Cycle LMFD to display TGP format but retain WPN as SOI format.
5. Slew the Maverick as normal over potential targets using the TGP in narrow+zoom to have a closer look.
6. Never cause the TGP to break slave from the other sensors.
There are other possible situations and desires that suggest other actions but I think this matches a very common case.
Bayonet last edited by
Thank you all, yes basic mistake.
I was using the TGP rather than WPN.
Thanks for your comprehensive reply Frederf
SLangner last edited by
Bayonet, Frederf’s comprehensive reply included the first thing I thought of - GMT air-to-ground radar mode, then switch to the weapon, since the Maverick is its own TGP, as it were.
cptmtge last edited by
also, if you cannot see the column in GM use GMT as they are moving