Project

General

Profile

Bug #19402

Exploding Struts and Wheel Damage when Docking/Undocking

Added by XLjedi over 6 years ago. Updated almost 6 years ago.

Status:
Closed
Severity:
Low
Assignee:
-
Category:
Gameplay
Target version:
Start date:
07/12/2018
% Done:

100%

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

Description

Another example of a bug that I believe came along with the change to the new Unity engine in 1.4. Again, the parts are very prone to exploding and/or taking damage now where in prior versions it was not a problem. Similar to my other bug report related to parts getting damaged when exiting Mk3 Cargo Bay doors.

In this case, if you dock/undock with a vehicle on the ground...
1) Landing Struts in contact with the ground tend to explode
2) Wheels in contact with the ground will take damage

The dock/undock can be triggered with any associated parts: Docking Ports, Claw Grabbing Unit, even entereing/leavig the External Command Chair

In this example video, I have a very simple craft with an External Command Chair.
https://youtu.be/0-hYURMqbbk

You'll notice as I enter and leave the command chair, the struts in contact with the ground instantly explode, and the large wheels progressively take damage until eventually all 6 are destroyed down to the rims.

The example craft file in the video is provided as an attached file.

Exploding_Struts_and_Wheels.craft (28.8 KB) Exploding_Struts_and_Wheels.craft Sample Exploding Strut Craft XLjedi, 07/12/2018 05:51 AM

History

#1 Updated by bewing over 6 years ago

  • Status changed from New to Investigating
  • % Done changed from 0 to 20

#2 Updated by dok_377 over 6 years ago

Can also confirm this bug for wheels from Making History. On docking they immediately explode having just a slight amount of load on them, and they break any time kerbals try to board/disembark from a seat. It seems like all the wheels susceptible to this bug in one way or another.

#3 Updated by joshua.collins about 6 years ago

  • Status changed from Investigating to Ready to Test
  • Target version set to 1.5.0
  • % Done changed from 20 to 80

Please recheck in 1.5.0

#4 Updated by Anonymous almost 6 years ago

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

1.5.1

#5 Updated by joshua.collins almost 6 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF