cannot repoduce and missing track file F-16 Trouble with waypoints

[Adamg1987]

Having some issue navigating to custom waypoints on multiplayer.

I get my Long and Lat from the f10 map I cycle the co-ordinates so that they are in the same format that the f16 needs for example;

Sam Site N43 41.479 E39 51.967 I enter them as they are adding a 0 before the 39 for east yet I'm miles off. 

I'm using Steer point 1 in Manual mode if that makes a difference.

Edited July 27, 2022 by Adamg1987

[razo+r]

Got a track, video or picture showing you putting the coordinates into the aircraft?

[Adamg1987]

Yes this is what I Input

Edited July 27, 2022 by Adamg1987

[Tom Kazansky]

OP says "N42..."

Screenshot says "N43..."

[Adamg1987]

Just now, Tom Kazansky said:

OP says "N42..."

Screenshot says "N43..."

That was a Typo it was deffinately N43

null

[Tom Kazansky]

When you make an overtly markpoint, is that the same as your F10-map position?

[Adamg1987]

Just now, Tom Kazansky said:

When you make an overtly markpoint, is that the same as your F10-map position?

Sorry not sure what you mean?

[Tom Kazansky]

To check whether your nav system works accurately or you have the right format at F10 map, you can compare your coordinates of the F10 map with your position. Either on the ground before take off or inflight with a markpoint at a known position e.g. like an airfield that you fly over.

[Adamg1987]

4 minutes ago, Tom Kazansky said:

To check whether your nav system works accurately or you have the right format at F10 map, you can compare your coordinates of the F10 map with your position. Either on the ground before take off or inflight with a markpoint at a known position e.g. like an airfield that you fly over.

I did not do that no, I did adjust the co-ordinates on the F10 map using Left Alt + Y to get them into the right format for the F16. 

I would of assumed that the Nav system would be working and alignments done. It was a hot start on a multiplayer server.

Edited July 27, 2022 by Adamg1987

[Tom Kazansky]

I just saw your photograph of the F10 map position. You have definitely the right format so maybe your INS alignment wasn't good. You can check that like I posted above.

[Tom Kazansky]

Without a track I have just one guess left: after the input of a steerpoint you have to increment the waypoint number at least once and switch back to the waypoint to get it into the Viper's nav system.

[Adamg1987]

24 minutes ago, Tom Kazansky said:

Without a track I have just one guess left: after the input of a steerpoint you have to increment the waypoint number at least once and switch back to the waypoint to get it into the Viper's nav system.

Hi, yeah I always cycle could see the targeting pod moving around cycling back between Waypoint 1&2. 

My DCS client wasn't running the most up-to-date version so I'm going to give it another go later. 

Appreciate the help. 

[Tom Kazansky]

Hope you get this sorted out.

[Frederf]

You can look at your LIST-6 INS DED page to see where your INS thinks it is. Make sure to CZ any slews as well. This can be a little insidious as there's no obvious indication slews are non-zero.

[AngryViper.101]

From personal experience.

I think the problem is that your system was not properly aligned (either use stored alignment, or normal alignment) prior to takeoff.

[skywalker22]

1 hour ago, warford said:

From personal experience.

I think the problem is that your system was not properly aligned (either use stored alignment, or normal alignment) prior to takeoff.

Yep, I have never experianced something like it with F-16 in last 2 years since I fly this bird.

[AngryViper.101]

3 hours ago, skywalker22 said:

Yep, I have never experianced something like it with F-16 in last 2 years since I fly this bird.

Hi, I do experience it often due to my own 'user' 101 error.

Either I do not wait for stored alignment to do its thing, or I forget, and then the systems are not aligned correctly resulting in what this post mentions.

That is why pilots shave checklists I should keep one handy.

Edited July 28, 2022 by warford

[SickSidewinder9]

I am noticing that waypoints on the ground report wrong distances.  This is since the last 2 beta updates (today's and the one the other day).  Really messes with landing procedures.  The position on the HSD/HAD/HUD will be right, but the distance measurement is way off.  Screenshots attached.  It is also off on the HSI down there below the frame.

 

nullas you can see, the distance shown on the HUD is around 4x the actual distance on the F10 map.  It's usually less when it happens.  This latest example is the most extreme.  Waypoints up in the air don't appear to have this problem.
This particular waypoint was from a HUD mark.  It WAS accurate.  Had the SPI right on the rubber marks at the end of the runway.  Switch back to it later and it distance is FUBAR'd.  It also is an issue with preset waypoints from the mission design.  This is in Singleplayer.  Changing waypoints back and forth does not fix it.
Anyone else getting this?  Still flying the mission, so I guess I can include a (very long) track file.null

Edited July 28, 2022 by SickSidewinder9
more specific

[SickSidewinder9]

Here is another 1 after mission restart where I put in 2 destinations as steerpoint 1 and 2, and you can clearly see a difference in miles between the HUD and the HSD.  Not sure when it happened, but I'm still taxiing, so fairly quickly off.  It says 3 Miles on the HUD, but on the HSD, you can see it's about 30 to 35 miles.  That's off by 10x!

I

Edited July 28, 2022 by SickSidewinder9

[Frederf]

The top picture is odd since the tadpole is showing the INS destination is to the right while the steerpoint diamond symbol is to the left of the FPM. Can you make a track showing this behavior?

[Adamg1987]

I updated my client to latest beta, was previously stable. Did everything the same and it worked fine. 
 

planes are prealigned on the server I used as planes are all hot start. So not sure what I did wrong. Is it possible to mess up an alignment after it is done ? 

[GibsonPlayer]

This is an older thread, but I'm having issues with the setting WPs in the 16. Using both Decimal and MGRS, my points are way off. It was like this for the last patch. Previous to that I had no issues. I could set all kinds of different WPs and it just worked right. Does it make a difference if the Tpod is on?

Edited May 28, 2024 by GibsonPlayer

[razo+r]

11 hours ago, GibsonPlayer said:

This is an older thread, but I'm having issues with the setting WPs in the 16. Using both Decimal and MGRS, my points are way off. It was like this for the last patch. Previous to that I had no issues. I could set all kinds of different WPs and it just worked right. Does it make a difference if the Tpod is on?

 

No, TGP has no influence over a steerpoint coordinates. 

Can you attach a short track demonstrating your issue? 

[Furiz]

12 hours ago, GibsonPlayer said:

This is an older thread, but I'm having issues with the setting WPs in the 16. Using both Decimal and MGRS, my points are way off. It was like this for the last patch. Previous to that I had no issues. I could set all kinds of different WPs and it just worked right. Does it make a difference if the Tpod is on?

 

Usual culprit is the elevation but as above poster said post a short track showing the issue so we can see what is going on.

[Aquorys]

If where the HUD is pointing you is not where the steerpoint is, press CZ (cursor zero) on the TGP page