fixed What am I doing wrong to hit a moving target with a GBU-12 ?

[JTFF-Marco]

Well title explains it all, here is a small video of me not understanding why I can't get my TD Box to follow a mooving tank in order to drop a GBU-12 on it. I must be doing something wrong or something changed because I did it a lot of them in the past. Any help appreciated. Thanks ! 

Last OB update from the 18/11/2021

 

Edited November 20, 2021 by JTFF-Marco

[fagulha]

Laser off?

[JTFF-Marco]

no, no laser problems, the drop cues will make me drop to far away anyway for the bomb to track and correct. 

[Fakum]

Well,, i know you didnt actually release a bomb in the video, so I am assuming when you do, the LASER is actually turned on, and additionally, did you set the laser code to 1688 in the IFC?

 

Maybe you should post a video of your actual attempt?

 

 

Edited November 20, 2021 by Fakum

[Ignition]

He said it was a problem with the SPI not updating on a moving target. Nice finding.

Did you try using the laser to see if it updates the SPI instead of slewing the TGP?

[JTFF-Marco]

Indeed my issue is more SPI related I guess the title of the topic could be wrong sorry. 

Quote

Did you try using the laser to see if it updates the SPI instead of slewing the TGP?

 

I did not I will try to see if it does. 

So for clarification, here is my question/issue : 

Let's say I am at FL200, I get a GMT return, GMTT, use TMS right to get the TGP on that location and see a moving convoy of Tanks. 

--> TGP SOI, and at 15nm from the convoy I go TMS Forward, setting the TGP as SPI and entering a Point Track on the lead Tank. Well while i keep following the Tank on point track the SPI is actually on the ground location where was that Tank when I entered Point track. And my CCRP release cues are pointing me to that location for the drop. So when 45-50 seconds later I get a release cue the convoy is 45-50 seconds away from that location and depending on his speed it might be out of reach of the LGB, or the LGB might never catch the laser as it's lasing to far away from the reference point used to calculate release point/time. 

[TheBigTatanka]

It indeed looks like a bug. SPI is not following the point track with TGP as SOI. Nice find.

Sent from my Pixel 3 XL using Tapatalk

[Carbon715]

same for the TGP/Mav not following the FCR GMT SPI, just slaves to the point of designation...However I don't know if that is a thing or not.

[Mike5560]

I think there's possibly a legitimate issue here. One is potentially a bug, that the (HUD) target designator doesn't follow the targeting pod generated SPI. I don't know if that's accurate as-is for the F-16 though. I will say that attacking a moving target from the front with GBU-12s is a bit of a gamble.  Often times from the front, the seeker will never acquire the laser with its narrow FOV.  AFAIK, the ballistic solution isn't based on a moving target, it only calculates a solution based on a stationary target.  If attacking from the front makes the most sense for other tactical reasons, it might be best to drag the TGP well in front of the target before release, drop, then reacquire the target, then lase.  

I just now tested hitting a BTR-80 going 45 kts on a straight road (from rear aspect) with no TGP trickery, just keeping on the target in point track. It appears to be updating the SPI position through the TGP.

Edited November 21, 2021 by Mike5560

[FoxOne007]

Looks indeed like SPI is somewhat broken, maybe @BIGNEWY or @NineLinecan confirm

[BIGNEWY]

I will take a look. 

Please in the future attach a short track replay showing the problem. 

Thanks

[BIGNEWY]

I have reported if for checking.

thanks