Unconscious Kerbal?

[barfing_skull]

Okay, after doing searches here and on Google "unconscious" or "knocked out" with site:forum.kerbalspaceprogram.com, I still haven't been able to find anything relevant on this.  I have to imagine this is a quite common question, so am I using the right term?

 

Something tosses my kerbals around in a rover, they're in a seat.  One or more of them goes floppy (unconscious), and can only do EVA reports and surface samples, but not leave the seat.  What is this called, and more importantly how do I wake them up?  Or move them to another vessel?  Do I just need to wait?

 

Cheers,

-BS

[Vanamonde]

Are you talking about a Kerbal who has become unresponsive while in a command chair, or on the surface of a world? Both are a bit of a problem. If there is another Kerbal on the surface, have him/her go over and run into the paralyzed one. This will often reset it. If there is no helper, try turning on the RCS pack with the R key, and try to jet the Kerbal loose. If that doesn't work, your only options are loading a save or sending a rescue mission. 

If in a command chair, that's an unusual bug which I myself have not experienced, and I do not recall what the fix might be, if there is one. 

[barfing_skull]

1 minute ago, Vanamonde said:

Are you talking about a Kerbal who has become unresponsive while in a command chair, or on the surface of a world? Both are a bit of a problem. If there is another Kerbal on the surface, have him/her go over and run into the paralyzed one. This will often reset it. If in a command chair, that's an unusual bug which I myself have not experienced, and I do not recall what the fix might be, if there is one. 

In this case, it's in a command chair.  It seems to be purposeful, as generally things like flipping the rover seem to precipitate it.  Yes, unresponsive.  I've seen it on the surface, too, several versions of the game ago, though.

 

This thread seems somewhat related, calling it a bug: http://forum.kerbalspaceprogram.com/index.php?/topic/101366-unresponsive-kerbal-after-rover-crash/

 

In that case, I was only able to wake the kerbal up by editing the save file.  There's some flag in there that indicates what state the kerbal is in.  Specifically, I think it's the "active = False" parameters here.  I compared this part of the file to another part that had a different, responsive and conscious kerbal.

						MakeReference
						{
							active = False
							guiActive = True
							guiActiveUncommand = False
							guiIcon = Control From Here
							guiName = Control From Here
							category = Control From Here
							guiActiveUnfocused = False
							unfocusedRange = 2
							externalToEVAOnly = True
						}
						OnDeboardSeat
						{
							active = False
							guiActive = True
							guiActiveUncommand = False
							guiIcon = Leave Seat
							guiName = Leave Seat
							category = Leave Seat
							guiActiveUnfocused = False
							unfocusedRange = 2
							externalToEVAOnly = True
						}
						RenameVessel
						{
							active = False
							guiActive = True
							guiActiveUncommand = False
							guiIcon = Rename Vessel
							guiName = Rename Vessel
							category = Rename Vessel
							guiActiveUnfocused = False
							unfocusedRange = 2
							externalToEVAOnly = True
						}
						ToggleStaging
						{
							active = True
							guiActive = False
							guiActiveUncommand = False
							guiIcon = Disable Staging
							guiName = Disable Staging
							category = Disable Staging
							guiActiveUnfocused = False
							unfocusedRange = 2
							externalToEVAOnly = True
						}

 

Cheers,

-BS

[barfing_skull]

Looks like:

                    state = Idle (Grounded)
versus

                    state = Seated (Command)
 

Also has something to do with it.

It really seems like there should be some way in-game to deal with this, unless it is actually a bug.

 

Cheers,

-BS

[Snark]

Have you tried just doing a quicksave and then loading the save?  I've found that that sometimes works well to wake up a dazed kerbal.

And incidentally, a common term for a kerbal in that state is "ragdoll", in case you're googling.

[steve_v]

10 hours ago, barfing_skull said:

...unless it is actually a bug.

AFAIK, that's exactly what it is. And an old, old bug at that.

[sal_vager]

This was addressed for 1.0.5, @barfing_skull are you playing 1.0.5 build 1028 ?

If yes your save would be very useful, you could put it on dropbox and link it here.

[Gaarst]

I had this thing happenning in 1.0.5 too. Luckily, I had a probe core on my rover and was still able to drive it after my two Kerbals were "knocked out" (not able to move, leave seat, etc).

Doing some sharp turns make the Kerbals fall out of their seats, and they get back to normal once they are on the ground (getting back up as if they just fell normally); so it seems that the Kerbals are unconscious like when they fall, but are also ejected out of the seat (which is why they fall from it easily), yet they are somehow clipping into the seat and therefore seem to still be seated and never "get back up" as they should until they are forced out of the seat (sharp turns work, maybe pushing them with another Kerbal might work).

Edited January 4, 2016 by Gaarst

[steve_v]

Yeah, it looks like the "ragdolled, but still in seat" (AKA kerbals becoming debris) bug was addressed, though there's another thread around here that makes me suspect there are still rare cases.
There's still the "ragdolled, and can't get up because clipping chair" issue though - this is still happening, albeit rarely, in 1.0.5.

Edited January 4, 2016 by steve_v
clarify

[barfing_skull]

7 hours ago, sal_vager said:

This was addressed for 1.0.5, @barfing_skull are you playing 1.0.5 build 1028 ?

If yes your save would be very useful, you could put it on dropbox and link it here.

It's 1.0.5.0, according to the startup screen.  I know I've seen a build number in previous version (still on the lower right?) but I'm not sure how to get anything more specific than 1.0.5.0.

 

I tried reloading a number of different saves/quicksaves, but nothing would wake poor Kimvy up.

 

Here's a link to the save file:

https://drive.google.com/file/d/0ByKJkpmLjsbmY1dxYUc0cnZDTXM/view?usp=sharing

I think the interesting part happens around line 84755.  This is the unedited save taken after I'd brought the Kerbal back to the vessel, but was still stuck in the rover.

 

Interestingly, I edited another save file to set the state to "active = True" in the above, and "state = Seated (Command)".  This allowed the Kerbal to wake up and leave the seat, but the rover itself got messed up.  A different Kerbal was no longer able to get into the seat (it said seat was obstructed upon clicking 'Board') and the other seat on the rover wasn't clickable at all.  I'm going to write the rover off for insurance purposes.

Hopefully the above is helpful....

 

Cheers,

-BS

[steve_v]

On 5/01/2016 at 1:45 PM, barfing_skull said:

I'm not sure how to get anything more specific than 1.0.5.0.

BuildID.txt in your KSP dir.

[barfing_skull]

19 hours ago, steve_v said:

BuildID.txt in your KSP dir.

Thanks.

 

build id = 01028
2015-11-10_18-03-24
Branch: master
 

Cheers,

-BS