[BUG] Jester map mark to waypoint utility incorrectly translating coordinates

[near_blind]

As of today's open beta, the waypoints created by the jester map mark utility are far off from the actual map mark, with the error growing the further from a maps origin coordinate.

 

 

ED apparently fixed the points returned by the world.getMarkPanels() having the x and z coordinates flipped. I would imagine that is effecting the function that calculates game position to lat/lon coordinates.

Edited August 15, 2019 by IronMike

[IronMike]

As of today's open beta, the waypoints created by the jester map mark utility are far off from the actual map mark, with the error growing the further from a maps origin coordinate.

 

 

ED apparently fixed the points returned by the world.getMarkPanels() having the x and z coordinates flipped. I would imagine that is effecting the function that calculates game position to lat/lon coordinates.

 

 

thank you, we will take a look.

[Blood-n-Guts]

+1

[funkyfranky]

@IronMike, it's this bug ED finally fixed https://forums.eagle.ru/showthread.php?t=213275

You need to swap the x and z components of the vector coordinates you are using.

[leonardo_c]

As of today's open beta, the waypoints created by the jester map mark utility are far off from the actual map mark, with the error growing the further from a maps origin coordinate.

 

 

ED apparently fixed the points returned by the world.getMarkPanels() having the x and z coordinates flipped. I would imagine that is effecting the function that calculates game position to lat/lon coordinates.

 

 

I can confirm that some modules are having problems with map marks (Tomcat) and even with initial INS alignment (Hornet)

For the Hornet you can workaround it with a TCN position update.

For the Tomcat I still coult not fix the problem.

A-10C and Mirage appear to be immune.

 

I'm loading a mission, where I know that BULLS is 97nm and I get a 452nm waypoint.

I also tried using different radio D/L (AWACS or carrier) but my best guess is that the initial position of the INS is completely way off.

The same issue happens if starting from ground and with hot starts.

[sLYFa]

You can still manually enter the coordinates, that works properly

[IronMike]

we're on it guys, thanks