Targeting pod error?

[GumidekCZ]

Hi

Have anybody the same problem as I have? When I lock target with TGP as point and with help of laser make it SPI. After that that I start maneuver plane, and strange thing happens. The SPI point on the TGP screen is than far behind the target. I noticed that this happens only when I manever plane pointing nose above trgt....lock target (make it SPI)...nose of plane pointing before (under) the target and than back to level flight. After every maneuver like this, I have to correct the possition of SPI.

Any help?

Sorry for my English.

[Tholozor]

When the SPI is set to the TGP, it will constantly set to what the TGP is telling it. If you lase a target, set SPI, then turn the laser off, the SPI will still only set to what the TGP sees, which is the ground behind it. Your best bet would be to designate the ground under the target, or make a mark point using the laser.

 

Old video, but great for explaining TGP functionality:

Edited December 19, 2012 by Tholozor

[GumidekCZ]

I tried again few minutes ago with same result. Lock target with TGP and laser ON and make it SPI. Than maneuver plane pointing nose 30 degree around the target and see what happens. The TGP camera rotates willdley some time and than you get new wrong possition of your previosly designated target. It not has to be only behind...could be 50 meter in front of the real target.

[GumidekCZ]

Still no clue about what is the reason for that TGP weird behavior. When testing, I noticed another two issues:

1) When locking target with laser ON from long distance, when come closer, the SPI point is behind the real target (depends on the targeting angle). So it seems to me that from distance the laser measuring is usless or very inaccurate.

2) Lock target again with TGP and make one pass behind some hill or cliff. For me the SPI change the position from target to edge of the cliff at the moment of lost direct contact with real target. WHY the hell the A10C cannot remember the SPI coordinates? This is very annoying!!:mad:

[Suchacz]

Try to ask guys on our web in my sig :thumbup:

[PhoenixBvo]

My guess at the cause is gimbal lock in combination with Tholozor's remark that the SPI will follow your TGP if it is still SOI.

You describe pointing the nose downward after designating the target. Assuming the target is directly at 12 o'clock this will cause the TGP to rapidly rotate to follow the target. You may hit the gimbal rotation speed limit depending on how close the target is to the longitudinal axis of the TGP. Because the TGP tracks the point it is looking at, it will be tracking another point after the maneuver. And because your SPI is still continuously being defined by the TGP's center of view, IT will also shift.

 

This is not a bug, but in fact an accurate simulation of gimballed optics.

[Madone]

Still no clue about what is the reason for that TGP weird behavior. When testing, I noticed another two issues:

1) When locking target with laser ON from long distance, when come closer, the SPI point is behind the real target (depends on the targeting angle). So it seems to me that from distance the laser measuring is usless or very inaccurate.

2) Lock target again with TGP and make one pass behind some hill or cliff. For me the SPI change the position from target to edge of the cliff at the moment of lost direct contact with real target. WHY the hell the A10C cannot remember the SPI coordinates? This is very annoying!!:mad:

 

Yes, that's what will happen in real life mate, deal with that, the TGP lock into the ground/thermal sigs, not coordinates, if you make a high G turn, the TGP can't hold the position, it doesn't have enough power to move that fast, and it's more true if you mask it with the plane, you can also get a "gimb roll" if you hit the limits of the head FOV and have to roll back.

 

If you set your SPI in a valley and then fly behind the hill, the TGP will recalculate the path to the nearest available target, hence the edge of the hill, it doesn't see through the mountains!!

The best solution is to set your SPI on the map, if the TGP lost the visual, you can press China Hat Forward to lead the TGP sensor on the SPI.

 

Well I can be wrong about the lock system, I'm a bit clueless about that. But I can tell you, it's not a bug. Maybe someone else will correct that.

 

Hope it helps

[Megagoth1702]

Here is what I do when I am about to do some hardcore maneuvers and I know I am going to screw up my TGP eventually (mountains n stuff).

 

Make TGP SOI, look at target, make TGP SPI.

Make HUD SOI, then slave sensors to SPI, then I make the HUD/TDC my SPI.

 

The TDC spi remembers coordinates etc. Now I can maneuver like a crazy person, have mountains in my way whatever, all I need to do to get TGP on target again is make TGP SOI and slew it to SPI.

 

This also helps when you know your TGP is about to "gimb roll". Just temporarily "save" your target'S location in your TDC (the thing you can slew in the HUD), boresight TGP, then slew to SPI again and it will be slewed to the TDC location. Then make TGP SPI again and continue doing what you were doing.