[FIXED] Waypoint steering cue / Tadpole bugged ?

[db349]

Hello,

I jumped back in the JF17 recently and I wondered if something changed wrt the waypoint steering cue / tadpole ? If I'm flying exactly on the route segment connecting 2 waypoints in chronological order (eg from 1 -> 2 etc), shouldn't the tadpole be centered on my velocity vector (with the circle inside it) ? On my end it's now totally on the left side of the HUD or on the right side when I follow the flight plan precisely. 

Either I'm missing something or it's a bug. I always remembered it acting as some kind of flight director. 

HNS on, GC aligned, all other systems on. Currently no mods, files verified on Steam.

Cf image attached.

Thanks !

Edited June 26, 2024 by uboats

[Mike_Romeo]

On 6/23/2024 at 12:39 AM, db349 said:

Hello,

I jumped back in the JF17 recently and I wondered if something changed wrt the waypoint steering cue / tadpole ? If I'm flying exactly on the route segment connecting 2 waypoints in chronological order (eg from 1 -> 2 etc), shouldn't the tadpole be centered on my velocity vector (with the circle inside it) ? On my end it's now totally on the left side of the HUD or on the right side when I follow the flight plan precisely. 

Either I'm missing something or it's a bug. I always remembered it acting as some kind of flight director. 

HNS on, GC aligned, all other systems on. Currently no mods, files verified on Steam.

Cf image attached.

Thanks !

Looks like you are using TACAN


 

[tekwoj]

11 hours ago, Mike_Romeo said:

Looks like you are using TACAN


 

This is not tacan, tacan arrow looks like this --o->  But from what you've marked on the screenshot we can see that the plane thinks the next waypoint is north. I think there was a bug on another module recently where there was a mix-up in relative/absolute directions. Here the waypoint is 0 degrees from the plane heading but it gets interpreted as 0 degrees on the compass.

 

Edit: I've tested it a bit and I think I figured out what's going on, the tadpole always shows as if the course line was from north instead from the previous waypoint.

Edited June 24, 2024 by tekwoj

[db349]

Glad to hear it’s not only on my end, so there is definitely something bugged, hope the devs can fix this soon..

I checked it again and the little directional arrows on the HSD that should point to the currently selected waypoint always point to the North in my case, idem for the tadpole. Only in approach mode they line up with the final approach track.

 

[tekwoj]

Right now they will point exactly to the waypoint if you fly to it exactly from the north. They should do that when you're exactly on the course line instead.

[db349]

As a temporary fix, copy pasting my 1st waypoint, to another waypoint after the flight plan through the DST page, then deleting 1st waypoint and finally transferring the coordinates through copy paste from the newly created waypoint after the flight plan to the original place of the 1st waypoint seems to make everything working as intended.

[uboats]

full procedures to reproduce it?

anyone knows when this appeared to happen, rough date?

Edited June 26, 2024 by uboats

[db349]

I just follow normal cold start procedures as indicated in chuck's guide and shown by many youtubers, sometimes using fast alignment other times GC alignment.

The issue also occurs when starting instant action missions, e.g. takeoff and navigation on Syria or Caucasus map, at least on my end, so I guess this would be the best way in trying to reproduce it. As stated, I currently run no mods and have verified integrity of game files through steam.

Timing not really sure, as I have been hopping into different modules recently, but as far as I remember, 2-3 months ago I didn't have this issue with the Jeff.

Thanks for looking into it !

[tekwoj]

I could reproduce it by just making a mission with air start and a few waypoints, just make sure the first waypoint is not directly south from spawn point.

Can't really tell when it appeared as I don't pay attention to it that much

[uboats]

fixed internally. not sure whether it can catch up the upcoming release

[db349]

Great news, thanks !