beeble42

Sorry about that. Thanks in advance for the fix.

Looks like BackgroundResources, and therefore DeepFreeze, now have a TacLifeSupport dependency. [LOG 19:42:12.712] 9/6/2019 7:42:12 PM,DeepFreeze,FixedUpdate failed to update DeepFreeze Internal Vessel Memory [LOG 19:42:12.713] 9/6/2019 7:42:12 PM,DeepFreeze,Err: System.IO.FileNotFoundException: Could not load file or assembly 'TacLifeSupport, Version=0.13.12.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. File name: 'TacLifeSupport, Version=0.13.12.0, Culture=neutral, PublicKeyToken=null' at BackgroundResources.InterestedVessel.UpdateModules () [0x00000] in <filename unknown>:0 at BackgroundResources.InterestedVessel..ctor (.Vessel vessel, .ProtoVessel protovessel) [0x00000] in <filename unknown>:0 at BackgroundResources.UnloadedResources.AddInterestedVessel (.ProtoVessel vessel) [0x00000] in <filename unknown>:0 at DF.DFIntMemory.CheckVslUpdate () [0x00000] in <filename unknown>:0 at DF.DFIntMemory.FixedUpdate () [0x00000] in <filename unknown>:0 That's repeated for MB after MB in my log since launching a vessel with DF parts. I can't access the settings window at KSC. The settings button isn't visible. So I'm running the mod with default settings. Alarms aren't working, but I can freeze kerbals just fine. I didn't discover this until after looking for the settings menu. When switching to my DF testing vessel from the tracking station, DF logs a bunch of NREs. [LOG 19:56:46.794] [FLIGHT GLOBALS]: Switching To Vessel DeepFreeze Test Station ---------------------- [LOG 19:56:46.794] setting new dominant body: Kerbin FlightGlobals.mainBody: Kerbin [LOG 19:56:46.811] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:14365 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.811] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:14365 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.812] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:14332 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.812] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:14332 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.812] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:14217 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.812] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:14217 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.813] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:13603 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.813] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:13603 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.813] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:12653 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.813] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:12653 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.813] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:12433 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.813] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:12433 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.815] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:12003 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.815] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:12003 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.815] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:8250 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.815] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:8250 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.815] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:7865 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.815] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:7865 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.815] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:7441 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.815] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:7441 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.817] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:7064 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.817] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:7064 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.817] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:999 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.817] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:999 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.817] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:461 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.817] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:461 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.817] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:459 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.817] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:459 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.818] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:287 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.818] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:287 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.818] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:263 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.818] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:263 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.818] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:191 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [LOG 19:56:46.818] [PartSet]: Failed to add Resource -182302047 to Simulation PartSet:191 as corresponding Part CRY-1300 Cryonic Freezing Chamber-0 SimulationResource was not found. [WRN 19:56:46.834] [Part]: PartModule UIRootManager at CRY-1300Freezer, index 10: index exceeds module count as defined in cfg. Looking for UIRootManager in other indices... [WRN 19:56:46.834] ...no UIRootManager module found on part definition. Skipping... [WRN 19:56:46.834] PartModule is null. [WRN 19:56:46.834] [Part]: PartModule RasterPropMonitorComputer at CRY-1300Freezer, index 10: index exceeds module count as defined in cfg. Looking for RasterPropMonitorComputer in other indices... [WRN 19:56:46.834] ...no RasterPropMonitorComputer module found on part definition. Skipping... [WRN 19:56:46.834] PartModule is null. [WRN 19:56:46.834] [Part]: PartModule FARPM at CRY-1300Freezer, index 10: index exceeds module count as defined in cfg. Looking for FARPM in other indices... [WRN 19:56:46.834] ...no FARPM module found on part definition. Skipping... [WRN 19:56:46.834] PartModule is null. [LOG 19:56:46.834] DeepFreezer OnDestroy [LOG 19:56:46.834] DeepFreezer END OnDestroy [WRN 19:56:46.842] [Part]: PartModule indexing mismatch at LS.Tank.250, index 6. Node 'TweakScaleDisabled' found in loaded data, but 'TweakScale' is defined in prefab. Looking for TweakScaleDisabled in other indices... [WRN 19:56:46.842] ...no TweakScaleDisabled module found on part definition. Skipping... [WRN 19:56:46.842] PartModule is null. [WRN 19:56:46.842] [Part]: PartModule indexing mismatch at LS.Tank.250, index 6. Node 'TweakScaleDisabled' found in loaded data, but 'TweakScale' is defined in prefab. Looking for TweakScaleDisabled in other indices... [WRN 19:56:46.842] ...no TweakScaleDisabled module found on part definition. Skipping... [WRN 19:56:46.842] PartModule is null. [LOG 19:56:46.898] [MechJeb2] Loading Mechjeb 2.8.3 [WRN 19:56:47.014] [Part]: PartModule ModuleSwitchableTank at RCSTank1-2, index 7: index exceeds module count as defined in cfg. Looking for ModuleSwitchableTank in other indices... [WRN 19:56:47.015] ...no ModuleSwitchableTank module found on part definition. Skipping... [WRN 19:56:47.015] PartModule is null. [WRN 19:56:47.209] [Part]: PartModule RasterPropMonitorComputer at CRY-0300Freezer, index 8: index exceeds module count as defined in cfg. Looking for RasterPropMonitorComputer in other indices... [WRN 19:56:47.209] ...no RasterPropMonitorComputer module found on part definition. Skipping... [WRN 19:56:47.209] PartModule is null. [WRN 19:56:47.209] [Part]: PartModule FARPM at CRY-0300Freezer, index 8: index exceeds module count as defined in cfg. Looking for FARPM in other indices... [WRN 19:56:47.209] ...no FARPM module found on part definition. Skipping... [WRN 19:56:47.209] PartModule is null. [LOG 19:56:47.241] [MechJeb2] Loading Mechjeb 2.8.3 [LOG 19:56:47.391] [MechJeb2] Loading Mechjeb 2.8.3 [LOG 19:56:47.491] Camera Mode: AUTO [LOG 19:56:47.517] [BetterBurnTime] Vessel changed to DeepFreeze Test Station [LOG 19:56:47.518] DeepFreezer OnVesselChange onvslchgInternal False activevessel baeb85bc-464a-40a5-9b5a-358f2e860436 parametervesselid baeb85bc-464a-40a5-9b5a-358f2e860436 this vesselid baeb85bc-464a-40a5-9b5a-358f2e860436 this partid 2814029613 [LOG 19:56:47.523] DeepFreezer OnVesselChange onvslchgInternal False activevessel baeb85bc-464a-40a5-9b5a-358f2e860436 parametervesselid baeb85bc-464a-40a5-9b5a-358f2e860436 this vesselid baeb85bc-464a-40a5-9b5a-358f2e860436 this partid 740040869 [LOG 19:56:47.530] DeepFreezer OnVesselChange onvslchgInternal False activevessel baeb85bc-464a-40a5-9b5a-358f2e860436 parametervesselid baeb85bc-464a-40a5-9b5a-358f2e860436 this vesselid baeb85bc-464a-40a5-9b5a-358f2e860436 this partid 2814029613 [LOG 19:56:47.530] DeepFreezer OnVesselChange onvslchgInternal False activevessel baeb85bc-464a-40a5-9b5a-358f2e860436 parametervesselid baeb85bc-464a-40a5-9b5a-358f2e860436 this vesselid baeb85bc-464a-40a5-9b5a-358f2e860436 this partid 740040869 [LOG 19:56:47.531] DeepFreezer OnVesselChange onvslchgInternal False activevessel baeb85bc-464a-40a5-9b5a-358f2e860436 parametervesselid baeb85bc-464a-40a5-9b5a-358f2e860436 this vesselid 01fe992f-9fbd-473a-9396-536b616d5b86 this partid 3993708272 [ERR 19:56:47.531] Exception handling event onVesselChange in class DeepFreezer:System.NullReferenceException: at (wrapper managed-to-native) UnityEngine.AudioSource:get_isPlaying () at DF.DeepFreezer.OnVesselChange (.Vessel vessel) [0x00000] in <filename unknown>:0 at EventData`1[Vessel].Fire (.Vessel data) [0x00000] in <filename unknown>:0 [EXC 19:56:47.531] NullReferenceException DF.DeepFreezer.OnVesselChange (.Vessel vessel) EventData`1[Vessel].Fire (.Vessel data) UnityEngine.Debug:LogException(Exception) EventData`1:Fire(Vessel) FlightGlobals:setActiveVessel(Vessel, Boolean) FlightGlobals:SetActiveVessel(Vessel) FlightDriver:Start() [LOG 19:56:47.531] DeepFreezer OnVesselChange onvslchgInternal False activevessel baeb85bc-464a-40a5-9b5a-358f2e860436 parametervesselid baeb85bc-464a-40a5-9b5a-358f2e860436 this vesselid 01fe992f-9fbd-473a-9396-536b616d5b86 this partid 2142072888 [ERR 19:56:47.531] Exception handling event onVesselChange in class DeepFreezer:System.NullReferenceException: at (wrapper managed-to-native) UnityEngine.AudioSource:get_isPlaying () at DF.DeepFreezer.OnVesselChange (.Vessel vessel) [0x00000] in <filename unknown>:0 at EventData`1[Vessel].Fire (.Vessel data) [0x00000] in <filename unknown>:0 [EXC 19:56:47.531] NullReferenceException DF.DeepFreezer.OnVesselChange (.Vessel vessel) EventData`1[Vessel].Fire (.Vessel data) UnityEngine.Debug:LogException(Exception) EventData`1:Fire(Vessel) FlightGlobals:setActiveVessel(Vessel, Boolean) FlightGlobals:SetActiveVessel(Vessel) FlightDriver:Start() [LOG 19:56:47.532] DeepFreezer OnVesselChange onvslchgInternal False activevessel baeb85bc-464a-40a5-9b5a-358f2e860436 parametervesselid baeb85bc-464a-40a5-9b5a-358f2e860436 this vesselid 570dac36-4111-48d0-97b0-e94b514671d9 this partid 3617464277 [ERR 19:56:47.532] Exception handling event onVesselChange in class DeepFreezer:System.NullReferenceException: at (wrapper managed-to-native) UnityEngine.AudioSource:get_isPlaying () at DF.DeepFreezer.OnVesselChange (.Vessel vessel) [0x00000] in <filename unknown>:0 at EventData`1[Vessel].Fire (.Vessel data) [0x00000] in <filename unknown>:0 [EXC 19:56:47.532] NullReferenceException DF.DeepFreezer.OnVesselChange (.Vessel vessel) EventData`1[Vessel].Fire (.Vessel data) UnityEngine.Debug:LogException(Exception) EventData`1:Fire(Vessel) FlightGlobals:setActiveVessel(Vessel, Boolean) FlightGlobals:SetActiveVessel(Vessel) FlightDriver:Start() [LOG 19:56:47.532] DeepFreezer OnVesselChange onvslchgInternal False activevessel baeb85bc-464a-40a5-9b5a-358f2e860436 parametervesselid baeb85bc-464a-40a5-9b5a-358f2e860436 this vesselid 570dac36-4111-48d0-97b0-e94b514671d9 this partid 988057946 [ERR 19:56:47.532] Exception handling event onVesselChange in class DeepFreezer:System.NullReferenceException: at (wrapper managed-to-native) UnityEngine.AudioSource:get_isPlaying () at DF.DeepFreezer.OnVesselChange (.Vessel vessel) [0x00000] in <filename unknown>:0 at EventData`1[Vessel].Fire (.Vessel data) [0x00000] in <filename unknown>:0 [EXC 19:56:47.532] NullReferenceException DF.DeepFreezer.OnVesselChange (.Vessel vessel) EventData`1[Vessel].Fire (.Vessel data) UnityEngine.Debug:LogException(Exception) EventData`1:Fire(Vessel) FlightGlobals:setActiveVessel(Vessel, Boolean) FlightGlobals:SetActiveVessel(Vessel) FlightDriver:Start() Not sure if they are related to the TACLS dependency. I'm using USILS so TACLS isn't installed. If I install it, will there be any conflicts with USILS?

Having a problem with the two sqaure headshields. They don't get drawn in the VAB when I select them. I can see the attach nodes though and if I attach them to my ship save, start a new ship and then load the old one, I can see the heatshield, but it's huge. I have tweakscale installed and it works fine with the hangars and all other parts, but if I try and change th size of the heatshields nothing happens. If I try and detach them, they disappear again. The logs seem to indicate something wrong with the geometry so I think what I'm seeing is not an accurate reflection of the parts actual state, but a drawing issue. [LOG 20:05:19.476] at AT_Utils.PartModuleExtensions.Log(.PartModule pm, System.String msg, System.Object[] args) at AT_Utils.AnisotropicPartResizer.Update() [LOG 20:05:19.476] [001_AnisotropicPartResizer: 20:05:19.476] _vessel:Heatshield for the Rover Lander Hangar[F8C7FCBC]:AnisotropicPartResizer[E10F4E00]: Model local scale changed [LOG 20:05:19.480] Autogen thumbnail for /Users/svc/Library/Application Support/Steam/steamapps/common/Kerbal Space Program/KSP.app/Contents/../../thumbs/Daddy_VAB_Rover Hangar.png from /Users/svc/Library/Application Support/Steam/steamapps/common/Kerbal Space Program/saves/Daddy/Ships/VAB/Rover Hangar.craft [WRN 20:05:19.504] BoxColliders does not support negative scale or size. The effective box size has been forced positive and is likely to give unexpected collision geometry. If you absolutely need to use negative scaling you can use the convex MeshCollider. Scene hierarchy path "RoverLanderHangar/SquareHeatshield/model/Hangar/Parts/Models/SquareHeatshield(Clone)/heatshield/collider/collider-wall_001" [WRN 20:05:19.504] BoxColliders does not support negative scale or size. The effective box size has been forced positive and is likely to give unexpected collision geometry. If you absolutely need to use negative scaling you can use the convex MeshCollider. Scene hierarchy path "RoverLanderHangar/SquareHeatshield/model/Hangar/Parts/Models/SquareHeatshield(Clone)/heatshield/collider/collider-wall_002" [WRN 20:05:19.504] BoxColliders does not support negative scale or size. The effective box size has been forced positive and is likely to give unexpected collision geometry. If you absolutely need to use negative scaling you can use the convex MeshCollider. Scene hierarchy path "RoverLanderHangar/SquareHeatshield/model/Hangar/Parts/Models/SquareHeatshield(Clone)/heatshield/collider/collider-wall_003" [WRN 20:05:19.504] BoxColliders does not support negative scale or size. The effective box size has been forced positive and is likely to give unexpected collision geometry. If you absolutely need to use negative scaling you can use the convex MeshCollider. Scene hierarchy path "RoverLanderHangar/SquareHeatshield/model/Hangar/Parts/Models/SquareHeatshield(Clone)/heatshield/collider/collider-wall_005" [LOG 20:05:19.672] [FAR v0.15.11.1] Voxel Element CrossSection Area: 0.00410273030977838 [LOG 20:05:19.738] [FAR v0.15.11.1] Std dev for smoothing: 3 voxel total vol: 65.6975937696505 filled vol: 66.6067298482193 [LOG 20:05:19.787] [FAR v0.15.11.1] Voxelization Time (ms): 329 [LOG 20:05:21.054] [FAR v0.15.11.1] Updating Rover Hangar [LOG 20:05:21.189] [FAR v0.15.11.1] Voxel Element CrossSection Area: 0.0128702505378598 [LOG 20:05:21.222] [FAR v0.15.11.1] Std dev for smoothing: 3 voxel total vol: 365.023235593196 filled vol: 172.404906994867 [LOG 20:05:21.254] [FAR v0.15.11.1] Voxelization Time (ms): 200 [LOG 20:05:32.486] [FAR v0.15.11.1] Updating Rover Hangar [LOG 20:05:32.553] [FAR v0.15.11.1] Updating Rover Hangar [LOG 20:05:32.688] [FAR v0.15.11.1] Voxel Element CrossSection Area: 0.0128702505378598 [LOG 20:05:32.721] [FAR v0.15.11.1] Std dev for smoothing: 3 voxel total vol: 365.023235593196 filled vol: 172.404906994867 [LOG 20:05:32.753] [FAR v0.15.11.1] Voxelization Time (ms): 200 [LOG 20:05:34.170] [FAR v0.15.11.1] Updating Rover Hangar [LOG 20:05:34.304] [FAR v0.15.11.1] Voxel Element CrossSection Area: 0.0128702505378598 [LOG 20:05:34.338] [FAR v0.15.11.1] Std dev for smoothing: 3 voxel total vol: 365.023235593196 filled vol: 172.404906994867 [LOG 20:05:34.370] [FAR v0.15.11.1] Voxelization Time (ms): 200 [LOG 20:05:35.903] [FAR v0.15.11.1] Updating Rover Hangar [LOG 20:05:36.038] [FAR v0.15.11.1] Voxel Element CrossSection Area: 0.0128702505378598 [LOG 20:05:36.072] [FAR v0.15.11.1] Std dev for smoothing: 3 voxel total vol: 365.023235593196 filled vol: 172.404906994867 [LOG 20:05:36.103] [FAR v0.15.11.1] Voxelization Time (ms): 199 [LOG 20:06:28.642] at AT_Utils.Metric.partsBounds(IList`1 parts, UnityEngine.Transform refT, Boolean compute_hull, Boolean exclude_disabled) at AT_Utils.Metric..ctor(IShipconstruct vessel, Boolean compute_hull, Boolean world_space) at GroundConstruction.VesselKit..ctor(.PartModule host, .ShipConstruct ship, Boolean assembled, Boolean simulate) at GroundConstruction.GCEditorGUI.Update() [LOG 20:06:28.643] [000_AT_Utils: 20:06:28.643] Metric.partsBounds: WARNING! No parts were provided. [LOG 20:06:28.644] at AT_Utils.Metric.partsBounds(IList`1 parts, UnityEngine.Transform refT, Boolean compute_hull, Boolean exclude_disabled) at AT_Utils.Metric..ctor(IShipconstruct vessel, Boolean compute_hull, Boolean world_space) at GroundConstruction.VesselKit..ctor(.PartModule host, .ShipConstruct ship, Boolean assembled, Boolean simulate) at GroundConstruction.GCEditorGUI.Update() [LOG 20:06:28.644] [000_AT_Utils: 20:06:28.644] Metric.partsBounds: WARNING! No parts were provided. [ERR 20:06:32.146] Cannot find fx group of that name for decoupler [ERR 20:06:32.422] Module AnisotropicPartResizer threw during OnStart: System.NullReferenceException: Object reference not set to an instance of an object at AT_Utils.JettisonUpdater.SaveDefaults () [0x00000] in <filename unknown>:0 at AT_Utils.AnisotropicPartResizer.create_updaters () [0x00000] in <filename unknown>:0 at AT_Utils.AnisotropicPartResizer.SaveDefaults () [0x00000] in <filename unknown>:0 at AT_Utils.PartUpdaterBase.OnStart (StartState state) [0x00000] in <filename unknown>:0 at AT_Utils.AnisotropicResizableBase.OnStart (StartState state) [0x00000] in <filename unknown>:0 at AT_Utils.AnisotropicPartResizer.OnStart (StartState state) [0x00000] in <filename unknown>:0 at Part.ModulesOnStart () [0x00000] in <filename unknown>:0 Using KSP 1.7.3, Using a pre-release of AT_Utils 1.8.2 (to resolve an issue wiht GroundConstruction) and Hangar 3.4.0 (pre-release downloaded at same time as other pre-release modules). AT_Utils-Debug log: [001_AnisotropicPartResizer: 20:04:09.295] _vessel:Heatshield for the Inflatable Ground Hangars[C4D5CEB2]:AnisotropicPartResizer[67938F80]: Model local scale changed [001_AnisotropicPartResizer: 20:04:11.143] _vessel:Heatshield for the Rover Lander Hangar[AD4B08E3]:AnisotropicPartResizer[D110F80]: Model local scale changed [001_AnisotropicPartResizer: 20:04:17.562] _vessel:Heatshield for the Rover Lander Hangar[8E454D23]:AnisotropicPartResizer[5D678300]: Model local scale changed [000_AT_Utils: 20:04:34.987] Metric.partsBounds: WARNING! No parts were provided. [000_AT_Utils: 20:04:34.987] Metric.partsBounds: WARNING! No parts were provided. [001_AnisotropicPartResizer: 20:04:47.160] _vessel:Heatshield for the Rover Lander Hangar[1441F0C2]:AnisotropicPartResizer[977F4180]: Model local scale changed [001_AnisotropicPartResizer: 20:04:59.093] _vessel:Heatshield for the Rover Lander Hangar[9BE18097]:AnisotropicPartResizer[648C0000]: Model local scale changed [000_AT_Utils: 20:05:12.237] Metric.partsBounds: WARNING! No parts were provided. [000_AT_Utils: 20:05:12.238] Metric.partsBounds: WARNING! No parts were provided. [001_AnisotropicPartResizer: 20:05:19.476] _vessel:Heatshield for the Rover Lander Hangar[F8C7FCBC]:AnisotropicPartResizer[E10F4E00]: Model local scale changed [000_AT_Utils: 20:06:28.643] Metric.partsBounds: WARNING! No parts were provided. [000_AT_Utils: 20:06:28.644] Metric.partsBounds: WARNING! No parts were provided. [001_AnisotropicPartResizer: 20:06:32.510] _vessel:Heatshield for the Rover Lander Hangar[7693B0FB]:AnisotropicPartResizer[C6CB7380]: Model local scale changed [000_AT_Utils: 20:06:38.156] Metric.partsBounds: WARNING! No parts were provided. [000_AT_Utils: 20:06:38.156] Metric.partsBounds: WARNING! No parts were provided. [001_AnisotropicPartResizer: 20:06:41.174] _vessel:Heatshield for the Inflatable Ground Hangars[69672FD0]:AnisotropicPartResizer[CD90300]: Model local scale changed Any Ideas?

Found the cause of my new issue. I paused the assembly line before the kit was completed and tried numerous things and then resumed only to have it freeze. One thing worked. I stopped the assembly line so that the kit moved back to the queue. But there was already one of the same thing in the queue. It seemed like when I started filling the empty kit with my vessel, it didn't move the vessel out of the queue. The double up caused the completion process to crash the whole game. Once stopped, both instances appeared in the queue side by side. I deleted one (red x icon) and restarted the remaining one and it completed successfully. No idea on exactly when this second instance appeared or what I did to get it there.

My issue could be impacted by this. I've been able to consistently build empty kits, but anytime I put anything in a kit, it explodes on spawn. I wonder if the mass of the kit could affect things. My assembly line isn't perfectly level. Mun has a slight slope (about 0.5%) at my base site. Not sure how I can get this to be perfectly horizontal. I've got a new issue I'm trying to figure out with the whole game freezing when a kit is about to be finalized. I built an empty kit and moved it into position. And whenever the assembly line finishes it's work on the kit the whole game freezes. Nothing in the logs at all. I'm going to try latest build from mega tonight to see if the previous beta build I was using is causing it.

Still having the same problem with your latest nightly build and 1.7.3. Explosion upon clicking Finalize in the assembly line. I was able to get an empty container to come out one time, but every other time they explode too. The module is connected to my main base for resource supply by KAS pipe in docked config. Is there anything else I can give you to help understand what is happening here? I'm at a complete loss on how I can proceed with this mod for a Duna base if I have to fly a kit for every single thing I may need to build all the way from Kerbin.

I'm on a Mac. For the refrence of others, the path is ~/Library/Logs/Unity/Player.log https://www.dropbox.com/s/upjmkhlzkrj9h32/Player.log?dl=0 I had a quick read and there's no extra messages other than what's seen in the ksp log. At least in the part I'm looking at. Hopefully you can find something useful. I've tried removing FAR and dependencies with no change. It could be another plugin causing a conflict but I'm hoping we could find something useful to narrow down that search a little.

Upgraded to ksp 1.7.2 and GC 2.4.1. Just built my first assembly line on the Mun but every kit explodes on spawn. Even an empty container. Looks like ksp sees the kit as crashing into Mun. I build the assembly line from a kit that was flown to the Mun. Not sure if that has anything to do with it. [LOG 21:20:59.229] [DIY Kit: Flex]: Ready to Launch - waiting to start physics... [LOG 21:20:59.229] 6/26/2019 9:20:59 PM,AmpYear,OnVesselCreate [LOG 21:20:59.235] [000_AT_Utils: 21:20:59.235] Vessel assembled for launch: DIY Kit: Flex [LOG 21:20:59.319] [Dynamic Battery Storage]: Summary: vessel DIYKit (loaded state True) - 0 stock power handlers [LOG 21:20:59.537] [FlightIntegrator]: Reloaded drag cube for zeroed cube root part DIYKit on vessel DIY Kit: Flex [LOG 21:20:59.538] [FlightIntegrator]: Vessel DIY Kit: Flex has been unloaded 1.79769313486232E+308, applying analytic temperature 176.292893558036 [LOG 21:20:59.735] [USI-LS] Vessel situation changed, refreshing life support [LOG 21:20:59.736] [USI-LS] Vessel situation changed, refreshing life support [WRN 21:21:00.632] [F: 80515]: Vessel DIY Kit: Flex crashed through terrain on Mun. [LOG 21:21:00.634] DIYKit Exploded!! - blast awesomeness: 0.2 [LOG 21:21:00.636] [DIYKit]: Deactivated Any suggestions on where to start troubleshooting? Anyone else seen this issue?

I checked and those log entries were there on startup. Since you said that SMSettings.dat is created on first run I decided to delete the current one and launch ksp and see if a new one was created. It was and the buttons show up in the toolbar again. There was obviously a problem with the old file. I hadn't tried editing it until after the buttons disappeared so perhaps one of my out of ram crashes damaged the file in someway.

@Papa_Joe Thanks for a great plugin. After the last update I noticed my toolbar button has disappeared. I was using the stock toolbar. I've tried changing the SMSettings.dat file to use Blizzy's toolbar and it doesn't show up there either. I've also tried turning on verbose and debug logging and didn't see any extra entries in the log file. In fact I can't see anything indicating an error. Nothing but loading and similar messages when I filter on the word "manifest". Let me know what else to look for. 4.4.1.0 of ShipManifest and 1.0.4 of KSP. 1.1.3.1 of CLS if it's in anyway related.

@taniwha Thanks for the quick work. Much appreciated.

I had used the re-root functionality when making this vessel in the VAB. Seems like this could be the core of the problem. Great catch. I have a quick save from after the build is completed but before finalize. I made a new model with the same parts but without using the re-root tool. I then used a text editor to copy the content of the craft file into the quick save file, replacing the CraftConfig section on the survey station. Quick load. Finalize. Worked as advertised. The new vessel appeared exactly where the stakes said it should. This is definitely something to do with the new re-root tool. If you have a save from before you finalized the build and you're comfortable doing some basic cut and paste in the save file then you can work around it without doing a rebuild from scratch.

Yes. All stakes are about 15m from the base with the C3 and no more than 40m from the C3 itself. They are all named the same and I can see the site name in the ui as expected. One thing I noticed when I continued testing after my post was that when I click finalize I can some times see the new module appear for a fraction of a second exactly where it's supposed to in the correct orientation. It's only for a frame and many times I don't get to see it at all. The next instant it's on it's side floating 1-2m above the surface on the opposite side of the base. When physics kicks in it drops down and then starts bouncing. Some times it it spawns half way in the ground and then bounces 500m up. So I think EL is placing the model of the new module where the stakes say it should go but then something either EL or something else immediately moves it. I've built many base modules on Mun without any problems using stakes but this is my first one on Minimus. I was running 5.0.2 and just updated to 5.1.0. The behavior is the same for both. Here are the log entries when I build (Base PDU is the vessel I'm building): [WRN 08:37:04.962] [Part]: PartModule FARBasicDragModel at MKS.ModuleBase, index 12: index exceeds module count as defined in cfg. Looking for FARBasicDragModel in other indices... [ERR 08:37:04.962] ...no FARBasicDragModel module found on part definition. Skipping... [LOG 08:37:04.970] [MKS] Awake! [LOG 08:37:04.977] Tac.LifeSupportModule[FFF44D62][710.92]: OnAwake [WRN 08:37:05.021] [Part]: PartModule FARBasicDragModel at MKS.PDU, index 14: index exceeds module count as defined in cfg. Looking for FARBasicDragModel in other indices... [ERR 08:37:05.021] ...no FARBasicDragModel module found on part definition. Skipping... [LOG 08:37:05.022] Base PDU loaded! [LOG 08:37:05.023] [EL] GetVesselBox (-2.1, 13.2, -2.7) (2.3, 18.0, 1.7) [LOG 08:37:05.023] [EL] launchPos (-1.0, -18.2, 1.0) (-0.7, 0.1, 0.1, 0.7) [LOG 08:37:05.025] [base PDU]: Ready to Launch - waiting to start physics... [LOG 08:37:05.054] [FLIGHT GLOBALS]: Switching To Vessel Base PDU ---------------------- [LOG 08:37:05.055] Packing Min Rover for orbit [LOG 08:37:05.055] Packing Min Base for orbit [LOG 08:37:05.068] Packing Tom Kerman Base for orbit [LOG 08:37:05.068] Packing Tom Kerman Base for orbit [LOG 08:37:05.068] Packing Tom Kerman Base for orbit [LOG 08:37:05.068] Packing Billo Kerman for orbit [LOG 08:37:05.071] stage manager resuming... [LOG 08:37:05.090] [iR GUI] vessel MKS.PDU [LOG 08:37:05.090] [iR GUI] 0 groups [LOG 08:37:05.090] Vessel assembly complete! [LOG 08:37:05.090] [EL] hft 2.482963 [LOG 08:37:05.090] stage manager starting... [LOG 08:37:05.093] 3/4/2015 8:37:05 AM,KerbalAlarmClock,Active Vessel changed - resetting inqueue flag [LOG 08:37:05.104] [KSP Interstellar] Radiation Module Loaded. [LOG 08:37:05.105] [REGO] - Error in - BaseConverter_OnStart - Object reference not set to an instance of an object [LOG 08:37:05.105] Tac.LifeSupportModule[FFF44D62][710.92]: OnStart: PreLaunch, Landed [LOG 08:37:05.105] [KSP Interstellar] Radiation Module Loaded. [LOG 08:37:05.127] 3/4/2015 8:37:05 AM,KerbalAlarmClock,Removing DrawGUI from PostRender Queue [LOG 08:37:05.144] Tac.FuelBalanceController[FFF4CEA4][710.92]: Rebuilding resource lists. [LOG 08:37:05.151] [MechJeb2] Focus changed! Forcing Min Base to save [LOG 08:37:05.260] [Min Rover]: ground contact! - error: 0.000m [LOG 08:37:05.260] Unpacking Min Rover [LOG 08:37:05.264] [Min Base]: ground contact! - error: 0.000m [LOG 08:37:05.265] Unpacking Min Base [LOG 08:37:05.316] [Tom Kerman Base]: ground contact! - error: 0.000m [LOG 08:37:05.316] Unpacking Tom Kerman Base [LOG 08:37:05.316] [KAS] OnVesselGoOffRails(Core) Re-attach static object [LOG 08:37:05.316] [KAS] JointToStatic(Base) Create kinematic rigidbody [LOG 08:37:05.316] [KAS] JointToStatic(Base) Create fixed joint on the kinematic rigidbody [LOG 08:37:05.316] [Tom Kerman Base]: ground contact! - error: 0.000m [LOG 08:37:05.316] Unpacking Tom Kerman Base [LOG 08:37:05.316] [KAS] OnVesselGoOffRails(Core) Re-attach static object [LOG 08:37:05.316] [KAS] JointToStatic(Base) Create kinematic rigidbody [LOG 08:37:05.316] [KAS] JointToStatic(Base) Create fixed joint on the kinematic rigidbody [LOG 08:37:05.316] [Tom Kerman Base]: ground contact! - error: 0.000m [LOG 08:37:05.316] Unpacking Tom Kerman Base [LOG 08:37:05.316] [KAS] OnVesselGoOffRails(Core) Re-attach static object [LOG 08:37:05.316] [KAS] JointToStatic(Base) Create kinematic rigidbody [LOG 08:37:05.317] [KAS] JointToStatic(Base) Create fixed joint on the kinematic rigidbody [LOG 08:37:05.317] [billo Kerman]: ground contact! - error: 0.000m [LOG 08:37:05.317] Unpacking Billo Kerman [LOG 08:37:05.327] 3/4/2015 8:37:05 AM,KerbalAlarmClock,Adding DrawGUI to PostRender Queue [LOG 08:37:05.327] 3/4/2015 8:37:05 AM,KerbalAlarmClock,Skipping version check [LOG 08:37:05.343] Tac.FuelBalanceController[FFF4CEA4][710.96]: Rebuilding resource lists. [LOG 08:37:05.475] 3/4/2015 8:37:05 AM,KerbalAlarmClock,Vessel Change from 'Min Base' to 'Base PDU' [LOG 08:37:05.528] Unpacking kerbalEVA (Billo Kerman). Vel: (0.0, 0.0, 0.0) [LOG 08:37:09.217] [base PDU]: ground contact! - error: 0.000m [LOG 08:37:09.217] Unpacking Base PDU

I'm having a similar problem as 5thHorseman. I have 3 stakes set, 2 are origin stakes so that the vessel spawns in between them instead of on top of 1 origin stake. I made that mistake once and saw a vessel bounce around on top of it. The other one is a +X stake to set direction. They are all in direction mode. The vessel spawns on the opposite side of the survey station oriented with +Z pointing in the same direction as the +X stake. I've tried changing the +X stake to +Z and it doesn't change anything. I've tried removing the +X stake, changing the origin stakes to a +/- X and Z and nothing I try changes. The vessel spawns on it's side above the ground and when physics kicks in in drops and then starts bouncing around. I'm on a lake on Minimus so the altitude of everything is exactly 0m. I wonder if that could be causing problems. I'm using MKS parts. The C3 module is the survey station and the vessel in question is an MKS base plus a PDU module. Just 2 parts.