Aigamuxa

Hiya -- I've run into some errors that seem to be related to the Research Bodies telescope. Not sure what if anything they affect but I thought I would report it all the same: From ModuleManager.log: [...] [LOG 20:51:06.162] Applying update DE_IVAExtension/Parts/@PART:HAS[#DE_IVA_internalName]:FOR[DE_IVAExtension] to REPOSoftTech/ResearchBodies/Parts/telescope/telescope.cfg/PART[TrackBodiesTelescope] [WRN 20:51:06.163] Cannot find key manufacturer in PART [ERR 20:51:06.163] Error - Cannot parse variable search when replacing (%) key storedStrings = #v1.1.0||$/title$|||||$/manufacturer$ [...] [LOG 20:51:06.171] Applying update DE_IVAExtension/Parts/@PART:HAS[#DE_IVA_internalName]:FOR[DE_IVAExtension] to REPOSoftTech/ResearchBodies/Parts/telescope/telescope.cfg/PART[TrackBodiesTelescope] [WRN 20:51:06.171] Cannot find key storedStrings in MODULE [ERR 20:51:06.171] Error - Cannot parse variable search when inserting new key DE_IVA_storedStrings = #$MODULE[RasterPropMonitorComputer]/storedStrings$ [...] [WRN 20:51:09.077] Errors in patch prevents the creation of the cache [LOG 20:51:10.049] ModuleManager: 3933 patches applied, found <color=orange>2 errors</color> 2 errors related to GameData/DE_IVAExtension/Parts.cfg Let me know if I can be of any assistance resolving this, but no pressure. It looks like a pretty niche issue to be sure.

You don't need to hold shift, it is a toggle

AP and PE aren't numerically shown when editing a maneuver node. Maddening

1. "Select Root" tool in VAB gets stuck on. Had to exit VAB and re-enter to clear it. 2. Lost control of Kerbal after planting flag on Mun (movement keys non-responsive). Quicksave/Quickload fixed it. 3. "F" to grab and "B" to board are not working. Currently trying to figure out how to work around it before Jeb's air runs out... (edit: restarting the game fixed it) Not sure if it is a bug, missing feature, or intentional (or I just can't find it) but there doesn't seem to be a way to see the delta-V of each stage in the VAB.

Alrighty, I got Unity 2019.4.18f1 installed, started a new empty project, and imported the PartTools package (from PartTools_AssetBundles_2019.4.18f1.zip). But I'm getting the error message "Unloading broken assembly Assets/Plugins/KSP Assets/KSPAssetCompiler.dll, this assembly can cause crashes in the runtime" How can this be resolved? Thanks again.

Nope, just trying my hand at making a very simple part. I just assumed some script somewhere would break if that component wasn't present, but if it's not necessary I'll try to proceed without it.

Right now I'm just sussing it out to see what all is involved, so let's assume I'm developing for 1.12. Which would mean Unity 2019.4.18f1 & TextMesh Pro Release 1.0.56 - Unity 2017.3, per the PartTools post. So it looks like I just need the missing TextMesh Pro package.

Hiya, Trying my hand at some very basic add-on development. I'm following through Tutorial:Making an asset from start to finish and I'm running into a problem with some broken links. I get to "Step 5 - Setting up Unity -> Download PartTools here. " but the link doesn't work. Searching for an alternative source takes me to the PartTools forum post. But A - the post says that Unity 2019.4.18f1 is the correct one to use (contrary to the tutorial, which indicates 4.2.2). And B - the PartTools post says I need a specific version of TextMesh Pro, but the link it provides is broken and I can't find another source for it. Is there a more up to date tutorial or source that lists the correct versions of these tools that should be used? If this is current information, is there a source for the version of TextMesh Pro I need? Thanks.

Hi there. New to the forums, and I thought I would give y'all a heads-up about an issue I've been having with KCT. Caveat: I haven't tested this extensively, and I don't have any tasty logs for you (though I could use some guidance on which ones to include in the future, and where to find them). But what I do have is a solution, in case anyone runs into the same issue. I'm running a fairly huge (for me) modpack, so naturally I get crashes from time to time. But occasionally, I find that KCT stops working when I restart the game after a hard-lock crash. The icon just doesn't show up in the toolbar. I found that it works in new saves, though, so I checked the KCT_Settings.cfg file in the bad save folder -- lo and behold, it was empty. So I copied over KCT_Settings.cfg from the new save (with the settings I want) to the bad save and voila! It works again. Despite my lack of rigor in tracking down the cause, I still feel like this information could be of some use to someone. edit: I'm on KSP 1.11.1.3066 and using KCT 1.4.9 from CKAN. I can at least tell you that much.