nav0t / decouplershroud Goto Github PK

KSP mods should have v3.5 here:

Originally reported by forum user Tonka Crash at https://forum.kerbalspaceprogram.com/index.php?/topic/183869-mods-with-wrong-net-target-framework/

The problem is that the shroud (when set to automatic) defaults to the original diameter.

ofc it can be set manually.

`[LOG 02:52:45.366] Std dev for smoothing: 3 voxel total vol: 0.520383015116331 filled vol: 0.366359180381173

[LOG 02:52:45.397] Voxelization Time (ms): 231
[LOG 02:52:54.964] HeatShield0 added to ship - part count: 4
[EXC 02:52:54.973] NullReferenceException: Object reference not set to an instance of an object
DecouplerShroud.ModuleDecouplerShroud.detectSize ()
DecouplerShroud.ModuleDecouplerShroud.partReattached ()
Part.onAttach (.Part parent, Boolean first)
EditorLogic.attachPart (.Part part, .Attachment attach)
EditorLogic.m__8D ()
KerbalFSM.RunEvent (.KFSMEvent evt)
KerbalFSM.updateFSM (KFSMUpdateMode mode)
KerbalFSM.UpdateFSM ()
EditorLogic.Update ()
[LOG 02:53:15.029] Updating Untitled Space Craft
[LOG 02:53:15.078] Updating Untitled Space Craft
[LOG 02:53:15.131] Voxel Element CrossSection Area: 0.000269432849891823`

Getting a lot of this, just started happening recently, no idea what prompted it. Happens with various parts, in this instance I was attempting to attach a 0.625m heatshield to a custom command pod, but once it does happen it appears to happen with any of the decoupler shroud capable parts such as the T18 stack decoupler. Using v0.2

KSP.log

Pic:

Log and stuff:
https://www.dropbox.com/s/tupilrxxt3s7j8o/output_log.txt%20and%20stuff%202019-06-18-01.zip?dl=1

It appears that 0.6.1 was compiled with the .NET Target Framework set to 4.6.1 instead of 3.5 like it should. This throws an error in the KSP.log