Jump to content

Recommended Posts

Posted

Okay, so I go out and find my target with the radar and I get the seeker head looking in the right direction. Then I should be able to press and hold TDC depress and I should be able to use the TDC slew hat switch to slew the seeker head onto the target. But I can't get it to slew. I have the TDC depress on the joystick so I can press and hold it and I know it's working because I can lock a target on the radar with it. But when I have the AGM-65F view set as the SOI and press and hold the TDC depress and move the TDC hat, nothing happens. What am I missing here? I watched a bunch of tutorials on this and they always do exactly what I just described, and they can slew the Maverick. For some reason, I can't. I have found that I can eventually get the radar lock close enough to get the seeker head to lock onto the target, but obviously that isn't the most efficient way to do this. I need to be able to slew the AGM-65F seeker head. What am I doing wrong?

AMD Ryzen 9 5900X @ 4.4ghz, 64gb DDR4 @ 3200mhz, GeForce RTX-3060ti 8GB DDR6, Three KTC 32" QHD monitors @ 165hz, Rosewill 80plus Bronze 1000w, Corsair Hydro H100i, 2tb M.2  SSD for OS, Two 3tb HDD, 2tb SSD for DCS, P3D, Star Citizen, Sound Blaster Zx, Thermaltake Overseer RX-I, Winwing Orion 2 HOTAS F-15EX throttle and F-16EX stick, Winwing 3 MFD MIP with FA-18 UFC and F-16 ICP, TrackIR 5, Surround Speakers & Subwoofer, Oculus Quest 2 VR.

:joystick::pilotfly:

Posted (edited)

My understanding is that you have to UNDESIGNATE to slew the Maverick off of a target is it slaved to by another sensor.  I did think that if you turn REALISTIC TDC slew OFF, you can slew without undesignating as GazAce does in this video. He does say that it doesn't work the same way with ATFLIR. I usually have REALISTIC TDC SLEW on, so if I need to slew the Maverick Seeker, I undesignate first whether using LITENING or ATFLIR.  When the AG RADAR is used for the initial lock, I think the UNDESIGNATE is necessary with or without Realistic TDC slew, but you CAN hand off a radar lock to the Targeting Pod first, which, while clunky, is something I usually do  to make sure of the targets. 

After the first UNDESIGNATE, the MAV seeker remains ground stabilized and the SLAVED position. After it fires, you need to re-slave it from BORESIGHT.

 

Are you using "realistic TDC slew"? If not, than for those of us that leave that on, I think you'll need to undesignate before slewing

 

I always have that option unticked
 

 
 
Edited by Recluse
Posted (edited)
1 hour ago, RoxSy said:

No change with or without the TDC Special Option and same thing with ATFLIR and Litening pod.

Yeah, I gave it a try, but I DO believe this is CORRECT AS IS. Once a target is designated by another sensor, the AGM-65F slaves to it. In order to slew independently, you need to either undesignate or start with no target undesignated and slew the Maverick seeker as the MAIN Sensor.

I have no references to support this, but it seems to make sense to me.  I haven't flown the A-10C even though I own it. Does it work differently there?

...come to think of it, in the HARRIER you CAN slew the Maverick Seeker after slaving it. I had to remap my TDC DOWN from the depress function of the TDC because it kept slewing when I didn't want it to.... HMMmmm

Edited by Recluse
  • Thanks 1
Posted
3 hours ago, Recluse said:

I haven't flown the A-10C even though I own it. Does it work differently there?

Yes you can ground stabilize the Mav with TMS aft-short. And then slew it to targets. I don’t think the Hornet can ground stabilize. The A-10 is much easier. In the Hornet you have to basically bore sight the Mav while flying and slew at the same time if you’re just using it’s sensor alone. 

i9-14900KS | ASUS ROG MAXIMUS Z790 HERO | 64GB DDR5 5600MHz | iCUE H150i Liquid CPU Cooler | ASUS TUF GeForce RTX 4090 OC | Windows 11 Home | 2TB Samsung 980 PRO NVMe | Corsair RM1000x | LG 48GQ900-B 4K OLED Monitor | CH Fighterstick | Ch Pro Throttle | CH Pro Pedals | TrackIR 5

Posted
9 hours ago, SharpeXB said:

Yes you can ground stabilize the Mav with TMS aft-short. And then slew it to targets. I don’t think the Hornet can ground stabilize. The A-10 is much easier. In the Hornet you have to basically bore sight the Mav while flying and slew at the same time if you’re just using it’s sensor alone. 

Thanks for the info.  In the Hornet, as I mentioned, once you undesignate the target, the uncaged Maverick DOES remain ground stabilized at that point for the selected missile and you CAN now slew the seeker around (TDC HELD DOWN) and it will lock onto a target when you release TDC.  Only works for THAT missile. The next one will be boresighted.  Again, I have no way of knowing if this is CORRECT behavior or not, just that it works that way.

Posted
8 minutes ago, BIGNEWY said:

there is an issue with undesignate and TDC when used with TGP and WPDSG, that will be resolved soon. 

 

Wow.. that is news!!   Can you expand on what the issue is? (the inability to slew when slaved or the continued ground stabilization when undesginate.. or OTHER) and what should the "Correct" behavior be??

Posted
Wow.. that is news!!   Can you expand on what the issue is? (the inability to slew when slaved or the continued ground stabilization when undesginate.. or OTHER) and what should the "Correct" behavior be??
Currently, if you have the FLIR on a tracking mode (SCENE/ATRK or AUTO/PTRK), but the TDC priority is assigned to another page (say, the Maverick page), pressing the undesignate button does not exit the FLIR tracking mode and thus does not remove the designation, which means that you cannot manually slew the Maverick.

The current workaround is to move the TDC priority back to the FLIR page, undesignate and then move TDC priority back to the Maverick page.

The correct behavior would be that any designating sensor, including the FLIR, will exit its designating mode when the Undesignate button is pressed on the stick.
  • Like 1
  • Thanks 1

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Posted (edited)
25 minutes ago, Harker said:

Currently, if you have the FLIR on a tracking mode (SCENE/ATRK or AUTO/PTRK), but the TDC priority is assigned to another page (say, the Maverick page), pressing the undesignate button does not exit the FLIR tracking mode and thus does not remove the designation, which means that you cannot manually slew the Maverick.

The current workaround is to move the TDC priority back to the FLIR page, undesignate and then move TDC priority back to the Maverick page.

The correct behavior would be that any designating sensor, including the FLIR, will exit its designating mode when the Undesignate button is pressed on the stick.

Well that's odd because I have ALWAYS been able to do just that:

-Desginate with WPDSG/FLIR etc..

- Move TDC to MAV page and Uncage if it doesn't happen automatically.

- With TDC on MAV page, UNDESIGNATE

- HOLD DOWN TDC DEPRESS and SLEW. 

I JUST tried it again and it worked fine as it did when I tested it to write my previous responses.  (Don't think this made it into the latest Open Beta, so I doubt it was fixed just now)

Ahhhh OK.. I did not go into POINT TRACK/SCENE. In that case it did not release the lock for slewing.

It works fine when slaving the FLIR to a WPDSG OR Slew the LITENING POD and designate with TDC DEPRESS then follow the steps above.

Edited by Recluse
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...