Jump to content

Recommended Posts

Posted

I'm using the Litening II Tpod with the AGM-65F - love the combo!. Yet, when I use waypoint designation, it gets me close by, but not right on the waypoint. At first I thought it was a range limit, but I waited until I was under 10nm from the target and still the same result. Am I missing something? Tried this on land and water targets.

Rig: Alienware Aurora R9 - 9th Gen Core i7 9700K 4.6GHz 8 Cores | NVIDIA GeForce RTX 3060 Ti 8GB GDDR6 | 2TB M.2 PCIe NVMe SSD | 64GB Corsair Vengeance RGB PRO SL DDR4 3200MHz XMP 2.0 | LG Series80 QNED 50in 4K 120hz | TM Warthog HOTAS w/F-18 grip | Logitech G Pro RP | 3 TM Cougar MFDs | TrackIR 5 Pro |

Modules: FC3 | F/A-18C | F-16C | A-10C II | F-14 | M-2000C | AV-8B | F-5E | JF-17 | P-51D | KA-50iii | UH-1H | AH-64D | F4U-1D | F-4E | Supercarrier | Combined Arms | Nevada | Persian Gulf | Syria | Normandy | Chanel | South Atlantic | Afghanistan

Posted

Ensure you are using precise coordinates, HSI->DATA (PB10)->WYPT (PB7)->BOX PRECISE (PB19). After that, ensure the coordinates you are trying to input are precise enough for the target. You can change between DD MM.mmm and DD MM SS.ss formats at HSI-->DATA (PB10)->A/C (PB6)-->LATLN (PB15).

 

For reference, approximate accuracy is listed below for the type of coordinate:

DD MM SS.ss - 0.3m

DD MM.mmm - 1.9m

DD MM.mm - 18.5m

DD MM SS - 30.9m

DD MM - 1,853m

 

Not applicable for FLIR designations, but always remember... accurate coordinates require all three axes (important for smart weapons)... so get an accurate elevation from the F10 map if required!

Posted (edited)
Ensure you are using precise coordinates, HSI->DATA (PB10)->WYPT (PB7)->BOX PRECISE (PB19). After that, ensure the coordinates you are trying to input are precise enough for the target. You can change between DD MM.mmm and DD MM SS.ss formats at HSI-->DATA (PB10)->A/C (PB6)-->LATLN (PB15).

 

For reference, approximate accuracy is listed below for the type of coordinate:

DD MM SS.ss - 0.3m

DD MM.mmm - 1.9m

DD MM.mm - 18.5m

DD MM SS - 30.9m

DD MM - 1,853m

 

Not applicable for FLIR designations, but always remember... accurate coordinates require all three axes (important for smart weapons)... so get an accurate elevation from the F10 map if required!

 

I'm not inputting coordinates; I have the way points already set up in the mission. All I should have to do is go to the SA screen, turn on way point, select the way point to use, and click the button WPDSG.

Edited by Wolf333

Rig: Alienware Aurora R9 - 9th Gen Core i7 9700K 4.6GHz 8 Cores | NVIDIA GeForce RTX 3060 Ti 8GB GDDR6 | 2TB M.2 PCIe NVMe SSD | 64GB Corsair Vengeance RGB PRO SL DDR4 3200MHz XMP 2.0 | LG Series80 QNED 50in 4K 120hz | TM Warthog HOTAS w/F-18 grip | Logitech G Pro RP | 3 TM Cougar MFDs | TrackIR 5 Pro |

Modules: FC3 | F/A-18C | F-16C | A-10C II | F-14 | M-2000C | AV-8B | F-5E | JF-17 | P-51D | KA-50iii | UH-1H | AH-64D | F4U-1D | F-4E | Supercarrier | Combined Arms | Nevada | Persian Gulf | Syria | Normandy | Chanel | South Atlantic | Afghanistan

Posted
I'm not inputting coordinates; I have the way points already set up in the mission. All I should have to do is go to the SA screen, turn on way point, select the way point to use, and click the button WPDSG.

If the waypoints are directly and precisely over the targets, then it should work well. I would guess that the waypoints aren't precisely over the targets, but slightly to the side. Either way, if it's close enough, slave the tpod to the waypoint, slew over the target, press TDC Depress to make a new target point, then uncage the Maverick to that new point.

Virpil WarBRD | Thrustmaster Hornet Grip | Foxx Mount | Thrustmaster TWCS Throttle | Logitech G Throttle Quadrant | VKB T-Rudder IV | TrackIR 5

 

 

AMD Ryzen 5 3600 | Nvidia GTX 1060 6GB | 32GB DDR4 3200 | SSD

Posted
dont forget the WP normally defaults to around 6000+ feet, ensure the WP you want to use is at ground level

 

Yesssssss! It just occurred to me that it was the altitude setting, most likely. I will test it when I get home.

Rig: Alienware Aurora R9 - 9th Gen Core i7 9700K 4.6GHz 8 Cores | NVIDIA GeForce RTX 3060 Ti 8GB GDDR6 | 2TB M.2 PCIe NVMe SSD | 64GB Corsair Vengeance RGB PRO SL DDR4 3200MHz XMP 2.0 | LG Series80 QNED 50in 4K 120hz | TM Warthog HOTAS w/F-18 grip | Logitech G Pro RP | 3 TM Cougar MFDs | TrackIR 5 Pro |

Modules: FC3 | F/A-18C | F-16C | A-10C II | F-14 | M-2000C | AV-8B | F-5E | JF-17 | P-51D | KA-50iii | UH-1H | AH-64D | F4U-1D | F-4E | Supercarrier | Combined Arms | Nevada | Persian Gulf | Syria | Normandy | Chanel | South Atlantic | Afghanistan

Posted

Yup, waypoint elevation is the first thing I would check as well.

 

If the waypoint isn't placed at ground level the FLIR will point at an empty location in the air, and will appear to be pointing at the ground somewhere beyond the target location. The error will appear to be greater the further away you are, and it will be off in a different direction relative to your position to the waypoint.

 

Also, since you're using Mavericks, what kind of targets are you attacking? Mobile units do have a tendency to move, and may not stay in the exact place you inserted them in the ME depending on what they are and what their orders are.

Posted

That's what it was, guys! Thanks for the help!

Rig: Alienware Aurora R9 - 9th Gen Core i7 9700K 4.6GHz 8 Cores | NVIDIA GeForce RTX 3060 Ti 8GB GDDR6 | 2TB M.2 PCIe NVMe SSD | 64GB Corsair Vengeance RGB PRO SL DDR4 3200MHz XMP 2.0 | LG Series80 QNED 50in 4K 120hz | TM Warthog HOTAS w/F-18 grip | Logitech G Pro RP | 3 TM Cougar MFDs | TrackIR 5 Pro |

Modules: FC3 | F/A-18C | F-16C | A-10C II | F-14 | M-2000C | AV-8B | F-5E | JF-17 | P-51D | KA-50iii | UH-1H | AH-64D | F4U-1D | F-4E | Supercarrier | Combined Arms | Nevada | Persian Gulf | Syria | Normandy | Chanel | South Atlantic | Afghanistan

  • Recently Browsing   0 members

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