Project

General

Profile

Bug #26938

Scanning arms obstruct hatches even when placed far enough away

Added by evanrichter 28 days ago. Updated 17 days ago.

Status:
Confirmed
Severity:
Low
Assignee:
Category:
EVA
Target version:
-
Start date:
12/27/2020
% Done:

10%

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

Description

I just noticed this issue with 1.11. I don't think it existed in 1.10. Scanning arms will prevent kerbals from exiting hatches when placed within a certain range, even when the arm itself isn't placed in front of the hatch. This will happen with any scanning arm, but the size of the arm does affect the range that it will block. My first thought was that the obstruction corelates with the scanning range, but it seems to be more complicated than that. It's possible to block one hatch, but not another, in which case, kerbals will exit via a second hatch if available. This issue is very easy to reproduce: just place a scanning arm near a crew module with kerbals onbard, then try to EVA after launching craft.

Lander Can with Scanning Arm.craft (9.43 KB) Lander Can with Scanning Arm.craft Craft file with only 2 parts: a crew module and a scanner arm evanrichter, 12/27/2020 03:27 PM
KSP all hatches obstructed.png (844 KB) KSP all hatches obstructed.png Screenshot showing kerbals are unable to exit craft evanrichter, 12/27/2020 03:37 PM
KSP only 1 hatch obtructed.PNG (1010 KB) KSP only 1 hatch obtructed.PNG Screenshot showing result if one hatch is obstructed, but another is available. evanrichter, 12/27/2020 03:37 PM
Player.log (866 KB) Player.log evanrichter, 12/27/2020 03:44 PM
hatch.jpg (93.7 KB) hatch.jpg Hatches work if I operate them directly [email protected], 12/27/2020 09:55 PM
55497
55498
55504

History

#1 Updated by Dunbaratu 28 days ago

evanrichter wrote:

I just noticed this issue with 1.11. I don't think it existed in 1.10. Scanning arms will prevent kerbals from exiting hatches when placed within a certain range, even when the arm itself isn't placed in front of the hatch. This will happen with any scanning arm, but the size of the arm does affect the range that it will block. My first thought was that the obstruction corelates with the scanning range, but it seems to be more complicated than that. It's possible to block one hatch, but not another, in which case, kerbals will exit via a second hatch if available. This issue is very easy to reproduce: just place a scanning arm near a crew module with kerbals onbard, then try to EVA after launching craft.

This explains a lot. I was having trouble with an airplane with a scanning arm in a cargo bay where it claimed hatches were obstructed when they weren't. The associated weirdness is that I got the message only when clicking "EVA" on the portrait of the kerbal, even though I could still EVA by clicking the cockpit hatch itself.

#2 Updated by [email protected] 28 days ago

55504

KSP lets me EVA through any hatch not blocked by the scanning arm in its parked position, if I click on the hatch directly to get the EVA option.

If I click on the 'EVA' button on the Kerbal portrait, and the first hatch is obstructed, then KSP lies to me and says "All hatches are obstructed". But if I then click on the secondary hatch, and then click EVA on the pop-up, I can EVA just fine.

#3 Updated by Dunbaratu 26 days ago

Here's some additional info from a modder that might provide help to KSP devs about this (I may be guessing about nothing since I can't see the actual code, so maybe this isn't worth anything, but I post it here in case knowing this helps).

As part of calculating the exact terrain height of a geoposition, the kOS mod does a Physics.Raycast with a bitmask that has layer 15 turned on, and all other layers turned off. This is to try to determine exactly where the surface of the terrain polygon is at a given precise latitude/longitude. Through some sleuthing by one of the users getting weird results, we discovered that if you trace the terrain height this routine gives, the terrain height traces a bizzarre phantom spherical bubble around scanner arms. This happens to look like it's exactly the same shape and size as the green glowing preview sphere you can see in the VAB when you click on the scanner arm and tell it to show you the scanner range. Remember that my routine is performing a Physics.Raycast looking only for hits on layer 15. This seems to be behaving as if a sphere exactly the same as the scanner range preview sphere still exists in some form during flight mode, and is using the same layer 15 as the terrain polygons do.

This anecdotal evidence maybe means (again, this is VERY speculative and I realize that humbly) that the check for blocked exit hatches is being fooled into thinking that phantom preview sphere counts as "terrain" blocking the exits.

#4 Updated by evanrichter 26 days ago

wrote:

KSP lets me EVA through any hatch not blocked by the scanning arm in its parked position, if I click on the hatch directly to get the EVA option.

If I click on the 'EVA' button on the Kerbal portrait, and the first hatch is obstructed, then KSP lies to me and says "All hatches are obstructed". But if I then click on the secondary hatch, and then click EVA on the pop-up, I can EVA just fine.

I didn't know about clicking on the hatch. That's a good workaround until this is bug is fixed.

#5 Updated by just_jim 17 days ago

  • Status changed from New to Confirmed
  • Assignee set to just_jim
  • % Done changed from 0 to 10

Also available in: Atom PDF