I think it might be a bug.

[F.T]

This is when the apfsds is used, the range is measured with the laser rangefinder in the gunner's position, and reasonable values are obtained in both modes (first and last).
 

[F.T]

We can still get a reasonable value with the laser rangefinder in the commander's position when using HESH.

[F.T]

However, the laser rangefinder went wrong in the gunner's position when the HESH was used. 

[Jartsev]

Here we go again. Please try to understand, what you are using and what is going on.

You have a gun-mounted thermal camera, and spin-stabilized projectile loaded.  Let's assume, that you didn't lased any target before and hence default battlesight range is indexed, lead is cancelled. What does it mean? In line (Elevation) TOGS reticle is more or less aligned  with  GPS LOS. But  is it aligned in  deflection(Azimuth)? No! Should it? Not quite so, because in fact it shows a predicted point of impact, and there is a drift compensation applied.

 

What is a practical implication? You can still lase a fully-exposed tank-sized target at normal combat range(e.g. up to ~2km), and to have decently accurate result, while at longer ranges it is not possible to expect highly accurate results.

 

Now what you are trying to do and what you are observing. You probably already have some 2+km range pre-indexed because of previous engagement, and you are lasing something. What is going on? Bluntly speaking, even after dumping lead you are going to measure a temperature on the  far side of the moon, because TOGS reticle still has drift compensation applied, and obviously is grossly not aligned with GPS LOS in deflection(and that is normal). So range obtained is going to be expectedly wrong.

 

Now question, how to reduce that error? 

- Use  GPS for long range engagements, if in Challenger 2

- If target is not observable  through GPS, HESH is  loaded, and you are using TOGS, before lasing try to minimize possible errors:

1) Index battlesight range (Backspace hotkey)

2) Dump lead

 

[F.T]

9 hours ago, Jartsev said:

Here we go again. Please try to understand, what you are using and what is going on.

You have a gun-mounted thermal camera, and spin-stabilized projectile loaded.  Let's assume, that you didn't lased any target before and hence default battlesight range is indexed, lead is cancelled. What does it mean? In line (Elevation) TOGS reticle is more or less aligned  with  GPS LOS. But  is it aligned in  deflection(Azimuth)? No! Should it? Not quite so, because in fact it shows a predicted point of impact, and there is a drift compensation applied.

 

What is a practical implication? You can still lase a fully-exposed tank-sized target at normal combat range(e.g. up to ~2km), and to have decently accurate result, while at longer ranges it is not possible to expect highly accurate results.

 

Now what you are trying to do and what you are observing. You probably already have some 2+km range pre-indexed because of previous engagement, and you are lasing something. What is going on? Bluntly speaking, even after dumping lead you are going to measure a temperature on the  far side of the moon, because TOGS reticle still has drift compensation applied, and obviously is grossly not aligned with GPS LOS in deflection(and that is normal). So range obtained is going to be expectedly wrong.

 

Now question, how to reduce that error? 

- Use  GPS for long range engagements, if in Challenger 2

- If target is not observable  through GPS, HESH is  loaded, and you are using TOGS, before lasing try to minimize possible errors:

1) Index battlesight range (Backspace hotkey)

2) Dump lead

 

I actually indexed battlesight distance(400m for the HESH) and dumped the lead before using the laser rangefinder. I do this all the time before I use the rangefinder again.

[Mirzayev]

Messed around with the Challenger 2 with HESH.

 

It works as intended when using first and last return. 

 

Not a bug.