Project

General

Profile

Bug #22726

Kerbal on eva not responding to controls

Added by solar138 almost 5 years ago. Updated almost 5 years ago.

Status:
Confirmed
Severity:
Low
Assignee:
-
Category:
Controls and UI
Target version:
-
Start date:
06/01/2019
% Done:

10%

Version:
Platform:
Windows
Expansion:
Breaking Ground, Core Game
Language:
English (US)
Mod Related:
No
Votes:
Arrow u r green
Arrow d r red

Description

Sometimes, when a Kerbal enters EVA, it stops responding to controls and wanders lets go of the command pod. The Kerbal acts like it is a vessel without control. A Kerbal on EVA always has control. Since it has crew, the Kerbal, it shouldn't ever lose control. I don't think this is actually due to it losing control since the indicator on the top left still says it has EVA control. Please correct me if this isn't a bug, I am new to KSP and the bug tracker.

History

#1 Updated by Kirk almost 5 years ago

Did you enable RCS (press "R")?

#2 Updated by solar138 almost 5 years ago

Kirk wrote:

Did you enable RCS (press "R")?

Yes, I did enable RCS.

#3 Updated by Anth12 almost 5 years ago

got a screen shot or a quicksave that has the craft with the kerbal eva bug happening?

#4 Updated by solar138 almost 5 years ago

Anth12 wrote:

got a screen shot or a quicksave that has the craft with the kerbal eva bug happening?

Sorry, but no. I think this might be a one time bug.

#5 Updated by Anth12 almost 5 years ago

Sounds familiar actually. Seen/read about a few occurrences of similar things happening, not sure if they were when going on EVA though

#6 Updated by Geschosskopf almost 5 years ago

  • Status changed from New to Confirmed
  • % Done changed from 0 to 10

Unresponsive EVA Kerbals is caused by having SAS turned off. If SAS is off, then the Kerbal will not respond to jetpack commands. If you turn SAS on, then the Kerbal returns to control.

I believe this is related to how a ship's SAS will turn off if the pilot EVAs. Even when the pilot returns to the ship, SAS will still be turned off and must be turned on again manually.

Both of these issues are new to 1.7.1. However, I don't know if they're intentional or not.

Also available in: Atom PDF