Aelfhe1m

@captinjoehenry The problem is the line: If you change it to: then it should work with any planet pack although some of the offered contracts may have maxAltitudes that are too low to be completed if there are bodies similar to Gilly that have surface features that extend above the "in space low" threshold.

The problem is the line: If you change it to: then it should work with any planet pack although some of the offered contracts may have maxAltitudes that are too low to be completed if there are bodies similar to Gilly that have surface features that extend above the "in space low" threshold.

@Krakatoa, @SpacedInvader Other mods with alternative shipyard models include: Spacedock (not to be confused with the website of the same name ) and Keridian Dynamics

@bornity I'm unable to replicate that using KSP 1.3.0 and the versions of KF and RS in your image. Can you please post links to your logs and the craft file for that rover? (How to get support)

@SpacedInvader Try updating USI Tools - the version bundled in the current Konstruction zip is slightly out of date and had an issue relating to custom categories.

Above a certain threshold (the PermaHabTime) a vessel/base/station's habitation time becomes "indefinite". Scouts and Pilots have a trait (ExplorerSkill) that allows them to reach this "indefinite" habitation time more quickly (the ScoutHabTime).

In that log the crash is actually happening with KAX: Are you using SpannerMonkey's 1.3.1 beta version?

The syntax is @PART[part1|part2|part3] using the vertical bar symbol to mean "OR" Yes multiple wildcards are allowed. MM is case sensitive so "decal" and "Decal" are two different values (but "*ecal" or "?ecal" will match either). ? matches a single character and * multiple characters. The @PART[X] syntax matches against the internal part names (i.e. the name = X line in the config). If you want to match against one of the other lines then you can use @PART[*]:HAS[#key[value]] to look for parts with a key = value line. NOTE: the #key filter does not work with | for OR searches but will work with wildcards.

Did you install the SSTU-OptionalPatches folder from GitHub? That has several incomplete (WIP) patches in it, some of which try to replace multiple individual parts with a single SSTU style switchable part. The files with "PartRemoval" in their name are responsible for hiding the "replaced" parts. Deleting those files will restore the original parts to your game.

Ah, but that icon comes from a third party mod so it's not canon...

@Marrv Part search only searches the stock categories. Any part that is only in a custom category will not show up in any search.

player.log (linux/OSX) = output_log.txt (Windows)

No Standard won't work either. It needs to be "Class Library (.NET Framework)".

Did you make sure you chose the project type "Class Library (.NET Framework)". If you did then your project properties page should include a target framework drop down with 3.5 selected

KSP plugins should be built against .NET Framework 3.5

Just posted an edit to my last post after I noticed that myself.

Well that shows that "some" patch is being applied at the right time: The log isn't very helpful for diagnosing MM problems (unless there's an actual patch error reported or you're trying to find conflicting patches, which is not the case here). Try posting a link to your ModuleManager.ConfigCache file - it will show what the modified part configs look like after patching. EDIT: downloaded EVA handrails continued to test myself. The problem is that the original parts don't have any tags. You can change the patch to work with either modifying a n existing tag or adding a whole new tag set:

@flart The main problem is the @tags line. When using ^= the trailing part needs three :s. One at the beginning, one to separate search from replace and one at the end. In most cases when adding a tag you want to stick it on the end, so: @tags ^= :$: extratag: Also note the space in the middle to separate the new tag from the existing ones. You can also merge the :NEEDS into a single statement :NEEDS[CommunityCategoryKit,KIS,NEBULA] and since the order of patch execution during the :BEFORE :FOR :AFTER phase is alphabetical you only need one :AFTER with the highest value (alphabetically). Putting it all together:

Personally, I'm not seeing that problem. My current save (and several past saves) has KEI and DMOS (and several other science mods) and they play fine together.

KSPTOT is a stand alone program for planning more complex missions. It has a bit of a steep learning curve but is well worth it. It does have a plug-in component for transferring data between KSP and the tool but it is very low impact and the tool can mostly be used without it - you'll just need to create the initial bodies ini file since this isn't the stock KSP system.

@Fomalhaut I only gave the log a quick scan so may have missed something: You've got multiple copies of ModuleManager installed. Remove all but the latest. KSPUtil was removed several versions ago (1.2?). This error appears to be associated with IRSurfaceSampler in your case. The actual crash is occurring during GameParameters:Save. That's indicative of having a 1.3.1 mod installed on 1.3.0 (or vice versa) that uses the built in settings screens. You seem to have USI Tools v. 0.10 installed but 0.9.3 was the last 1.3 version

@magico13 I've been using KCT #38 for about a week now in KSP 1.3.1 and have upgraded to #39 today and played a couple of hours so far - I've not seen any problems with either build (x64 windows with ~120 mods)

Upload your image to an image sharing website (Imgur is popular but pretty much anywhere will work) and then paste the URL of the uploaded image into the forum.

@Gibster That sounds like you're having a problem with the copy of B9PartSwitch you have installed - either a mismatch between the mod version and KSP version or a mis-install. NFC 0.8.4 is working fine for me with KSP 1.3.1 and B9PartSwitch 1.10.0. Post a link to a copy of your log files and someone here might be able to find the problem ("How to get support" thread)

Rovers, life support and containers categories come from CommunityCategoryKit. Kolonization, Construction, Logistics and Manufacturing come from USI_Tools. Post a link to a copy of your log files and someone here might be able to find the problem ("How to get support" thread)