Mission Editor Bearing Bug Fix

[Case]

The Problem

The ruler tool in the Flaming Cliffs 2.0 and Black Shark mission editors returns the wrong bearings. Due to the difference between the map in the editor, which is spherical, and the map in the game, which is flat, the bearing measured in the editor can be off by as much as 4 to 7 degrees. This will makes lining up units with features on the map very tedious.

 

 

The Solution

Replace BlackShark\modules\me_map_window.lua for LockOn Flaming Cliffs 2.0 and/or DCS:Black Shark with the file in the attachment below.

 

The attachment changes the code in BlackShark\modules\me_map_window.lua from

--local x1,z1 = Roads.xz(tape.points[1][1].x, tape.points[1][1].y)
--local x2,z2 = Roads.xz(tape.points[1][2].x, tape.points[1][2].y)
--local dist = base.math.floor(base.math.sqrt((x1-x2)*(x1-x2)+(z1-z2)*(z1-z2))+0.5)
local lat1 = tape.points[1][1].x
local long1 = tape.points[1][1].y
local lat2 = tape.points[1][2].x
local long2 = tape.points[1][2].y
local dist = base.math.floor(db.getDist(lat1, long1, lat2, long2))
--local ang = base.math.mod(base.math.floor(360+90-base.math.atan2(lat2-lat1, long2-long1)*180/base.math.pi), 360)
local cos = base.math.cos;
local sin = base.math.sin;
local atan2 = base.math.atan2;
local pi  = base.math.pi;
       
local dl = long2 - long1;
ang = atan2(sin(dl)*cos(lat2), cos(lat1)*sin(lat2) - sin(lat1)*cos(lat2)*cos(dl));		

to

local x1,z1 = Roads.xz(tape.points[1][1].x, tape.points[1][1].y)
local x2,z2 = Roads.xz(tape.points[1][2].x, tape.points[1][2].y)
local dist = base.math.floor(base.math.sqrt((x1-x2)*(x1-x2)+(z1-z2)*(z1-z2))+0.5)
--local lat1 = tape.points[1][1].x
--local long1 = tape.points[1][1].y
--local lat2 = tape.points[1][2].x
--local long2 = tape.points[1][2].y
--local dist = base.math.floor(db.getDist(lat1, long1, lat2, long2))
--local ang = base.math.mod(base.math.floor(360+90-base.math.atan2(lat2-lat1, long2-long1)*180/base.math.pi), 360)
--local cos = base.math.cos;
--local sin = base.math.sin;
local atan2 = base.math.atan2;
local pi  = base.math.pi;
       
--local dl = long2 - long1;
--ang = atan2(sin(dl)*cos(lat2), cos(lat1)*sin(lat2) - sin(lat1)*cos(lat2)*cos(dl));		
ang = atan2(z2-z1,x2-x1)

 

Essentially, the bug was that the bearing was calculated for the spherical mission editor map, not on the flat game map.

me_map_window.rar

[crazyeddie]

If this works I will personally offer to bear your babies ... this problem has pi**ed me off for ages.

 

Will give you feedback tomorrow, when I'm sober ...

[Panzertard]

Much appreciated, such a small issue can be really annoying. Thanks for the fix, bud :)

[Grimes]

Win.

[104th_Crunch]

Thanks once again for sharing your work Case!

[LawnDart]

+1

 

That's great! Any idea if there's a fix for the LAT/LONG coordinates as well?

[Kuky]

Great!

[Moa]

+1

 

That's great! Any idea if there's a fix for the LAT/LONG coordinates as well?

 

The mapping from Lat/Long to in-game x,y is complicated. This is because an Gnomonic projection is used to project the spherical surface onto a flat plane. The formulae for the projection (and its inverse) can be found in the following thread:

 

http://forums.eagle.ru/showthread.php?t=44427

 

For the working Java code I wrote for LEAVU2 (including a bugfix by Yoda) see the MapProjection class in the LEAVU2 source code at:

 

http://kenai.com/projects/leavu2/sources/subversion/content/LeavuGeneralClasses/src/nav/MapProjection.java

[STP Dragon]

Thx for that! :)

[crazyeddie]

Brilliant mate - now about the babies ... I was pi**ed when I said it and I have this no womb problem ... can we negotiate.

[Case]

Brilliant mate - now about the babies ... I was pi**ed when I said it and I have this no womb problem ... can we negotiate.

At the moment I have no need for babies, so it's your lucky day :D

[Vecko]

Ah finaly ,blocks on road again...:D

TY Case,S!

 

P.S.And here is madman pack for lazy peoples...

Mission Editor Bearing Bug Fix.rar

Edited June 14, 2010 by Vecko

[X-man]

Good stuff Case! :thumbup:

[Case]

P.S.And here is modman pack for lazy peoples...

Thanks Vecko!

[coolts]

Brilliant mate - now about the babies ... I was pi**ed when I said it and I have this no womb problem ... can we negotiate.

 

At the moment I have no need for babies' date=' so it's your lucky day :D[/quote']

 

Dont let the whole no-womb thing be a problem guys. Arnie got round that one ! :megalol:

 

[Vecko]

I don't know do you all guys realise but this bug is driving crazy mission designers since DCS come out.this is realy good peace of work and it should be uploaded on lockon files.

[christopher m]

I wonder if we can merge this mod with "Mission Editor Mod" by Blindspot

 

 

http://forums.eagle.ru/showthread.php?t=55186&highlight=editor

 

 

 

Regards,

Edited June 20, 2010 by christopher m
ad url

[Shaman]

Is this already part of Blindspot'sME from version 1.6?

If it is not, if I install this modman file on top of Blindspot'sME will I break something? Since Blindspot'sME comes with own me_map_window.lua.

Do you have any information how the mission plays when copied to computers without the mod? Any misalignment then? Or over multiplayer?

[Case]

This fix does not affect multiplayer and missions made with a ME using the fix will play perfectly on machines with the ME without the fix.

[Blindspot]

It's not part of 1.6 but will be in 1.7. I promise :)

[combatace]

Well there is a problem in this mod I think. I have to set point target little south to hit the it.

[Vecko]

Well there is a problem in this mod I think. I have to set point target little south to hit the it.

 

This mod just fixing bearing , correct positioning of units and target spots are still broken...

[combatace]

This mod just fixing bearing , correct positioning of units and target spots are still broken...

 

Oh! so its not due to this mod.

[Vecko]

Oh! so its not due to this mod.

 

Correct !

[Gaanalma]

Unfortunately I have to reopen this old topic of FC2 for a problem that I'm experiencing between editor and cdu entries in the A-10C ...

 

If you try to measure the distance and the bearing of the editor to reach a target starting from the bullseye when I insert data in the CDU by Oset of my A-10C, they lead me off course ... I get the impression that the problem detected in FC2 is also transferred to the DCS World ... Can someone test how to mè exposed and see if it is my problem or the simulator?

 

thanks