Can't launch at Desert or Woomerang even though they are on the map.

[maestro]

So now that there are discoverable launch sites I went to a few of them to unlock them. Desert and Woomerang are on my map already and I even flew over Desert to ensure it was unlocked but because I don't think I clicked "Enable additional launch sites", I still cannot spawn at them.

The game should be treating them as discoverable launch sites at least, unlocking them but they seem permenantly locked if they weren't enabled before a career was started.

[miklkit]

You can change that in "escape" --> "settings" --> "advanced settings". I did.

[maestro]

Originally posted by miklkit:

You can change that in "escape" --> "settings" --> "advanced settings". I did.

I'll check that out thanks.

[miklkit]

Oops! I left out one step. difficulty settings

[maestro]

Ok. It still does seem odd though that you have to enable "Allow other launch sites" to use a site that you already discovered.

I think Dessert site and Woomerang site should just be treated like the new sites: you can launch at all them if you discovered them unless "Allow other launch sites" is enabled in which case you cannot regardless of if they are discovered or not.

I just checked my current career game and I *can* launch at any of the new sites even though "Allow other.." is unchecked. The legacy sites don't seem updated for the new system and the new system doesn't seem to disallow non-KSC launches.

I'm probably overthinking. It's more likely just the way the devs intended the sites to be.

[elu]

Originally posted by Maestro4202:

Ok. It still does seem odd though that you have to enable "Allow other launch sites" to use a site that you already discovered.

I think Dessert site and Woomerang site should just be treated like the new sites: you can launch at all them if you discovered them unless "Allow other launch sites" is enabled in which case you cannot regardless of if they are discovered or not.

I just checked my current career game and I *can* launch at any of the new sites even though "Allow other.." is unchecked. The legacy sites don't seem updated for the new system and the new system doesn't seem to disallow non-KSC launches.

I'm probably overthinking. It's more likely just the way the devs intended the sites to be.

Yeah this seems super buggy. That's exactly what's going on. If you don't enable the Allow other launch sites setting, you can still discover the new discoverable launch sites and then launch from those, but you can never "discover" Woomerang or Desert Airfield, so they aren't available in the VAB. Seems like the setting needs another possible value; eg Allow All / Allow If Discovered / Allow None, and then fix these two sites so they behave accordingly. Or at the very least, just that last part... make them discoverable if the setting is disabled.

It makes sense from a difficulty standpoint that preventing the use of additional launch sites provides a challenge, but if all you have to do is discover the others (sans the older bugged ones), then that subverts the difficulty setting and you might as well just allow them up front. This needs fixing, imo. Kinda confusing.

[GunsForBucks]

Originally posted by elu:

Originally posted by Maestro4202:

Ok. It still does seem odd though that you have to enable "Allow other launch sites" to use a site that you already discovered.

I think Dessert site and Woomerang site should just be treated like the new sites: you can launch at all them if you discovered them unless "Allow other launch sites" is enabled in which case you cannot regardless of if they are discovered or not.

I just checked my current career game and I *can* launch at any of the new sites even though "Allow other.." is unchecked. The legacy sites don't seem updated for the new system and the new system doesn't seem to disallow non-KSC launches.

I'm probably overthinking. It's more likely just the way the devs intended the sites to be.

Yeah this seems super buggy. That's exactly what's going on. If you don't enable the Allow other launch sites setting, you can still discover the new discoverable launch sites and then launch from those, but you can never "discover" Woomerang or Desert Airfield, so they aren't available in the VAB. Seems like the setting needs another possible value; eg Allow All / Allow If Discovered / Allow None, and then fix these two sites so they behave accordingly. Or at the very least, just that last part... make them discoverable if the setting is disabled.

It makes sense from a difficulty standpoint that preventing the use of additional launch sites provides a challenge, but if all you have to do is discover the others (sans the older bugged ones), then that subverts the difficulty setting and you might as well just allow them up front. This needs fixing, imo. Kinda confusing.

The best place to post this suggestion would be on their official website.
Even though they are all working on KSP2 right now, there is a possibility they will come back with a final patch to fix up this games issues with the construction update.\

At least I read something that alluded to that.

But I don't think anything suggested in the steam forums will make it to the ears developers for patch consideration. They have a whole bug tracker thing over there.

[elu]

Originally posted by GunsForBucks:

The best place to post this suggestion would be on their official website.
Even though they are all working on KSP2 right now, there is a possibility they will come back with a final patch to fix up this games issues with the construction update.\

At least I read something that alluded to that.

But I don't think anything suggested in the steam forums will make it to the ears developers for patch consideration. They have a whole bug tracker thing over there.

Yeah I know, I wasn't putting those thoughts here with that expectation. Sorry if it came across that way. Just wanted to chime in and see if the idea had any resonance here since others have noticed this sort of confusing behavior too. Not bothered by it enough to submit a formal ticket.