Project

General

Profile

Bug #18105

Seated Kerbals Not Ocluded In Cargo/Materials Bays/Fairings.

Added by Cupcake.. over 1 year ago. Updated 7 months ago.

Status:
Closed
Priority:
Low
Assignee:
-
Category:
Physics
Target version:
Start date:
03/17/2018
% Done:

100%

Version:
Platform:
OSX, Windows
Expansion:
Core Game
Language:
English (US)
Votes:
Arrow u r green
Arrow d r red

Description

This is a bug that appeared in a previous version of KSP. As the title suggests Kerbals are no longer being occluded in cargo/materials bays/fairings and consequently producing huge amounts of drag and running the risk of exposure to re-entry heat.


Testing was done in 100% stock environment, no Mods. Windows 64.
I hope this bug can be fixed soon as it isn't ideal for my SSTO designs!

Oclusion Test.craft (36.1 KB) Oclusion Test.craft Test Craft Cupcake.., 03/17/2018 10:15 PM
Screen Shot 2018-03-29 at 5.32.00 PM.png (3.58 MB) Screen Shot 2018-03-29 at 5.32.00 PM.png The setup craft. two kerbals, one in a fairing and one in a mk1 cargo bay. enginersdontfly@gmail.com, 03/30/2018 12:37 AM
screenshot12.jpg (176 KB) screenshot12.jpg 555-555-0199@example.com k-ohara5a5a@oco.net, 06/30/2018 11:24 PM
34942
36925

Related issues

Related to Kerbal Space Program - Bug #18782: The kerman in the fairing will still be calculated resistanceClosed05/03/2018

Copied to Kerbal Space Program - Bug #19357: Seated Kerbals Not Occluded In Cargo/Service Bays/Fairings (except MK3)Moot03/17/2018

History

#1 Updated by enginersdontfly@gmail.com over 1 year ago

34942

I have found this same bug in my 1.4.2 OSX steam game.

Each kerbal is in a command char sitting on a cubic octagonal strut inside their respective cargo bays.

When the craft starts moving, the drag of the struts stays at zero, but the drag of the kerbal still exists.
https://imgur.com/FwLkLfJ
Entire album: https://imgur.com/a/R3q36

#3 Updated by fourfa2 over 1 year ago

Here's a craft that always shielded kerbals from drag in 1.2.x and 1.3.x, which now kills them:

https://kerbalx.com/fourfa/Nano-SSTO

#4 Updated by Cupcake.. about 1 year ago

Bug is still present in 1.4.3. Does that mean we have to file a fresh bug report?

#5 Updated by k-ohara5a5a@oco.net about 1 year ago

A duplicate report using version 1.4.3 exists
https://bugs.kerbalspaceprogram.com/issues/18782
So even if Squad staff filter by reported-in version, this will be found.
I started a thread to collect what information users might have, at
https://forum.kerbalspaceprogram.com/index.php?/topic/175939-draggy-kerbals-in-command-chairs-in-cargo-bays/

#6 Updated by TriggerAu about 1 year ago

Fixed in 1.4.4

#7 Updated by k-ohara5a5a@oco.net about 1 year ago

36925

What steps are required to demonstrate that the bug is fixed? If I
1) Install a fresh KSP 1.4.4
2) Download the craft file in the report
3) Separate the fairing-deploy from the engine-fire staging
4) Enable display of part-drag in the debug menu
4) EVA each Kerbal, walk them to one of the EAS-1 seats
5) Close the cargo bays
6) Stage engines
then I see the same results as in the original report, except that the Kerbal in the Mk3 cargo bay shows no drag (seen in screenshot12.jpg attached)
I can feel the drag when flying Fourfa's example craft.

On the user forum, I speculated that, after loading a Kerbal into the chair and closing the bay, an F5 quicksave / F9 quickload would give the desired behavior.

#8 Updated by bewing about 1 year ago

  • Related to Bug #18782: The kerman in the fairing will still be calculated resistance added

#9 Updated by bewing about 1 year ago

  • Copied to Bug #19357: Seated Kerbals Not Occluded In Cargo/Service Bays/Fairings (except MK3) added

#11 Updated by joshua.collins 9 months ago

  • Status changed from Confirmed to Ready to Test
  • Target version set to 1.5.0
  • % Done changed from 10 to 80

#12 Updated by k-ohara5a5a@oco.net 7 months ago

  • Status changed from Ready to Test to Resolved
  • % Done changed from 80 to 100

This one was fixed, all-the-way, in version 1.4.5 and remains so in 1.5.1

#13 Updated by joshua.collins 7 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF