Problems with TR-38-D

[THobson]

I have several vessels that use the TR-38-D decoupler that have no problems decoupling.  I recently modified one of the vessel slightly and as a result every time I try to decouple the TR-38-D the game crashes to the desktop.  Three points:

- it doesn't matter if I decouple using the staging process or right click and decouple manually, I get the same problem.

- the modifications I made to the vessel that has no problems was nowhere near this decoupler.

- I recall in earlier versions of KSP this decoupler had problems if there were struts that had to separate at the same time.  I have removed all such struts, still no use.

 

I am using v1.0.5.1028 in case that is relevant.

 

Is this a known issue?

Edited April 13, 2016 by THobson

[KocLobster]

I apologize for not being able to provide you with any specific help. However, I suggest uploading your crash logs, as well as requesting a mod move this to one of the tech support forums; you'll likely get more help that way.

[Snark]

Moving to the tech support forum.

After KSP crashes, what does the log say?  (KSP_Data.output_log.txt)

[THobson]

I don't have such a file.  I suspect KSP is killed too quickly for it to register.  I do have a long error log file provided by the Mac operating system though.

It is really odd.  I have just tested two other new rockets.  One works fine the other decouples okay but the back end of the rocket (the TR-38-D and everything below it) just vanishes.

[KocLobster]

You should have a folder (like 2016-4-13-16_142842 or something like that) denoting the date and time the crash happened, and inside one of the files should be your output/error log. This folder would be in your base KSP folder and is created anytime KSP crashes.

Are you sure you didn't miss it, or maybe were looking for a text file in the main KSP folder, for example?

[THobson]

I fear I have no such folder and I did look in all the folders I have for the file.  I think KSP is killed too quickly.  The instant I decouple I am back to the desktop.

[HebaruSan]

Check this previous thread. I've had crashes with this part as well, fixed by changing PhysicsSignificance in the part file.

For what it's worth, I haven't seen this problem happen in the 1.1 pre-release so far.

[THobson]

Thanks.  I had completely forgotten about this thread.  This is exactly the thread that I found the solution to way back in an earlier version of the game.  I have been playing v1.05 for along time now and experienced no problems at all with this decoupler so I thought the problem had been fixed, and forgot about this fix. The relevant file now has a different location, so for anyone else that has this problem (Mac/Linux only?):

Go to: KSP/GameData/Squad/Parts/Structural/Size3Decoupler

Open part.cfg and change PhysicsSignificance = 1 to PhysicsSignificance = 0

Apparently this gives the part physics rather than taking it away, or so I gather from the other thread.  This is not my solution, my only contribution here is to point others to the new location of the file.  And to moan a bit about the problem not being dealt with.  I suppose there is a good reason for this, in the earlier version this decoupler was a nightmare, but so far in 1.05 I only hit the problem once so maybe there is more going on behind the scenes.

By the way my workaround was to use 2 x Kerbodyne ADTP-2-3; 1x Rockomax Brand Decoupler and a lot of struts.  So I now have a manned vessel on its way to Moho with a rather strange backend.

 

EDIT:

I now see the problem.  Vessels that used to launch successfully now do not because there is so much flex at the TR-38-D that they bend over.  I am fixing this by using a lot of struts but it looks ugly.  What I really need is for PhysicsSignificance = 1 on launch and PhysicsSignificance = 0 on decouple.

Edited April 14, 2016 by THobson
Update

[soulsource]

On 13.4.2016 at 7:26 PM, THobson said:

I don't have such a file.  I suspect KSP is killed too quickly for it to register.  I do have a long error log file provided by the Mac operating system though.

It is really odd.  I have just tested two other new rockets.  One works fine the other decouples okay but the back end of the rocket (the TR-38-D and everything below it) just vanishes.

I know it's off topic, but for future reference: The log file is at a different location depending on operating system:

• On Linux it's in "~/.config/unity3d/Squad/Kerbal Space Program/Player.log", where the "~" character denotes the user's home folder.
• On OS X it's located in "/Users/$USER/Library/Logs/Unity/Player.log" .
• Last, but not least, on Windows it's being written to "KSP_Data\output_log.txt" in KSP's installation folder.