reported earlier HMD target designation shifts - Slant range related

[Swift.]

https://forums.eagle.ru/forum/english/digital-combat-simulator/dcs-f-a-18c-hornet/bugs-aa/7143660-reported-tgt-designation-drifts-when-jhmcs-on Reported already

[Bullitthead]

Hello, I've seen this bug reported earlier but I think I may have found some more information. I've noticed that the HMD target designation cursor moves if the navigation waypoint elevations are not set to near ground level. The HMD designation function appears to work normally if the navigation waypoint elevations are set to near 0 using the HSI DATA waypoint function.

HornetHMDbug1.trk

[Bullitthead]

I've found that if I set the navigation waypoint altitudes to near 0 ft/meters using the HSI DATA page then the HMD designated target will not shift/move. Not sure why the HMD is tied to the nav waypoint altitudes but give it a try.

[BIGNEWY]

Thanks we do have this reported, likely related to slant range.

 

thank you

[RoGaR]

Hi,

I would like to report a possible bug about TGP and the HMD miscommunication when I try to designate target.

What I try to do: I would like to pick roughly the area of interest via HMD. Then I try to find my target and designate it via TGP.

The basic setup:

GBU—12 (auto mode, instant fuse), TGP Pod – On and displayed in the MFD, A/G-on, Master Arm – on, HMD on.

Normal work:

1)      SCS (Sensor control switch) – FWR

2)      Pick a close target via the HMD (less than 5 miles) – TDC Depress. The diamond appears in the HMD. The targeting pod should also look to this point and the diamond should be visible in the TGP’s MFD. Coordinates in the MFD are still !!!

3)      Press the SCS (Sensor control switch) towards to the TGP’s MFD (SCS to Right in my case)

4)      Slew the TDC in some direction. The diamond should change to the cross and you can pick up your new target via the TGP by TDC depress.

5)      Press the TDC Depress in the new coordinates (The cross change to a diamond). The new position of the diamond should be visible in the TGP’s MFD. Coordinates in the MFD are still !!!

This was how I expect it should work (and it works so far) but here comes the buggy part (at least for me)….repeat the previous procedure like this:

1)      SCS (Sensor control switch) – FWR

2)      Pick a far target via the HMD (10-15 miles) – TDC Depress. The diamond appears in the HMD. The targeting pod should also look to this point and the diamond should be visible in the TGP’s MFD. Coordinates in the MFD are still !!!

3)      Press SCS (Sensor control switch) towards to the TGP’s MFD (SCS to Right in my case)

4)      Slew the TDC in some direction. The diamond should change to the cross and you can pick up your new target via the TGP by TDC depress.

5)      Press the TDC Depress in the new coordinates (The cross change to a diamond).. The new position of diamond should be visible in the TGP’s MFD and it is visible ….. BUT THE COORDINATES ARE CHANGING AND THE DIAMOND TRAVELS!!!

I tried to undesignate, re-designate via markpoints or waypoints, offset the designation etc. No matter what I do, the diamond travels. If you try to fix it…the entire procedure degrades even more and in one point after (10-15) designation you will not even be able to switch between the diamond and the cross (Step 4 is not working)

TGP_HMD_BUG_SHORT.trk

[Sharkku]

Yes, I have observed this behaviour also. I would definitely consider this a bug.

[BIGNEWY]

I believe we have this reported already here 

Most likely an issue with slant range

 

Thanks

 

threads merged

[John1606687966]

Same issue here. It's really annoying 

[Joni]

Will this be fixed for today's update? I have some missions that require this feature to be working correctly and was really looking forward to see this fixed.

 

 

Thanks.

[John1606687966]

Nope, this wasn't fixed in today's update 

[Joni]

2 minutes ago, John1606687966 said:

Nope, this wasn't fixed in today's update 

 

Update is not live yet, just got into steam seconds ago. How would you know?

Edited December 17, 2020 by Joni

[John1606687966]

Mine updated 10 mins ago.

[Amarok_73]

Is it the issue as on this screenshot?

[Swift.]

11 hours ago, Pipok said:

Is it the issue as on this screenshot?

There isn't anything explicitly wrong in this screenshot. PTRK means the pod isn't necessarily tied to the TGT. And the behaviour between the HUD, the MAVF and the TGT look correct.

[Tenkom]

I feel there is something wrong with HMD A-G target designation.

I have attached a track.

What I did:

With no target designated I set the FLIR as SOI. I slave the TGP to the Velocity vector. I point the VV in the rough area and press TDC depress, I then use the tgp to slew to a hangar and press TDC depress(not sure if this is a necessary step but whatever). I then fly around a little. The coordinates displayed in the TGP are rock solid and never change. When I come around 360 degrees the tgp is still pointed exactly where I left it.

 

Next Step:

I undesignate the target. Put my HMD as SOI. Look in the general area of the hangar. Hit TDC Depress. Switch SOI to tgp. Hit TDC Depress. Slew over to the hangar again with the TGP. Hit TDC Depress again just to be sure. Then I fly around a little. Now I can see the coordinates drift, especially the altitude goes out of whack. After I come around 360 degrees the tgp is no longer pointing at the place I left it.

 

Is this correct behaviour? It seems to me that although I used the HMD to point the TGP in the rough direction, after that it was the TGP that took over and did the final designation. Why would the HMD interfere after this point?

This is a big problem because when I use the HMD to find targets most of my JDAMS miss even when I use the TGP for fine tuning.

hmcs drift.trk

[Dark Cloud]

Yeah it’s a bug. Super annoying - happens when you designate a point further than 10 miles using HMD. Apparently some problem with slant range calculation. Once you’ve designated with HMD even switching to TGP doesn’t fix. Has been reported a while ago but no solution yet. 
Was really hoping it would be sorted last patch but no joy.

Edited December 24, 2020 by Dark Cloud

[moggel]

Another hiatus and now trying to catch up with the updated HMDC. I go HUD/HMD as SOI, then look at a point and designate it. What happens is the diamond appears but is moving along the ground. Is that supposed to happen? I need to constantly slew/re-designate but overall this approach is pretty useless ATM. Bug or have I missed something?

Edited December 26, 2020 by moggel

[QuiGon]

No LANTIRN on the Hornet, only on the Tomcat.

[Harker]

42 minutes ago, moggel said:

What happens is the slewable diamond appears but is not fixed. Instead it slowly moves along the ground so I need to keep slewing/re-designate. Is this a bug or have I missed something?

It's a reported bug. For now, try to use it for close distances only, I find it helps.