-
-
Notifications
You must be signed in to change notification settings - Fork 385
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mapping mission that Orbital Scanner XKM-1750 is unable to resolve. #5508
Comments
The save as provided has the player's ship outside of the frame of Gikegaryu f 1. That being said, the distance from the planet's sea level altitude to the player's ship is not displayed on the flight HUD, so in reality you're at a ~1.714Mm mean altitude. That's not far enough for the XKM-1750 to start operating, as it requires a 1.750Mm altitude. |
The save is just the location where the autopilot's "fly to vicinity of Gikegaryu f 1" stops, when the autopilot's high orbit option is then selected, and the ship moves towards Gikegaryu f 1, Gikegaryu f 1 becomes the current frame of reference when at an altitude approx 2.44Mm, this is when the scanner starts working (scanners only work if the current frame of reference is the planet due to be scanned, irrespective of the altitude above that planet). Between 2.44Mm and 2.33Mm (high orbit altitude of Gikegaryu f 1) is where MINIMUM ALTITUDE for Orbital Scanner XKM-1750 is reached. Hope this makes sense. |
I now get there is a difference in altitudes depending where it is measured from, still, if the scanner is not able to use any of the autopilot's orbits, the average space cadet lacking in the fine art of manual orbit calculations will probably need to carry both orbital scanners before embarking on a mission, because there will be many missions where installing just one of the scanners is not going to get a result as in the case above. |
I'll see if I can squeeze in a quick bugfix to display the sea level altitude instead of distance-to-center for this patch, to make it less confusing at the very least. |
Observed behaviour
Accepted a mission to perform an orbital scan of Gikegaryu F1, flew to vicinity of Gikegaryu F1, then used autopilot to get into a high orbit around the planet. Engaged Orbital Scanner XKM-1750 when the current frame of reference was Gikegaryu F1, scanning started briefly, but as the autopilot neared high orbit, the scanner no longer worked because the "minimum altitude" had been reached.
Expected behaviour
One would expect the premium scanner would be up for the job, I worked my ass off shuttling green haired humanoids around the galaxy in order to buy this premium piece of kit, where do I get a refund? ;-)
Steps to reproduce
Load the savefile, you are already in the vicinity of Gikegaryu F1.
sinonatrix_15.gz
(the attached file was renamed by adding .gz to allow upload).
Use the autopilot to enter a high orbit of the planet.
When close enough to engage the scanner, engage it, making sure the Orbital Scanner XKM-1750 is selected, it should work briefly.
As the ship approaches close to high orbit altitude, the scanner will reach "minimum altitude" and stop working.
The Orbital Scanner XKM-650 does work in this high orbit.
My pioneer version (and OS):
20230129


Linux Mint.
The text was updated successfully, but these errors were encountered: