AccidentalDisassembly

Threw a couple easy-to-fix issues up on the github in case you don't receive notifications for it! Some quick fixes with brackets and two duplicate patches that can be removed from squad patches (Control.cfg).

Small note: there's a missing opening curly brace on the second patch (@PART[opt_vtol_jumpa*|opt_vtol_bubble*|opt_vtol_egg|opt_vtol_heli*]:NEEDS[KerbalActuators]) in GameData\OPT_Legacy\Patches\KerbalActuators.cfg, just FYI! EDIT: Additionally, there's a double " or" bar in this patch: @PART[AAengine|turboRamJetj_60d||opt_vtol_lpr1]:NEEDS[RP-0] in GameData\OPT_Reconfig\TechTree\OPT_RP0.cfg.

Hello! Small note about configs - each of the following configs has a mismatched number of curly braces, which appears mostly to be the result of a missing closing brace at the end of the file: Check {} in C:\Games\KSP_win64\GameData\ContractPacks\PWP\Milestones\100.cfg Check {} in C:\Games\KSP_win64\GameData\ContractPacks\PWP\Milestones\2500m.cfg Check {} in C:\Games\KSP_win64\GameData\ContractPacks\PWP\Milestones\AtlasII.cfg Check {} in C:\Games\KSP_win64\GameData\ContractPacks\PWP\Milestones\AtlasIII.cfg Check {} in C:\Games\KSP_win64\GameData\ContractPacks\PWP\Milestones\Gilly

If I remember correctly (you can look it up in the TS configs somewhere), 2x engine dimensions = roughly 4x the thrust but 8x the weight (thrust as a function of nozzle surface area, weight as a function of volume). However, those scaling factors might have changed since the last time I looked...

Hooray, it works! Thanks!

Is this meaningful? Why is there a DLL included with the NF companion, anyway...? Trying to figure out what exactly is preventing me from loading KSP..

I'm not sure I understand the first part of that, was the < in red supposed to be >? If so, yep, that's what I was thinking - I guess another way of conceiving of the "increase hyper warp by Y" would be to allow the user to define a list rather than one specific increment: Like with better time warp continued (I think), the user could define the specific multipliers for slow-motion and hyperwarp that are chosen/switched to when pressing the < and > keys. For instance, a user might want very fine control over warp between 0.5x and 1x, but only one jump from 0.1x to 0.5x:

I don't think you can have two things in FOR[], but I'm not sure about that... Secondly, be very careful with :FOR - if you use it, it tells ModuleManager that those things are installed! My understanding is that you should never use FOR unless there is a very good reason to do so.

Ah! Looked in the config. I think maybe it's just because that one part doesn't have a "tags= ...." entry in the config, that's all.

I didn't even know you could do that with MM! Interesting. Glad I got in the ballpark of the problem at least. One small note about the most recent version, just noticed as I was taking it for a spin (loads fine!) - one cockpit is not successfully captured by the category:

@JadeOfMaar --- With the new OPT Reconfig, KSP also hangs while loading for me - on part h_2m_em_fm. While looking through the patches to figure out what was going on, I notice one instance of empty OR pipes in a module manager patch ("||") that may or may not cause problems.: MainUtilities.cfg, line 146. Or not, I don't know. However, the real issue is with OPT_CCTanks.cfg. Two things: It applies a CC patch to h_2m_em_fm (and other parts) even if the user hasn't installed CC but has installed any other AT mod, because ConfigurableContainers DLL is packaged with AT_Utils, unfortunat

Okie doke! Two small things I noticed in the APP Companion so far: There's an empty plugins directory - not really a big deal. In AirplanePlus_Utility_TweakScale.cfg, three parts are engines - they could be moved to the engines config, and they might need the "#@TWEAKSCALEBEHAVIOR[Engine]/MODULE[TweakScale] { }" : S1APU S1p5APU S2APU That's all I've seen so far!

In case someone hasn't reported it - the J Edgar VTOL engine is missing a node in one of its variants. The following SUBTYPE needs the green bit to be added: SUBTYPE { name = #LOC_M2X_JedgarF transform = Engine_base transform = Fairing transform = Pivot node = bottom node = top addedMass = 0.25 } EDIT: Also, I think the Fairing transform needs to go to the variant above it... Possibly. No fairing appears when attaching a part to the engine using the variant wit

Small suggestion for the next version - in Zs_ProbesBeforeCrew.cfg, the patch that creates the telemetry experiment applies it only to un-crewed parts. However, contracts generate requests for that experiment for all sorts of situations, including things like "send a scientist here and perform telemetryReport". It stands to reason that a crewed capsule should be able to send telemetry too, no need for an additional probe core on the vessel. So: @PART[*]:HAS[@MODULE[ModuleCommand],#vesselType[Probe]]:NEEDS[CommunityTechTree] <-- Deleting that would be a convenience! { MODUL

Hi @Lisias - I'll take a look at the APP tweakscale when I get a chance I am having a strange behavior with the combination of TweakScale and Stage Recovery. From memory, I am reasonably certain this can be reproduced with only TS and SR installed (and KSP recall and whatnot, on 1.9.1), but I have not verified that. I should say: I don't know whether this has anything to do with TweakScale, so... sorry if it's a Stage Recovery thing instead. Here's what happens: Using symmetry, place a non-scaled parachute on a part (like a booster nose, in the image below). Stage Recover