TR-38-D keeps crashing the game

[Irvin]

Hi,

could you tell me why the TR-38-D in the ship "Ore rover.craft" attached to this post keeps crashing my game every time I try to stage it ?

Step to reproduce: launch the ship, first aspargus staging, second aspargus staging, try to stage the TR38D => crash

If I try to manually separate (right click) it crashes too, and the second TR-38-D a bit above the first one crashes the game as well when activated manually.

The ship is a work in progress so please don't comment on the wacky design , this bug is definitely a showstopper for me.

Tested on KSP 1.0.2 linux 32 and 64 bits, ubuntu 14.04, nvidia drivers, Player.log attached to this message too, no crash report available all I have is a Segmentation Fault. I checked the memory while playing, at worst I got that:

total used free shared buffers cached

Mem: 2048424 1977324 71100 9360 336 41988

-/+ buffers/cache: 1935000 113424

Swap: 7875576 637920 7237656

With PhysicsSignificance set to 0 (old TR-38-D bug) the ship breaks apart before I can try to stage.

I'd like to know if there is something obviously wrong in my ship before issuing an official bug report.

Thanks a lot.

Player.log

Ore rover.craft

[H2O.]

I confirm the bug.

I have another ship that makes the game crash when I stage the TR-38-D decoupler.

However I have not be able to pinpoint the steps to reproduce yet. It idepend on other parts on the ship for sure, but with which ones does it crash? I don't know.

[sal_vager]

Hi Irvin, your sepratrons are destroying the TR-38-D while you are trying to stage, you need to angle the sepratrons away from the rocket.

[Irvin]

Hi,

You mean the sepratrons on top of the first aspargus stage?

I can't test right now but I will asap, anyway that shouldn't crash the game so I think I'll fill a bug report.

Thanks to both of you for the tests.

[H2O.]

To be more precise:

KSP Version: v0.1.0.2.0 Linux 64-bit

build id = 00842

2015-05-01_14-01-57

Branch: master

What Happens: Game Crash when big white decoupler is activated

Mods / Add-Ons: All Stock

Steps to Replicate:

_open the archive "big white decoupler bug" (provided below through dropbox)

_place the "Kassandra 2" ship in your VAB location

_launch the game

_place the "Kassandra 2" on the launch pad

_right click on the big white decoupler then click on "decouple"

Fixes/Workarounds:

/

Other:

_crash when activated through staging too

_doesn't crash when some parts are removed (like the command module)

_crash in linux 32 bit version too

_Log file and craft in the archive (dropbox link)

[Irvin]

Thanks !

Now all we have to do is to wait for a fix.

[Psycho_zs]

Stumbled upon this seconds before reentry.

remove 'PhysicsSignificance = 1' line from part config

Strangely, I've found it in already resolved bug http://bugs.kerbalspaceprogram.com/issues/2355

[Padishar]

9 hours ago, Psycho_zs said:

Strangely, I've found it in already resolved bug http://bugs.kerbalspaceprogram.com/issues/2355

Why strangely?  This thread is over 6 months old and is talking about version 1.0.2 of KSP.

[Psycho_zs]

Strangely because I've got this crash in 1.0.5 and found 'PhysicsSignificance = 1' just where it shouldn't be, since the bug was closed for 1.0.2.

Edited January 13, 2016 by Psycho_zs

[Padishar]

It wasn't fixed by changing that value in the part (that part needs that value to be set or the joints between it and 3.75m fuel tanks get very wobbly, this is a long-standing issue in the Unity physics code when objects with very different masses are joined together).  Instead, the underlying bug of separating a vessel into two at a physics insignificant part was supposedly fixed.  If you have an example craft that was built in 1.0.5 that gives this problem then you should edit that bug, set it to "Not fixed" and add the details and craft file so it can be investigated.

Edited January 13, 2016 by Padishar