[RESOLVED] Jester/F10 Waypoints Broken?

[Kondor77]

I can't get Jester to give me a correct waypoint via the F10 menu. Is this a bug? Attached pictures of what I see. This happens in SP and MP. Starting cold/hot doesn't seem to make a difference. Cold I always go to fine alignment. Anyone else getting this? I have a feeling it's something on my end since I can't find any other posts on this.

 

 

 

Edited August 20, 2019 by IronMike

[Knock-Knock]

Yes

https://forums.eagle.ru/showthread.php?t=247681

[IronMike]

Thank you, this is already fixed internally and will be included in the next patch.

[grant977]

I don’t think this made today’s patch just fired up the jet cold start with stored heading alignment and still exists.

[IronMike]

No, sorry, what I meant was the next regular patch, the hotfix only reflected on our black wing hotfix and the ARAK fix for the Viggen.

[viper2097]

Tested it today with the Viggen on the NTTR map and everything was fine, so was the NTTR not affected?

[grant977]

Cool no worries thank you for the clarification.

[IronMike]

Tested it today with the Viggen on the NTTR map and everything was fine, so was the NTTR not affected?

 

 

Likely, in this case.

[draconus]

But the F-14B still bugged even on NTTR. Just FYI

[leonardo_c]

Tested today the Viggen and it was working perfectly.

The Tomcat appears still broken though. ;)

Entering coordinates manually still works however.

[-IRRE-Rolluptito]

Not solved for me, I still have the problem. (Tested on Persian Gulf, cold-started and with fine alignement)

[viper2097]

Viggen is fixed, Tomcat ist broken.

HB did already fixed it internally, but ED decided to not make an OB update this week. So we'll have to wait for the next OB to fix that issue.

[RSharpe]

Are all waypoints set by Jester broken, not just those designated on the F10 map? I've been trying to enter waypoints in manually through the Jester menu. In every case, Jester will only allow me to enter the first 5 digits. It won't allow me to enter the 6th digit, so instead of N 42 55 19, I would get N 42 55 1. Jester simply stops inputting after the 5th digit, and moves on.

 

I think this is the same problem as the F10 map.

 

Unfortunately, ED chose not to roll out a beta update this week, so I'm not sure if this has been internally addressed.

[near_blind]

Are all waypoints set by Jester broken, not just those designated on the F10 map? I've been trying to enter waypoints in manually through the Jester menu. In every case, Jester will only allow me to enter the first 5 digits. It won't allow me to enter the 6th digit, so instead of N 42 55 19, I would get N 42 55 1. Jester simply stops inputting after the 5th digit, and moves on.

 

I think this is the same problem as the F10 map.

 

Unfortunately, ED chose not to roll out a beta update this week, so I'm not sure if this has been internally addressed.

 

Thats not a jester issue, the Tomcat's INS only stores coordinates to the first seconds digit. Welcome to the 1970s.

[draconus]

Thats not a jester issue, the Tomcat's INS only stores coordinates to the first seconds digit. Welcome to the 1970s.

So for N 42 55 19 I should rather input N 42 55 2, right?

[near_blind]

So for N 42 55 19 I should rather input N 42 55 2, right?

 

That's best practice, but if we're being real honest the difference between 42 55 1 and 42 55 2 is ~1000 feet. I can't imagine doing anything in the Tomcat reliant upon the INS alone where that sort of error really matters.

[draconus]

That's best practice, but if we're being real honest the difference between 42 55 1 and 42 55 2 is ~1000 feet. I can't imagine doing anything in the Tomcat reliant upon the INS alone where that sort of error really matters.

I could think of this http://www.heatblur.se/F-14Manual/weapons.html#computer-initial-point