Bluebottle

No, I didn't. The weldment config file was written with those empty mesh/collider lists in it, and empty lists seem to cause the exception: all mesh switching stops when an empty list is encountered. That's why I was getting the Z-fighting from the B9 parts - all meshes were being used, rather than the right ones being selected by WeldedMeshSwitch. As for why stock Squad parts would cause empty lists to be written to a weldment file, I don't know. Here are all the times that Mk3-Size2Slant occurs in my log file: $ grep Mk3-Size2Slant KSP.log [LOG 20:38:16.198] Load(Model): Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant [LOG 20:38:48.247] Config(@PART[adapterMk3-Size2Slant]:FOR[SETIrebalance]) SETIrebalance/MM-PartModding/SETI-PartMod-SQUAD-FuelTanks/@PART[adapterMk3-Size2Slant]:FOR[SETIrebalance] [LOG 20:38:48.256] Config(PART) Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant/adapterMk3-Size2Slant [LOG 20:38:48.274] Config(@PART[adapterMk3-Size2Slant]) TweakScale/patches/Squad/Squad_Tanks/@PART[adapterMk3-Size2Slant] [LOG 20:38:55.497] [ModuleManager] Applying node Diazo/AGExt/part/@PART[*] to Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant/adapterMk3-Size2Slant [LOG 20:38:55.804] [ModuleManager] Applying node Diazo/ModActions/part/@PART[*] to Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant/adapterMk3-Size2Slant [LOG 20:39:38.448] [ModuleManager] Applying node TweakScale/patches/Squad/Squad_Tanks/@PART[adapterMk3-Size2Slant] to Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant/adapterMk3-Size2Slant [LOG 20:39:59.548] [ModuleManager] Applying node HotSpot/Patches/HotSpotModule/@PART:FOR[HotSpot] to Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant/adapterMk3-Size2Slant [LOG 20:40:21.889] [ModuleManager] Applying node SETIrebalance/MM-PartModding/SETI-PartMod-SQUAD-FuelTanks/@PART[adapterMk3-Size2Slant]:FOR[SETIrebalance] to Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant/adapterMk3-Size2Slant [LOG 20:40:36.626] [ModuleManager] Applying node CryoTanks/Patches/CryoTanksFuelTankSwitcher/@PART[*]:HAS[@RESOURCE[LiquidFuel],@RESOURCE[Oxidizer],!MODULE[ModuleCryoTank],!MODULE[InterstellarFuelSwitch],!MODULE[ModuleEnginesFX],!MODULE[ModuleEngines],!MODULE[FSfuelSwitch],!MODULE[WBIResourceSwitcher]]:FOR[zzz_CryoTanks] to Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant/adapterMk3-Size2Slant [LOG 20:40:38.998] [ModuleManager] Applying node VenStockRevamp/PathPatches/Aero-PathPatches/@PART[*]:FOR[zzzVSRPathPatch] to Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant/adapterMk3-Size2Slant [LOG 20:40:41.701] [ModuleManager] Applying node VenStockRevamp/PathPatches/Command-PathPatches/@PART[*]:FOR[zzzVSRPathPatch] to Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant/adapterMk3-Size2Slant [LOG 20:40:44.442] [ModuleManager] Applying node VenStockRevamp/PathPatches/Electrical-PathPatches/@PART[*]:FOR[zzzVSRPathPatch] to Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant/adapterMk3-Size2Slant [LOG 20:40:48.323] [ModuleManager] Applying node VenStockRevamp/PathPatches/Engines-PathPatches/@PART[*]:FOR[zzzVSRPathPatch] to Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant/adapterMk3-Size2Slant [LOG 20:40:53.029] [ModuleManager] Applying node VenStockRevamp/PathPatches/FuelTanks-PathPatches/@PART[*]:FOR[zzzVSRPathPatch] to Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant/adapterMk3-Size2Slant [LOG 20:40:57.063] [ModuleManager] Applying node VenStockRevamp/PathPatches/Structural-PathPatches/@PART[*]:FOR[zzzVSRPathPatch] to Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant/adapterMk3-Size2Slant [LOG 20:41:01.953] [ModuleManager] Applying node VenStockRevamp/PathPatches/Utility-PathPatches/@PART[*]:FOR[zzzVSRPathPatch] to Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant/adapterMk3-Size2Slant [LOG 20:41:07.197] [ModuleManager] Applying node B9PartSwitch/PartInfo/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]]:FOR[zzzzzz-B9PartSwitch] to Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant/adapterMk3-Size2Slant [LOG 20:41:08.850] [ModuleManager] Applying node Diazo/ModActions/part/@PART[*]:Final to Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant/adapterMk3-Size2Slant [LOG 20:41:10.136] [ModuleManager] Applying node SETIrebalance/SETI-GeneralSettings/@PART[*]:HAS[#category[FuelTank]|#category[Propulsion]]:FINAL to Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant/adapterMk3-Size2Slant [LOG 20:43:25.217] PartLoader: Compiling Part 'Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant/adapterMk3-Size2Slant' [LOG 20:43:25.235] PartLoader: Part 'Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant/adapterMk3-Size2Slant' has no database record. Creating. [LOG 20:43:25.240] DragCubeSystem: Creating drag cubes for part 'adapterMk3-Size2Slant' None of those hits cause any errors, and the only warning is this, although I get this for many parts: [LOG 20:43:25.217] PartLoader: Compiling Part 'Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant/adapterMk3-Size2Slant' [WRN 20:43:25.220] PartLoader Warning: Variable LF not found in Part [WRN 20:43:25.220] PartLoader Warning: Variable OX not found in Part [WRN 20:43:25.220] PartLoader Warning: Variable totalCap not found in Part [WRN 20:43:25.220] PartLoader Warning: Variable massOffset not found in Part [WRN 20:43:25.220] PartLoader Warning: Variable costOffset not found in Part I have B9 Part Switch 1.7.1. Ubio Welding is 2.5.0, of course.

Hi Nertea, just reporting a long-standing but minor issue I encounter with the Mark IV crew cabin (the 12-kerbal one). The top airlock (Airlock1 collider) is always "obstructed", despite there being no other part near the collider. This happens even with a one-part vessel. The bottom airlock, Airlock4, has the same problem. So when I built the Iris, which has both ends of the crew cabin blocked with other modules, kerbals in there can only EVA by transferring to other parts. Screen: Other than that, Mark IV works brilliantly. Beauty shot: Edit: the airlock can be used for entry, just not exiting the part.

Hi again Alewx. I've seen another unityException when loading a welded part in the editor: Could it be due to the cloning (via symmetry) of some parts? I notice that the previous part was a B9 part that gives me mesh problems - you know, the normal Z-fighting when all its meshes are loaded. I'm currently experimenting with adding more mesh selection to the WeldedMeshSwitch section of the part config. I love WeldedMeshSwitch - with so many parts using multiple meshes these days, it's vital! Edit: I've found what it was. Welding these parts: Squad/Parts/FuelTank/adapterTanks/Mk3-Size2Slant Squad/Parts/FuelTank/mk2FuselageLong/FuselageLongLFO added empty mesh/collider lists into the WeldedMeshSwitch configuration. So It looked like this: objectIndicies = 0; 16; 17; 19; 20; 21; 23; 25; 27; 28; 29; 31; 33; 34 objects = Basic,Collider01,Collider02,Collider03,FuselageShortLFO,Point001,Sky001,TankLFO; Basic,CargoDoor001,CargoDoor002,CargoExternal,CargoInternal,Collider01,Collider02,ColliderFloor,ColliderFloor002,ColliderFloor003,Piston01Lower,Piston02Lower,Sky001,TankLFO; LFO_10m,Mk3COL; Tail_Lowered; ; StandardWing; ; LFO_10m,Mk3COL; Tail_Lowered; ; StandardWing; ; Basic,Collider01,Collider02,Collider03,FuselageShortLFO,Point001,Sky001,TankLFO; Adapter,Basic,Collider01,Collider1,Collider02,Collider2,Iguana,Sky001,TankRCS Those "; ;" sections were causing the problem. Everything worked after I removed those empty lists, and the corresponding part index from objectIndicies.

That's a 404 now - any chance of getting that file again please?

heh, so I have no idea where I got my Soil vs Dirt story from then. I was sure I'd seen Soil somewhere, many moons ago, despite never installing Snacks...

Hi Angel. It looks like it is impossible to change the Hacienda to be a Cropworks these days. It is wanting to use the Soil resource, but that is missing from the CRP. In the log, I see this immediately after the template for the Cropworks, when I try to reconfigure a Hacienda: CRP no longer has Soil, neither in the original mod, or your bundled one. RD got rid of it in favour of Dirt, IIRC. Pathfinder 1.5.1, KSP 1.2.2, USILS (not Snacks)

Oh, so that's what the dot is for. I thought it was a non-clickable status indicator. As for hiding and re-showing the UI, that didn't fix the problem last night. But I might have a lot of old configuration files to delete, since I have been using TCA for ~18 months. I'll try that.

Looks awesome. I've been searching for something like this (large, flat-sided sections), for Minmus VTOLs, for at least a year!

I love the idea behind the new UI, but, ummm, is it supposed to look like this? KSP v1.2.2, TCA v3.4.0

Hi, I've got a situation where most/all EL parts fail to be compiled by the PartLoader. This isn't the old MKS issue, not at all. Linux x64, v1.2.2. All was well on v1.2.1 I tried to clean that list up a bit - it was the result of a contextual grep. The result is the same both with CKAN and a manual install of EL v5.6.0. A similar issue was here. If it's not an integer requirement, could it be character encoding? I had a great time with KSP 1.0.5, when the loader would CTD if I didn't set my locale to en_US. Edit: I've got some detective work to do. The problem doesn't occur on an otherwise-stock install of v1.2.2. Time to dive deep into my 220+ mods... Edit 2: For completeness, it was caused by an entryCost multiplier section in SETI-rebalance's MM config. The problem affected B9, Near Future Spacecraft, and even a stock part.

Is that change the "all rights reserved" on the assets? I forget what it was in the past.

All the others look fine, at least in the tracking station.

Just another tiny typo report: on case-sensitive filesystems (i.e. Linux/Mac), Moho has no texture and looks like a snowball. In it's Kopernicus config file, the texture name is given as: Material { texture = SVEKopernicus/Moho/PluginData/Moho00.png } but the actual file name is "moho00.png". Note the small "m". Trivial to fix, as I have done myself. Loving the mod otherwise!

Sure, no problem. Here. The log file I posted on page 2 is identical regarding this issue. Thanks! You'll need at least Ven's Stock Revamp, RLA Stockalike, Dmagic's experiments, Procedural Fairings, MRS (full/complete), SPS tanks and Randazzo's Vanguard engine pack to load that. Sorry! Edit: and USI-LS

Thanks, but I already put back the PNGs I made last time and edited the configs. I had no idea that any settings changes would give Unity the necessary kick!

And... yes, there it is. This happened during a simple launch of a vessel with one Mk1 pod and one probe core. I did not touch/supply any PDPN pod names before launch. [EXC 23:56:16.374] ArgumentOutOfRangeException: Cannot be negative. Parameter name: length System.String.Substring (Int32 startIndex, Int32 length) PDPN.PDPN_SelectionWindow.GetFormat (System.String templateName) PDPN.PDPN_SelectionWindow.formatManualEntryName (.PartModule pm2, System.String templateName, Boolean fillSelections, Boolean inFlight, System.String storedTemplateName) PDPN.PersistentDynamicPodNames.FixedUpdate () I got the CTD at ~130km altitude, so about 2 minutes after launch. At least 30 exceptions per second until then, right from within a second of the flight mode scene change. The other PartModuleList.GetEnumerator exception I was getting before was unrelated and not happening any more since I removed an old version of Ship Sounds.

I removed the mod a month ago, simply so I could continue playing, and now that I've added it back again to test, I can't yet provoke the NRE. I'm still on 1.2.1 too. No doubt it'll appear as soon as I post this!

Sorry to report that the problem continues, but all images (normal, color, etc) have to be in PNG format for OpenGL users. KO 0.4.4 still shows no texture for bodies like Potatus, at least for me, on Linux.

Hi, got a problem with Stage Recovery 1.6.5 on KSP 1.2.1: an NRE when debris is destroyed. The result is that this mod effectively does nothing at all - no stages are recovered. Log file: As you can see, my parachutes were activated during staging. I've been using SR for about 1.5 years so I know how to make it work, until now. edit 1: let me try without KK in there... edit 2: Yes, Kerbal Konstructs was stopping SR from working. Any idea which mod is doing something "wrong"?

Excellent! A quick question: do you support using 2.5.0 on KSP 1.2.1?

I can confirm this. As it is now, KO isn't compatible with any OpenGL KSP installation. I'm on Linux and I had to manually convert all DDS images to PNG, and edit the config files because .dds was specified in many of them. After those changes, everything seems fine.

How many stars does your engineer have? If they're a novice and/or too stupid (if stupidity is enabled as a factor in the settings) then "vessel productivity" could be zero, and the build never happens.

I'm just going to leave this note here in case somebody has the same problem I did, which Google has apparently never heard of. I had an old version (from 2015) of ShipEffects still installed on my career game with KSP 1.2.1 and it was producing 10-20 of these every second: MissingMethodException: Method not found: 'PartModuleList.GetEnumerator'. The solution was just to remove/update the old version, of course. The difficulty was nailing down which mod was producing the message.

No problem.Log file and persistent.sfs. Compressed with XZ to save 50MB. My mod list is insane. I wouldn't blame you if you throw up your hands and walk away. CKAN says: Almost everything listed as "incompatible" has updated patches on top, e.g. AIES, or is upgraded manually, e.g. Pathfinder, Buffalo.

Hi LGG. I'm getting a lot of log spam with v0.1.6.1 on KSP v1.2.1 (Linux x64). This eventually causes a CTD (usually about 30-60 seconds after scene load). I am not sure whether the PartModuleList.GetEnumerator message is related to PDPN - been trying to track that one down for over a week now. and it goes on until the CTD.