need track replay Wrong target position on HUD

[Black6]

The position of target indicated on HUD is not corresponding with its true position. Target is marked by external laser designator (FAC) and picked up by LST (ATFLIR). Am I doing something wrong?

 

?

[razo+r]

Did you designate that laser spot as the new target?

Edited January 27, 2024 by razo+r

[Black6]

1 hour ago, razo+r said:

Did you designate that laser spot as the new target?

 

Yes I did. Picture of a new try. I this case I was unable to switch field of view of FLIR. It happens randomly to me. If I push closer view it jumps back to wide field.

[rob10]

You really need to post a track of this happening.  Pictures don't tell the whole story.

[Czar66]

Instant Action - Persian Gulf - Ready on the Ramp -> ATFLIR with custom loadout armed while aircraft is hot. Not that it matters being spawned hot. I did several sorties with the Hornet by starting up cold and still was accurate, not 100% but nowhere near the discrepancy shown on OP screenshots.

Nav to IFA.
A-G Gun.

HUD is accurate to Atflir position.

Can you test on similar instant action default mission?

Edited January 27, 2024 by Czar66
Better wording.

[Black6]

Something similar - POD is locked on the target - slaved Maverick too. The mark from Maverick is on the target, mark from POD is on wrong position.
Could it be associated with the lenght of flight? Target is 400-500nm from carrier location. I tryed both modes - NAV and IFA, no efect ...

[razo+r]

1 hour ago, Black6 said:

Something similar - POD is locked on the target - slaved Maverick too. The mark from Maverick is on the target, mark from POD is on wrong position.
Could it be associated with the lenght of flight? Target is 400-500nm from carrier location. I tryed both modes - NAV and IFA, no efect ...

Get us a track. 

[Black6]

46 minutes ago, razo+r said:

Get us a track. 

 

 

 

 

similar situation, the difference is here not so significant, but it is there - on the end of track

HUD.trk

[razo+r]

8 minutes ago, Black6 said:

 

 

 

 

similar situation, the difference is here not so significant, but it is there - on the end of track

HUD.trk 1.93 MB · 1 download

I see the mission is set to pre-GPS, hence why you didn't see a difference between the INS knob in NAV or IFA. The F-18 is also known to have way overdone INS drift in DCS.

Any chance you can retry it but in a mission where GPS is available? I highly suspect it's this INS drift bug playing a role here.

Edited January 28, 2024 by razo+r

[Black6]

3 hours ago, razo+r said:

I see the mission is set to pre-GPS, hence why you didn't see a difference between the INS knob in NAV or IFA. The F-18 is also known to have way overdone INS drift in DCS.

Any chance you can retry it but in a mission where GPS is available? I highly suspect it's this INS drift bug playing a role here.

 

I changed the date to 2000 and flew again. It helped, tha marks were identical. But that prove, that there is a bug. I suppose that the indication should be based on pointing angles of the sensor, as like with Maverics ...
By the way, do You know since what year is GPS available in DCS? I think it should be some early 90ths ...

[Czar66]

This doesn't make sense.

If INS drifts, wouldn't it be just the coordinates and steer point positioning error vs real world position?

If the TPOD locks onto something on the ground, the HUD should point at the right place as well regardless of INS drift because both (HUD/Aircraft & TPOD) are operating within the same INS.

Am I missing something here? If this behavior happens every time there is no GPS due to mission date, isn't this a bug?

[Ramsay]

21 minutes ago, Black6 said:

... what year is GPS available in DCS?

The "general" date for GPS to function in DCS i.e. F/A-18C, JDAMs, etc. is March 24th 1994, IIRC the "official" date when the constellation of GPS satellites was completed.

An exception to this the F-15E which didn't receive it's EGI until 1998.

Edited January 28, 2024 by Ramsay

[razo+r]

4 minutes ago, Czar66 said:

This doesn't make sense.

If INS drifts, wouldn't it be just the coordinates and steer point positioning error vs real world position?

If the TPOD locks onto something on the ground, the HUD should point at the right place as well regardless of INS drift because both (HUD/Aircraft & TPOD) are operating within the same INS.

Am I missing something here? If this behavior happens every time there is no GPS due to mission date, isn't this a bug?

The INS in the Hornet for some reason also affects the CCIP cues for example, so my guess would be that the whole thing is bugged in a much more deeper way.