Honestly, it's not hard at all to fly to any given set of coordinates.
0, 90, 180, 270 is all you really need to know.
If you are at 100,-80 and need to get to -50, 20, you can do it "the hard way", and align yourself with 0, 90, 180 or 270 on the bearing indicator and fly in that direction and watch what your lat and log numbers do - either increase or decrease, until you reach your destination, or you can use something like: https://edbearingcalc.neocities.org/ and it will tell you to align to a course of 146 degrees and fly that way until you reach your destination.
That's it. That's all there is to it.
Yeah, it might be nice to include this kind of functionality, but.. the math involved in calculating a heading is somewhat complex - here's an example:
"Bearing from point A to B, can be calculated as,β = atan2(X,Y),
where, X and Y are two quantities and can be calculated as:
X = cos θb * sin ∆L
Y = cos θa * sin θb – sin θa * cos θb * cos ∆L
Lets us take an example to calculate bearing between the two different points with the formula:
So X and Y can be calculated as,
- Kansas City: 39.099912, -94.581213
- St Louis: 38.627089, -90.200203
X = cos(38.627089) * sin(4.38101)
X = 0.05967668696
And
Y = cos(39.099912) * sin(38.627089) – sin(39.099912) * cos(38.627089) * cos(4.38101)
Y = 0.77604737571 * 0.62424902378 – 0.6306746155 * 0.78122541965 * 0.99707812506
Y = -0.00681261948
So as, β = atan2(X,Y) = atan2(0.05967668696, -0.00681261948)
β = 96.51°
This means, from Kansas City if we move in 96.51° bearing direction, we will reach St Louis." (source: http://www.igismap.com/formula-to-f...-angle-between-two-points-latitude-longitude/)
While you are at it FDEV (because this would be wonderful), please make the system have multi-waypoints for ship/SRV races (mayby a mini-map of the planet that can be opend up/in the top right corner?) and can be shared between commanders. Ive seen someone create a program once that hacked the ram and could already sort out these kind of things (can anyone remember the name of that program? It had speed indicators and RPM as well... Seems he didnt really like anyone to have it...), so it couldnt be to hard to create. You would do us a HUGE favour with this ei not having the need for human markers all the time...
Honestly, it's not hard at all to fly to any given set of coordinates.
0, 90, 180, 270 is all you really need to know.
If you are at 100,-80 and need to get to -50, 20, you can do it "the hard way", and align yourself with 0, 90, 180 or 270 on the bearing indicator and fly in that direction and watch what your lat and log numbers do - either increase or decrease, until you reach your destination, or you can use something like: https://edbearingcalc.neocities.org/ and it will tell you to align to a course of 146 degrees and fly that way until you reach your destination.
That's it. That's all there is to it.
Yeah, it might be nice to include this kind of functionality, but.. the math involved in calculating a heading is somewhat complex - here's an example:
"Bearing from point A to B, can be calculated as,β = atan2(X,Y),
where, X and Y are two quantities and can be calculated as:
X = cos θb * sin ∆L
Y = cos θa * sin θb – sin θa * cos θb * cos ∆L
Lets us take an example to calculate bearing between the two different points with the formula:
So X and Y can be calculated as,
- Kansas City: 39.099912, -94.581213
- St Louis: 38.627089, -90.200203
X = cos(38.627089) * sin(4.38101)
X = 0.05967668696
And
Y = cos(39.099912) * sin(38.627089) – sin(39.099912) * cos(38.627089) * cos(4.38101)
Y = 0.77604737571 * 0.62424902378 – 0.6306746155 * 0.78122541965 * 0.99707812506
Y = -0.00681261948
So as, β = atan2(X,Y) = atan2(0.05967668696, -0.00681261948)
β = 96.51°
This means, from Kansas City if we move in 96.51° bearing direction, we will reach St Louis." (source: http://www.igismap.com/formula-to-f...-angle-between-two-points-latitude-longitude/)
Dear People Who Decide What Gets Done in Frontier,
Planetary navigation is terrible.
This becomes apparent when trying to reach a set of LAT/LON coordinates on a planet surface, when there is no waypoint (like in a surface recovery mission).
Try reaching a LAT/LON from space, to glide, to the surface. It is nigh on impossible.
Sure, we can get into Orbital Cruise, and we have a display of LAT/LON. But then you're trying to change direction of orbit relative to planet surface and the coords. Trying to get the coords to go up/down/positive/negative at just the correct rate so they will converge at the desired LAT/LON.
Then, even when you're getting close to the target, you have to try and judge the right moment when to come out of orbital cruise to glide down to the surface - you'll probably overshoot badly.
In short, this is a terrible experience.
So for 2.4 - please, please allocate some dev time to marking a surface waypoint we can target, by way of the 3D surface map in the System Map.
Please!?
Hi Qohen! o7
Yeah nothing new - but asking just for 1 small thing - being able to enter a bloody Lat and Lon coord and having that as a marker to aim at. I figured it would be more likely to be considered as a single, simple issue, rather than bombard Frontier with all sorts of awesome ideas at once. And this one single issue would be a massive and instant QoL improvement in itself
Regards
Dear People Who Decide What Gets Done in Frontier,
Planetary navigation is terrible.
This becomes apparent when trying to reach a set of LAT/LON coordinates on a planet surface, when there is no waypoint (like in a surface recovery mission).
Try reaching a LAT/LON from space, to glide, to the surface. It is nigh on impossible.
Sure, we can get into Orbital Cruise, and we have a display of LAT/LON. But then you're trying to change direction of orbit relative to planet surface and the coords. Trying to get the coords to go up/down/positive/negative at just the correct rate so they will converge at the desired LAT/LON.
Then, even when you're getting close to the target, you have to try and judge the right moment when to come out of orbital cruise to glide down to the surface - you'll probably overshoot badly.
In short, this is a terrible experience.
So for 2.4 - please, please allocate some dev time to marking a surface waypoint we can target, by way of the 3D surface map in the System Map.
Please!?
Honestly, it's not hard at all to fly to any given set of coordinates.
0, 90, 180, 270 is all you really need to know.
If you are at 100,-80 and need to get to -50, 20, you can do it "the hard way", and align yourself with 0, 90, 180 or 270 on the bearing indicator and fly in that direction and watch what your lat and log numbers do - either increase or decrease, until you reach your destination, or you can use something like: https://edbearingcalc.neocities.org/ and it will tell you to align to a course of 146 degrees and fly that way until you reach your destination.
That's it. That's all there is to it.
Yeah, it might be nice to include this kind of functionality, but.. the math involved in calculating a heading is somewhat complex - here's an example:
"Bearing from point A to B, can be calculated as,β = atan2(X,Y),
where, X and Y are two quantities and can be calculated as:
X = cos θb * sin ∆L
Y = cos θa * sin θb – sin θa * cos θb * cos ∆L
Lets us take an example to calculate bearing between the two different points with the formula:
So X and Y can be calculated as,
- Kansas City: 39.099912, -94.581213
- St Louis: 38.627089, -90.200203
X = cos(38.627089) * sin(4.38101)
X = 0.05967668696
And
Y = cos(39.099912) * sin(38.627089) – sin(39.099912) * cos(38.627089) * cos(4.38101)
Y = 0.77604737571 * 0.62424902378 – 0.6306746155 * 0.78122541965 * 0.99707812506
Y = -0.00681261948
So as, β = atan2(X,Y) = atan2(0.05967668696, -0.00681261948)
β = 96.51°
This means, from Kansas City if we move in 96.51° bearing direction, we will reach St Louis." (source: http://www.igismap.com/formula-to-f...-angle-between-two-points-latitude-longitude/)
Too lazy to scroll through all of these posts do maby this has been suggested but, why not add the option to input coordinates into the ship to auto pilot it's self much like the docking computer?
No new equipment needed just make it a part of the planetary approach suite