You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed an issue twice now where kerbals on my space station will become "grouchy" (tourists) several days before the timer in the life support status window says they will. Just now it happened as I was setting up the rendezvous between my crew rotation ship and the station, i.e. I was definitely not making any changes to the station's habitation at the time.
I have some screenshots as evidence:
at launch time, my KSS kerbals had 9d4h left until homesickness (for reference) and 7 to 8 days of habitation left.
But then at docking time, four hours have passed (9d0h until homesickness) but their habitation has expired!
And to be clear, their habitation expired before the docking actually happened (and I'm pretty sure before KSS was even in physics range, let alone resource-sharing range), and my KSS has sufficient electricity generation and storage that my hab didn't turn off at night or anything like that.
As a workaround, is there any way to snap kerbals out of tourist mode so I can at least EVA them out to my crew rotation ship?
The text was updated successfully, but these errors were encountered:
If you dock a vessel with more hab time, that should get them to snap out of being tourists. The only other alternative, afaik, is to use save file editing.
I've noticed an issue twice now where kerbals on my space station will become "grouchy" (tourists) several days before the timer in the life support status window says they will. Just now it happened as I was setting up the rendezvous between my crew rotation ship and the station, i.e. I was definitely not making any changes to the station's habitation at the time.
I have some screenshots as evidence:
As a workaround, is there any way to snap kerbals out of tourist mode so I can at least EVA them out to my crew rotation ship?
The text was updated successfully, but these errors were encountered: