Jump to content

SPI (Sensor Point of Interest) on HMCS vs TGP not synced


Go to solution Solved by skywalker22,

Recommended Posts

Posted

I know it isn`t that important, also not sure how accurate SPI on RL aircraft is, but in DCS seems to be a bit unaccurate based on TGP (Litening Targeting Pod).

IMPORTANT: this is only when SOI is the HUD (and not the MFD). When MFD is SOI both point on same thing.

Here is an example (pointing on top of the antenna):

View from JHMCS:

image.png

View from TGP:

image.png

---

Test: make MFD SOI. Both MFD and HMCS show the same point of interest. Now make the HUD SOI. Look into MFD and try to move the target designator just a tiny bit, you will see how much it moves on the MFD, for quite a lot. Thats some sort of a bug.

Posted
30 minutes ago, Deano87 said:

Presume the HMCS is calibrated? Also what is the pressure setting of the mission? is it default?

I started the sortie HOT, from runway, didn`t try COLD yet. Will do that now.

What do you think has the pressure got to do with it?

Posted

Setting editor to 15°C 29.923"Hg and from Batumi runway after HMCS calibration (hot runway start isn't perfectly calibrated). Object is an apartment tower north a couple degrees above the horizon. Helmet line of sight is about 45 degrees right of nose.

TGP seems to change to very different logic when above the horizon. There's no terrain backdrop to convert a particular line of sight into a specific three dimensional point. I can't put the helmet cue on this building target directly because it's above the horizon. If you try the TGP will say N45 07.770 E34 15.931 which is the X, Z = 0, 0 point on the terrain. This is over 380 miles away in the wrong direction.

So to get the helmet TD box on a building while on the ground we have to designate on valid terrain and then slew the box post-designate. By slewing the box as shown

image.png

I will look at what SPI position is assume on TGP screen.

image.png

We note the LOS is bad but mostly we care about the L/L/elev. The air conditioner I'm aiming at is at N41 36.818, E41 36.355, 210'. The TGP-listed position is where I first placed the TD box on the ground with the helmet so I could later adjust it to the building top. The elevation seems to be the maximum elevation just as I was slewing above the horizon.

So it's no wonder the TGP's LOS doesn't match the helmet's LOS because it's trying to fix parallax at a range of a hundred feet when the target we care about is 0.6nm away. It's really important to consider the difference between lines of sight and points in space.

OK try 30°C 30.923"Hg for a radically different weather. Same helmet cue placement, looking at TGP cursor result it's not any different. Symbol alignment can be caused by system altitude errors but in this case I don't think it applies.The TGP is about 8 feet below, 3 feet aft, 2 feet right of the pilot. Unless range is correct the LOS, even if perfectly calibrated parallel, won't convert because of this offset.

On the other hand if you TGP SOI and place TGP over a desired point the helmet TD box is not that far off. In my case my TGP shows L/L of N42 40.040 E41 47.767 at 18,707' which is 65nm away but it's in the same LOS as the building.

In conclusion the LOS mismatch is due to the helmet or TGP coming up with different points or lines of sight which make harmonization difficult. I don't know if there's an issue or not. Being on the ground and using the helmet/TGP above the horizon to direct the other sensor is a weird case.

  • Like 1
  • Solution
Posted
18 hours ago, NineLine said:

I am not seeing an issue here as related to being on the ground, is anyone seeing an issue in the air at all? If so let me know and supply a track and I will look into it. Thanks.

You are right, while in the air, all is working fine. Sorry for not testing in each possible circumstances. My bad, will try better next time. So this is NOT a bug after all.

But is a bit odd why is this not working on the ground, just saying.

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

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