Roundtrip locked inside

By sakura_sk

February 14, 2021

Branch: Preview Branch

Version: Windows

Fixed

I don't know if that change "Rockets automatically request their crew/kick out passengers when the launch button is pressed, rather than requiring correct crew to press the button. This obsoletes the "Auto" crew setting and makes launching a rocket less fiddly" makes "auto" obsolete but it definitely makes roundtrip bugs more visible... (I used "auto" a lot before :cry: .... It didn't trap dupes ) Currently having roundtrip on, locks dupes in rocket when rocket returns from a starmap trip (no planet destination selected) and only clearing "crew" selections lets the dupe out/enables access to command module.

Steps to reproduce:

Trying to move a dupe "manually", currently inside the rocket, works like below:

Spoiler

Clicking dupe

Clicking "move to"

Clicking planetoid (right column), then clicking location

Dupe moves to location

If rocket is launched and returns (roundtrip selected), dupe cannot move outside the rocket

Spoiler

Rocket options : Roundtrip selected, all dupes permitted, Nikola set as crew

Launch and return (roundtrip to orbit and back just to be quicker about it)

Now Nikola can't be "manually" moved outside the rocket.

I first noticed it while testing how to not let dupes out until surroundings are in safe temperature. The only oxylite available in order to refill small oxidizer tank when the door to rocket silo was closed, was inside the rocket module but dupes didn't try to refill it

Reloading a save after rocket has landed fixes bug

Unchecking dupe as crew after rocket returns also fixes bug

I still haven't found a way, how roundtrip could work correctly....

Steps to Reproduce

Launch small petroleum engine rocket (roundtrip to orbit already selected).

When rocket returns try to move dupe outside.

Dupe is trapped inside (although there is no alert about that)

The Needy 26 roundtrip lock.sav

Followers 0

Go to bugs

User Feedback

2 Comments

A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.