Lat/Lon within Apollo Navigation Landmarks.mkr should be updated about nassp

[indy91]

It's interesting. The coordinates we have been using are from the flight plan, so theoretically they should be good. We don't have the full Apollo 8 Lunar Landmark Maps document available but I found one page and the coordinates differ from the flight plan:

Flight Plan:

Landmark Maps:

So our values should definitely be changed. Maybe not necessarily to the ones that got used on the actual mission, as the exact coordinates were more of a suggestion than exact. But we should definitely use the coordinates that Jim Lovell intended to use before the mission. I'll do some more research!

[Aeasala]

I might be mistaken about the last note.
Either way, example of current selected values:
-162.700 -5.250 : CP1 504 (Apollo 8)
+155.100 -10.200 : CP2 526 (Apollo 8)
+95.9 -9.1 : CP3 334 (Apollo 8)

From Table V:
-158.0462 -6.3079 : CP1 504 (Apollo 8)
+163.2463 -9.7036 : CP2 526 (Apollo 8)
+96.8915 -8.8990 : CP3 334 (Apollo 8)

[indy91]

I will go through the coordinates some time and make necessary corrections. Thanks!

[Aeasala]

Yeah, not sure about how it should go forward, but the document I listed does provide all of the landmark coordinates to a T, geographically. At least when comparing the visual references provided in the document for each landmark, there's pretty much zero error.

I'm assuming this .mkr file is only for visual aid if markers are enabled, and not actually referenced behind the scenes as NASSP does its thing. If that's not the case, I like the idea in your last note.

[eddievhfan1984]

IIRC, the original .mkr files took into account that Orbiter 2016 had a flat mesh for the Moon, so shooting sights on landmarks had to account for that. Does the format also include altitude placement as well? From: em ***@***.***> Sent: Wednesday, December 20, 2023 11:50 To: orbiternassp/NASSP ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [orbiternassp/NASSP] Lat/Lon within Apollo Navigation Landmarks.mkr should be updated (Issue #1117) Yeah, not sure about how it should go forward, but the document I listed does provide all of the landmark coordinates to a T, geographically. At least when comparing the visual references provided in the document for each landmark, there's pretty much zero error. I'm assuming this .mkr file is only for visual aid if markers are enabled, and not actually referenced behind the scenes as NASSP does its thing. If that's not the case, I like the idea in your last note. — Reply to this email directly, view it on GitHub <#1117 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADHTXBJMDUAZD7MRWMK7IP3YKMJKRAVCNFSM6AAAAABACUMQA6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRUHAYTANRXG4> . You are receiving this because you are subscribed to this thread. <https://github.com/notifications/beacon/ADHTXBJZEBE4TBHDANJYHJLYKMJKRA5CNFSM6AAAAABACUMQA6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTPE3ALK.gif> Message ID: ***@***.*** ***@***.***> >

[Aeasala]

From what I can tell, I can't find any .mkr files -- vanilla to the base game, or not -- which have anything beyond lat/lon and a label for each entry. So I would assume no.

[indy91]

Hey @eddievhfan1984 good to hear from you!

Orbiter 2016 introduced a new marker format which can take the elevation into account and which I have implemented for Earth landmarks. But I really dislike the way this has to be done and I am hesitant to implement it for the lunar landmarks. You basically have to change a file that comes with Orbiter and the rendering of the marker is tied to rendering of Orbiter textures itself. So it's quite inconsistent if they even show up! The best long term solution would probably still be this newer format, I might try it again some time.