reported NAV-Fix with TGP

[Moonshine]

taking a NAV-Fix with the TGP seems to not be putting the "updated" steerpoint location where i designated it using the same procedure as explained by wags here; <https://www.youtube.com/watch?v=RBHrEzLGSqw

and here: 

https://forum.dcs.world/topic/209147-viper-mini-updates/?do=findComment&comment=4992813

OFLY works fine, HUD works fine and FCR works but is a pain as it constantly resets the crosshair during sweeps, having to start over

Track attached, mission date 1980 to ensure GPS isnt available

 

NAV-FIX_with_TGP_broken.trk

[Volator]

1 hour ago, Moonshine said:

mission date 1980 to ensure GPS isnt available

I'm not certain and by no means an expert, I am only currently learning to operate the F-16, but I think the missing GPS is part of the problem. I tried to simulate non-GPS Cold War flying by disabling GPS via year and taking NAV fixes via the TGP (yes, I know this anachronistic too), and it showed that it was not possible to take precise NAV fixes that way. While the DED indication always showed 0.0 deviation from the waypoint, the TGP would always point off the intended STP when pressing CZ, and it seemed that the deviation was getting bigger and bigger with every fix taken. Interestingly enough, the deviation got so big that while I was lasing a target, the aming cue in CCRP was totally off and the LGBs were dropped so far off the target they could not aquire the laser any more. Now WITH GPS everything worked just fine, but then I did not have to take any fixes as the navigation precision was always very high and spot-on.

 

I'm not sure whether the whole thing is a bug or whether the TGP itself needs GPS to place steerpoints correctly and CZ, but it's clear without GPS the whole TGP fix-taking doesn't work.

[Lord Vader]

I am investigating this behaviour. Thanks for the track, @Moonshine.

[Moonshine]

Yeah its funny, after the first fix you take, moving the tgp with the fix page open actally shows a decreasing offset the closer you get to your very initial steerpoint location. In my case it was the tower on the airfield. Deviation showed 0 the closer i got to that tower, even though the steerpoint diamond was at one end of the runway

[Volator]

4 hours ago, Moonshine said:

FCR works but is a pain as it constantly resets the crosshair during sweeps

OT, but: Is that realistic btw? I would assume if there's a freeze function on the radar, putting the cross on the right spot during sweeps must be possible too?!

Edited September 19, 2023 by Volator

[Moonshine]

There is a freeze option one could (and in this case should) use yes. No idea if the recentering of the crosshair is realistic on every sweep. 

[Lord Vader]

Hi @Moonshine

We believe we have fixed this internally, please wait for future updates and try again.

[Flappie]

@Moonshine Was this issue fixed for you?

[Moonshine]

 

7 hours ago, Flappie said:

@Moonshine Was this issue fixed for you?

Did not test it yet

edit:

tested just now, seems to be better but still not really good. after designating the "new" location with the pod, pressing Enter will update the system. however the final location of the updated steerpoint seems to shift or hang in the air compared to what was just designated with the pod.

for examples:

in my test i first want the steerpoint to be at the start of the runway on the white lines. somehow the final location is off by a couple 10m

then i try it again with a parking hangar and later on with the ATC building, still the same.

 

for general navigation given no GPS years this is surely "good enough" but to correct coordinates for bombing something this surely isnt unless the target can be visually picked up before employment. not saying this isnt realistic, its just the observation of whats happening now with it.

bottom line, the "updated" steerpoint location doesnt end up to be in the center of the TGP crosshair as it was originally designated. or the elevation doesnt match. then again, in the DED the elevation seemed correct.

NAV-Fix-TGP.trk

 

Edit 2:

seems something with the elevation is off. after designating, it adds 200 feet somehow. you can see it in the TGP page, top left the elevation number

NAV-Fix-TGP_2.trk

Edited November 17, 2023 by Moonshine

[Moonshine]

@Lord Vader was the fix already implemented? or is what im seeing still the "old issue"?

[Lord Vader]

Hi @Moonshine

I will bring this again to the team, thanks for your cooperation.

[Lord Vader]

Hello again, @Moonshine

We've analysed this new item you presented and we confirm the adding of an altitude error to the new FIX performed.

However, you are only performing the FIX itself and you also need to perform an altitude correction, remember these are tridimensional points. You can do that with the ACAL functionality.

Hope that helps, this appears fixed at this time.