Skip to content
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

Lunar Orbiter & Mapper PE Max Updates #2260

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

westlakem
Copy link

@westlakem westlakem commented Oct 7, 2023

First Lunar Orbiter & Mapper (Uncrewed) & the optional mission afterwards, requires you to collect visual imaging 2 (VI2) science from around the moon. The current contract doesn't require any PE Max, however the biome science has to be collected from space low. To see why I wasn't collecting the science, I had to reference 3 different materials:

  • the contract requirements (to see it was biome specific),
  • the Science window (too see that biome science only comes from low orbit),
  • and the wiki to see where "space low" started

In talks with the dev-feedback channel in discord, someone pointed out that someone else on the discord had to "cheat" their way to completing the contract because they weren't collecting the science, and assumed it's because they were in "space high" since you can complete the orbit requirements without ever dipping into space low. This PR is an attempt to bring the orbit requirements of the contract in line with the altitude requirements for the science.

Alternative: We could also lower the AP requirements to 150KM so they were completely in space low, but that may be more constrictive than the contract intends to be.

DISCLAIMER: I have not tested these changes and only assume this will edit the contract properly. Please advise if I need to change this (or feel free to do so yourself)

@hallucinogender
Copy link

Imposing a maximum periapsis limit is probably preferable from a gameplay perspective because it will still allow eccentric orbits, but with the condition that they approach closely enough to the Moon at least some of the time.

@lpgagnon
Copy link
Contributor

lpgagnon commented Oct 7, 2023

Given the goal of helping the player go to an orbit where the needed experiment will actually function, a max Pe of 150 may not do the best job. Yes, it will force the player to spend some time in the right situation; but a 499x149 orbit that spends 10s per orbit in the right situation is going to take forever to gather the required amount of science, and by the time the player realizes it, there's a good chance it's too late to save the mission.

So this is no substitute for actually spelling out what the experiment needs; it also highlights the broader problem that there's nothing at all in-game that explains where the low/high boundaries are.

@westlakem
Copy link
Author

Given the goal of helping the player go to an orbit where the needed experiment will actually function, a max Pe of 150 may not do the best job. Yes, it will force the player to spend some time in the right situation; but a 499x149 orbit that spends 10s per orbit in the right situation is going to take forever to gather the required amount of science, and by the time the player realizes it, there's a good chance it's too late to save the mission.

So this is no substitute for actually spelling out what the experiment needs; it also highlights the broader problem that there's nothing at all in-game that explains where the low/high boundaries are.

Yea, so the options are set the peMax to 150 so they spend some of their time there, or change the apMax to 150 to they spend all of their time in space low.

@lpgagnon
Copy link
Contributor

lpgagnon commented Oct 7, 2023

the other other option is to actually tell the player what he's being asked to do instead of just trying to force him into the right orbit without telling him why

@westlakem
Copy link
Author

the other other option is to actually tell the player what he's being asked to do instead of just trying to force him into the right orbit without telling him why

I'll leave it to the mods if they want to update the description to tell them why they need to be under 150, as it would be the only contract with that type of description.

@hallucinogender
Copy link

If no other contracts which require specific experiments include written details of the experiment parameters, that raises a bigger question: is the problem actually the fact that this particular contract doesn't have good enough orbital parameters, or is the problem that players don't know how to figure out what conditions an experiment needs in order to run? If the latter, then that needs to be addressed.

As for this contract, there should ideally be some possible leeway with orbit eccentricity. A satellite which reaches orbit of the Moon with an adequate periapsis but fails to circularize would, in reality, still be able to collect some useful data and fulfil its purpose, so ideally the same should be true for this contract in the game.

Perhaps a sufficient solution would be to introduce a condition for maximum periapsis that is lower than the upper bound for the space low environment (perhaps 10 to 20 kilometers lower than the upper bound). This would guarantee that a satellite which fulfils the contract's orbital parameters is also capable of collecting the data, and would mean that it spends more than the absolute minimum time in the low space environment.

@westlakem
Copy link
Author

westlakem commented Oct 7, 2023 via email

@SierraHotel84
Copy link
Contributor

SierraHotel84 commented Oct 7, 2023

the other other option is to actually tell the player what he's being asked to do instead of just trying to force him into the right orbit without telling him why

Sure, but that should be in addition to setting the orbit requirements correctly. What's the point of having mission parameters allowed that don't actually accomplish the purpose of the mission? If the goal of the mission is to map the lunar surface, then you shouldn't be able to complete the mission without actually gaining the science that was the intent of the mission anyway. If someone wants to go send an orbiter to the moon with the stated purpose of mapping the moon, and then not map the moon, they shouldn't get credit for completing the mission. Hence my comment on discord, mission parameters should match the experiment being used. I had to update some of the EOS requirements for that reason.

@Tsits11
Copy link

Tsits11 commented Oct 7, 2023

This is ridiculous. Visible imaging experiment specifies that it only gathers biome specific data in space LOW condition . A player can easily figure that out, no need for any changes as things stand really….

@NathanKell
Copy link
Member

I think it's worth considering whether we need to keep the spacelow threshold at 150km anyway. I'd certainly not like to enforce a Pe or Ap so low for this contract. It is equally true that other experiments also have requirements that can bite you--for example the experiments with minimum eccentricity, which also do not work in frozen orbits.

@hallucinogender
Copy link

I'd certainly not like to enforce a Pe or Ap so low for this contract.

That probably necessitates raising the space low threshold then. Are there any contracts designed around experiments which require space high around the Moon? If so, the lower bounds for orbits required by these contracts should be considered the upper bound for how much the space low threshold can be raised without interfering with them.

@westlakem
Copy link
Author

It is equally true that other experiments also have requirements that can bite you--for example the experiments with minimum eccentricity, which also do not work in frozen orbits.

Yes, however they do not have specific missions with collecting that science in them, that also has conflicting orbit requirements. EX: there's no mission that requires you to do a meteorite scan, as well as be in GSO. You're just unable to collect the science while in GSO.

I think it's worth considering whether we need to keep the spacelow threshold at 150km anyway. I'd certainly not like to enforce a Pe or Ap so low for this contract.

Raising the spacelow threshold to 500km would fix it for this contract (since it already has the apMax requirement at 500km), but I don't know what side effects that would have. I'm kind-of torn on this, as it would make getting space low a lot easier, but If I wasn't forced to be so close to the moon on my first principia playthrough, I would have never gone "Why are all my space low sats getting destroyed" and learn about frozen orbits.

@hallucinogender
Copy link

Raising the spacelow threshold to 500km would fix it for this contract (since it already has the apMax requirement at 500km), but I don't know what side effects that would have. I'm kind-of torn on this, as it would make getting space low a lot easier, but If I wasn't forced to be so close to the moon on my first principia playthrough, I would have never gone "Why are all my space low sats getting destroyed" and learn about frozen orbits.

It's probably best not to raise the space low threshold as high as 500km in that case. Perhaps this combined solution would work: raise the spacelow threshold to either 200km, 250km, or 300km, and impose a maximum periapsis limit 50km below that. As long as this doesn't conflict with any other contracts, I don't see an obvious reason why it wouldn't resolve the issue.

@westlakem
Copy link
Author

So who takes it from here? I'm not a maintainer and need some direction here from someone who is.

@siimav
Copy link
Contributor

siimav commented Apr 18, 2024

I feel like both raising the space low threshold and clarifying the requirement in contract description is the way forward.
Btw, I wonder why was 150km chosen in the first place? Sounds awfully low, especially when using Principia. I would suggest 250km instead.

@Capkirk123
Copy link
Member

The moon space low threshold has been increased to 250 km here. I'm not sure if we still want to specify a max perilune to force an orbit that passes through moon space low, but the contract should be more reasonable now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants