F/A-18C with L Maverick and Targeting Pod - Finding the target without a waypoint.

[Thorns]

 Need some help in the F/A-18C with the L maverick and using the T-pod.   Finding a target "without" a waypoint...I can put the triangle in the hud on the target location from a distance and depress TDC and the square doesn't go anywhere near where the triangle was pointing when you depressed TDC...almost impossible to find the target without flying around and searching blind.  Help!! 

[Tholozor]

The triangle represents the LOS of the Maverick seeker, not the targeting pod. You can't make a designation point using the Maverick.

Edited July 6, 2022 by Tholozor

[Thorns]

Thanks for your reply...what do you use?

 

[Tholozor]

You can create a TGT designation with the velocity vector. Sensor Control Switch forward (in NAV or A/G master modes) will assign the TDC to the HUD (denoted by a dot in the middle of the velocity vector). Depressing the TDC will create a TGT designation on the ground along the LOS of the VV. The targeting pod should automatically slave to the designation.

Alternatively, the targeting pod itself can also be slaved to the velocity vector. Double-pressing the NWS/Undesignate button on the stick will command VVSLV mode. With the TDC assigned to the FLIR page, depressing the TDC will create a designation and slave the pod to it.

If you have the JHMCS installed and turned on, the helmet can also be used to create a designation. SCS forward will also assign the TDC to the helmet when not blanked by the HUD (denoted by a dashed reticle in the middle of the HMD). Depressing the TDC will create a designation on the ground along the LOS of the helmet sight.

Edited July 6, 2022 by Tholozor

[Thorns]

Thank you sir!  Have a good day.

[Lane]

In addition, you can still use the radar in map or GMT mode ( for moving vehicle ) then slave the tgpod to the Point of interest (TGT Designation )

[Ala12Rv-Tundra]

On 7/7/2022 at 1:52 AM, Tholozor said:

You can create a TGT designation with the velocity vector. Sensor Control Switch forward (in NAV or A/G master modes) will assign the TDC to the HUD (denoted by a dot in the middle of the velocity vector). Depressing the TDC will create a TGT designation on the ground along the LOS of the VV. The targeting pod should automatically slave to the designation.

Alternatively, the targeting pod itself can also be slaved to the velocity vector. Double-pressing the NWS/Undesignate button on the stick will command VVSLV mode. With the TDC assigned to the FLIR page, depressing the TDC will create a designation and slave the pod to it.

If you have the JHMCS installed and turned on, the helmet can also be used to create a designation. SCS forward will also assign the TDC to the helmet when not blanked by the HUD (denoted by a dashed reticle in the middle of the HMD). Depressing the TDC will create a designation on the ground along the LOS of the helmet sight.

 

I need to try this, thx

[rfxcasey]

Side note, FLIR screen, box 'VVSLV' on the right, then put your velocity vector on your HUD onto the area you want to designate and hit the throttle designate button. Once you designate a target (or target area to search with your pod) with the velocity vector you can hit the markpoint 'MK1' button on the HSI and convert it to a mark point. You can do this to designate 9 separate markpoints. After you designate a markpoint hit the 'undesignate' button on your HOTAS. You can then designate a new target now by either slewing your pod (to another tank for example) or putting your velocity vector on another point and hitting the throttle designate button. Then hit the markpoint button again (will say 'MK2' now) to record the second markpoint. To cycle through the points you marked and automatically send your TGP back to them at will, cycle down the waypoints on the HSI with the arrows on the right until you get to the markpoints, then choose the markpoint you want e.g. 'MK1' and hit the 'WPDSG'. The way I like to work is, if I know a general location of baddies, I'll designate a point on the area with my velocity vector which will send my TGP camera to that point. Then I will create a markpoint for that location by hitting 'MK1' on the HSI so I can always go back to that point. Then I'll slew my pod around that area looking for targets, designating them and then converting each to it's own markpoint. This way, I can cycle back through my original area point and several marked targets with ease on my TGP. When you get to 'MK9' it will cycle back to 'MK1' and overwrite 'MK1' the next time you hit the button.

 

It is also possible to use a HARM missile to locate a SAM sight after which it will show a square box on your HUD at the location of the detected radar emissions. Then, with 'VVSLV' selected you can put your velocity vector symbol on your HUD into the box and hit designate. The TGP will now slew to the SAM sight. You can make a markpoint for the sight, then slew the pod around the site, designate targets and assign markpoints for each. I don't usually do this but it is possible.

Edited August 1, 2022 by rfxcasey

[Ramires]

Question concerning Hornet's AGM-65E and Harrier's AGM-65E:

I think this question might have already been asked but I couldn't find a topic for this subject:

The Harrier's AGM-65E (AGM-65E1) can only be used by buddy lasing procedure. In the F/A-18C targets may be marked by the target pod laser of the firing aircraft too. Does the F/A-18 carry the AGM-65E2 or L? DCS designated both as AGM-65E.

[Tholozor]

The reason the Harrier can't self-lase the 65E is because the TPOD and LMAV displays run on the same video line to the MFDs, it can only display one or the other. The Hornet doesn't have this problem (each pylon has its own dedicated video line), and can use the standard 65E with a TGP all day long.

The 65E2 on the Harrier uses a differing display logic that allows the MFDs to sort-of 'hot-swap-merge' the TPOD and LMAV videos displays with each other while maintaining TPOD control.

Edited October 22, 2022 by Tholozor

[Ramires]

9 hours ago, Tholozor said:

The reason the Harrier can't self-lase the 65E is because the TPOD and LMAV displays run on the same video line to the MFDs, it can only display one or the other. The Hornet doesn't have this problem (each pylon has its own dedicated video line), and can use the standard 65E with a TGP all day long.

The 65E2 on the Harrier uses a differing display logic that allows the MFDs to sort-of 'hot-swap-merge' the TPOD and LMAV videos displays with each other while maintaining TPOD control.

 

Thank you!