[1.8.x] UnKerballed Start v1.1.0 (updated Oct 27, 2019)

[SpinkAkron]

8 hours ago, Steven Mading said:

Be aware that thrust plates only exist in the Making History DLC, not the stock game (which is annoying - they are an important base part for exactly this reason - multi-engine mounts are a basic rocketry idea dating back to the early days.)  Without thrust plates, most engines will refuse to surface attach to the bottom of a fuel tank so you can only mount one engine, in the center of the tank, on the attachment node.

The structural parts that fork multi-ways (2-way, 3-way, 4-way adapter) are the only other option I've found without DLC parts, and I don't think they're available at the start in the tech tree.

You can use the small cube structural piece to accomplish the same thing. Attach as many as needed to the bottom of a tank and add the engines to those. Scootch them up to improve appearance. I demoed it in one of my Let's Play videos.

[Dunbaratu]

1 hour ago, SpinkAkron said:

You can use the small cube structural piece to accomplish the same thing. Attach as many as needed to the bottom of a tank and add the engines to those. Scootch them up to improve appearance. I demoed it in one of my Let's Play videos.

That causes drag, and causes a flex point where there should be a rigid flush attachment.  It just really bugs me that people who don't have the DLC are penalized by having to pay the price of extra drag and extra bendiness for a basic construction feature that has nothing to do with the point of the DLC.

[kcs123]

14 hours ago, SpinkAkron said:

The delayed availability of larger engines is intended. Fuel tanks availability is based on volume not radius. Multi-engine stages are encouraged and work great.

 

15 hours ago, SpinkAkron said:

Not changing parts is one my design principles.  I use a mod that nerfs reaction wheels so using RCS on small probes is mandatory.  I reduce the power of RCS thrusters in the build menu to 25% or less and get good results. 

 

10 hours ago, Steven Mading said:

Be aware that thrust plates only exist in the Making History DLC, not the stock game (which is annoying - they are an important base part for exactly this reason - multi-engine mounts are a basic rocketry idea dating back to the early days.)  Without thrust plates, most engines will refuse to surface attach to the bottom of a fuel tank so you can only mount one engine, in the center of the tank, on the attachment node.

The structural parts that fork multi-ways (2-way, 3-way, 4-way adapter) are the only other option I've found without DLC parts, and I don't think they're available at the start in the tech tree.

I understand your idea behind choices you have made. However, there is some gaps that need to be attended for better overall gamebalance.
I have pretty much stummbled upon with lack of some parts that are available only in DLC or covered with oter part pack mod that player for some reason don't have installed (for various reasons: not being supported with current KSP release, conflict with some other mod that player use, or simply don't like some mod etc.).

To test overall gamebalance with this texch tree, I'm using pretty hard difficulty and with minimal mods installed (still tracking what mod can cause issue and what not). Installe dmods in spoiler section:

Spoiler

AT Utils (AT-Utils v1.7.0)
B9 Aerospace Parts Pack (B9 1:v6.5.2)
B9 Aerospace Procedural Wings - Fork (B9-PWings-Fork 1:0.91)
B9 Aerospace Props (B9-props 1:v6.5.2)
B9 Animation Modules (B9AnimationModules v1.5.0)
B9 Part Switch (B9PartSwitch v2.7.1)
ClickThrough Blocker (ClickThroughBlocker 0.1.7.1)
Community Category Kit (CommunityCategoryKit 4.1.0.0)
Community Resource Pack (CommunityResourcePack 1.1.0.0)
Community Tech Tree (CommunityTechTree 1:3.3.7)
Community Trait Icons (CommunityTraitIcons v1.1.1)
Configurable Containers Core (ConfigurableContainers-Core 2.4.5)
Contract Configurator (ContractConfigurator 1.27.1)
Contract Pack: Anomaly Surveyor (ContractConfigurator-AnomalySurveyor 1.7.1)
Contract Pack: Bases and Stations Reborn (ContractConfigurator-KerbinSpaceStation 2:3.7.1.4)
Contract Pack: Clever Sats (ContractConfigurator-CleverSats 1.4)
Contract Pack: Field Research (ContractConfigurator-FieldResearch 1.2.1)
Contract Pack: Giving Aircraft a Purpose (GAP) (GAP 1.6.1)
Contract Pack: Kerbal Academy (ContractConfigurator-KerbalAcademy 1.1.10)
Contract Pack: Tourism Plus (ContractConfigurator-Tourism 1.5.2)
Contract Parser (ContractParser 8.0)
Contracts Window + (ContractsWindowPlus 9.2)
Custom Barn Kit (CustomBarnKit 1.1.19.0)
DMagic Orbital Science (DMagicOrbitalScience 1.4.2)
Ferram Aerospace Research Continued (FerramAerospaceResearchContinued 3:0.15.10.1)
Filter Extensions - Default Configuration (FilterExtensionsDefaultConfig 3.2.2.17)
Filter Extensions - Plugin (FilterExtensions 3.2.2.17)
Final Frontier (FinalFrontier 1.5.3-3465)
Firespitter Core (FirespitterCore v7.12.0)
Firespitter Resources config (FirespitterResourcesConfig v7.12.0)
Global Construction Core (GroundConstruction-Core 2.3.2)
InnerLock (InnerLock 0.0.4_ksp-1.6.1)
Kerbal Alarm Clock (KerbalAlarmClock v3.10.0.0)
Kerbal Attachment System (KAS 1.3)
Kerbal Foundries2 (KerbalFoundriesContinued 2.2.6.16)
Kerbal Inventory System (KIS 1.20)
Kerbal Joint Reinforcement - Next (KerbalJointReinforcementNext v4.0.3)
Konstruction (Konstruction 1.1.0.0)
kOS: Scriptable Autopilot System (kOS 1:1.1.8.0)
KSP Wheel (KSPWheel 15.13.32)
MechJeb 2 (MechJeb2 2.8.3.0)
MechJeb and Engineer for all! (MechJebForAll 1.3.0.5)
ModularFlightIntegrator (ModularFlightIntegrator 1.2.6.0)
Module Manager (ModuleManager 4.0.2)
Portrait Stats (PortraitStats 17.0)
Precise Node (PreciseNode 1.2.10.2)
Progress Parser (ProgressParser 10.0)
RasterPropMonitor Core (RasterPropMonitor-Core 1:v0.30.6)
RCS Build Aid Continued (RCSBuildAidCont 1:0.9.7.6)
RealChute Parachute Systems (RealChute v1.4.7.4)
SCANsat (SCANsat v18.10)
scatterer (Scatterer 2:v0.0540)
scatterer - default config (Scatterer-config 2:v0.0540)
scatterer - sunflare (Scatterer-sunflare 2:v0.0540)
ScienceAlert ReAlerted (ScienceAlert 1.9.6.2)
SmokeScreen - Extended FX Plugin (SmokeScreen 2.8.1.0)
Strategia (Strategia 1.7.3)
Toolbar (Toolbar 1.7.18)
Toolbar Controller (ToolbarController 1:0.1.6.20)
TweakScale - Rescale Everything! (TweakScale v2.4.2.0)
UnKerballed Start (UnKerballedStart 1.0.7)
USI Core (USI-Core 1.1.0.0)
USI Kolonization Systems (MKS/OKS) (UKS 1:1.1.0.0)
USI Life Support (USI-LS 1.1.0.0)
USI Tools (USITools 1.1.0.0)
Waypoint Manager (WaypointManager 2.7.5)
WorldStabilizer (WorldStabilizer 0.9.4-ksp-1.6.1)
KAX (manual install)
IR Next (manual install)

I have ditched out SETI contracts (some of contract packs were causiing spam in logs and this pack may contain obsolete MM commands). That contract pack also mess with Custom barn kit configuration. Starting funds is 10000 and 0 science points. Have to pay entry for each researched part, no additional relay ground stations besides KSC. I also restricting myself only to level 1 buildings, to see how much is feasible to accomplish.

So, I need to establish comm network in orbit with minimum of 6 satelites in equator orbit somewhere between 120 - 160 km and additional 2 in polar orbit with 90 degree longitude orbit difference. Whole craft need to be cheap as possible as I might not be able to have any contract from it as minimum refund. But those are necessary to be able to accomplish any future contracts and grind some scinece points later on.

Since picture tells more than thousens of words - craft example:

So, for latest stage, to be controlable in space I need 8 linear RCS ports with still lacking 4 more to have proper roll control. Those weight too much for such small probe, cuting down upper stage dV a lot. Yemo have solved this issue by adding custom parts in SETI probes mod, previously being integrated with UBM. Sure, I can cut down throttle on those to 25% for better control with kOS, but trough ascent is necessary to have 100% of trust, because boosters don't have any gimbal control and wing surfaces are too heavy.

Instead of solid rocket boosters I can use engine attached to truss and surface attach those to fuel tank. But for 4 engines it is additional 4 more parts that adds to overall part count in VAB/SPH. 40 parts as I suggested might not be enough to counterbalance this issue. And more than 40-50 might be overkill for level one buildings.

Sure, I can use tweakscale to cut down weight of RCS linear ports in half, but I attempt to do test without it, using tweakscale only for IR parts. Just to test overall game balance and get better feel what might be necessary to change. I have only "cheated" a bit trough GAP mod, to get decoupler slightly earlier. Otherwise, might not be possible to even reach space early in game.

There is also missing longer variant of oscar LQ fuel tank, I need to put stack of 3 of them instead of using just one as you have used in your video examples.

I understand your reasons to not change any stock parts. But it might be necessary to add some new ones similar as it is case with LVT-10 engine. I have used MM patch over stock part, but might be better idea to create new part from stock part copy with custom modifications on it. Structural adapters might be also good idea to create 2-4 stack addapters, but for 0.625 size tanks. Just scale down existing stock parts and put it somewhere earlier in tech tree. That would cut down part count from 8 to 5 for same thing.

I would try at first by only adding mentioned additional probe with poor reaction wheels and scaled down 3-4 way adapters. There was some issues with custom RCS ports inYemo's command probes mod between KSP versions, so I would not recommand those as it might be difficult to maintain in future.
Also with ARR licence that mod can also become obsolete, so there is need some other solution for people without DLC packs.

16 hours ago, SpinkAkron said:

I won't have time to work on this for awhile but these are some great ideas for the next version. 

No worries, I was not being able to play KSP for a long time either, not to mention ability to help with mod. Take your time, I will keep posting any other obstacle I found and possible solutions. I understand that you might not be willing to addopt all of them, but I will leave it here for others if they want same changes/solutions that I made.

[kcs123]

@theonegalen, is it possible to remove "FINAL" from this KAX config ?

//Hide Propelators, which asre useless without tiny SXT wings 
@PART[KAXVintagePropelator|KAXVintagePropelatorExtra|KAXVintagePropelatorS|KAXVintagePropelatorSS]:NEEDS[!SXT]:FINAL
{
	@TechRequired = unresearchable
	@category = none
	@TechHidden = true
}

I don't use SXT mod, but don't find those engines useless without it. And because of "FINAL" command, I need to comment out this piece of code each time when UKS mod updates. I can't create my own MM patches that could overrride that MM comand. It wont work. More apropriate thing would be to use BEFORE or AFTER UKS or something like that.

I understand that there is some people who want just to hide those parts, though.

[kcs123]

Found some more parts that does not seem to fit properly in tech tree. SIGINT parts from DMagic Orbital science apear too soon in tech tree, much sooner than most powerful stock RA-100 Antenna. While those parts serve as science part, their secondary role is over powered Relay in comparison to stock parts. Put one such part in geostationary orbit and your comm network is early covered for whole KSP universe.

So, I moved those for my peronal purpose much higher in tech tree. Also note that there is 3 similar SIGINT parts: "dmSIGINT.Small", "dmSIGINT" and "dmSIGINT.End".
Seems like "dmSIGINT.Small" was not covered at all in config files, so it apeared too soon in "miniaturization" tech tree node. To balance out changes I have also moved part "dmScope" (least powerful in terms of Science collection) to "miniaturization" node, it was just one tier less than before, but also that part should be available sooner than GORESAT (infrared scope).

@PART[dmSIGINT.Small]:NEEDS[CommunityTechTree,DMagicOrbitalScience]:BEFORE[zzzUnKerballedStart]
{
	@TechRequired = experimentalScience
	//@TechRequired = miniaturization // apear too soon
}


@PART[dmSIGINT.End]:NEEDS[CommunityTechTree,DMagicOrbitalScience]:BEFORE[zzzUnKerballedStart]
{
	@TechRequired = longTermScienceTech
	//@TechRequired = advScienceTech // previous tech node	
}

@PART[dmSIGINT]:NEEDS[CommunityTechTree,DMagicOrbitalScience]:BEFORE[zzzUnKerballedStart]
{
	@TechRequired = longTermScienceTech
	//@TechRequired = advScienceTech // previous
}

@PART[dmscope]:NEEDS[CommunityTechTree,DMagicOrbitalScience]:BEFORE[zzzUnKerballedStart]
{
		@TechRequired = miniaturization  // tier 5
		//@TechRequired = advExploration // previous tier 6
}

 

[kcs123]

IR Next is just released.

While IR Next comes with Ctt support, seems to be off the place for UKS. So, I re-positioned those along robotic line of tech tree branches:

Spoiler

@PART[IR_Pivotron_Uncontrolled_v3|IR_Rotatron_Uncontrolled_v3]:NEEDS[MagicSmokeIndustries,CommunityTechTree,UnKerballedStart]:BEFORE[zzzUnKerballedStart]
{
	@TechRequired = actuators
}

@PART[IR_RailExtendatron|IR_RailGantry_Long|IR_RailGantry_Short|IR_RailHinge_Long|IR_RailHinge_Short|IR_RailLiftatron_Long|IR_RailLiftatron_Short|IR_RailPivotron_Long|IR_RailPivotron_Short|IR_RailRotatron_Long|IR_RailRotatron_Short|IR_RailSlidertron_Long|IR_RailSlidertron_Short]:NEEDS[MagicSmokeIndustries,CommunityTechTree,UnKerballedStart]:BEFORE[zzzUnKerballedStart]
{
	@TechRequired = advActuators
}

@PART[IR_LandingFoot|IR_LargeSuspension|IR_SmallSuspension|IR_Foldatron_OffsetMini_v3|IR_Foldatron_Offset_v3|IR_Foldatron_Mini_v3|IR_Foldatron_InsetTwist_v3|IR_Foldatron_InsetEnd_v3|IR_Foldatron_Inset_v3|IR_Foldatron_Hinge_v3|IR_Foldatron_Extended_v3|IR_Foldatron_Basic_v3]:NEEDS[MagicSmokeIndustries,CommunityTechTree,UnKerballedStart]:BEFORE[zzzUnKerballedStart]
{
	@TechRequired = experimentalActuators
}

@PART[IR_Camera|IR_DockingPort|IR_SurfaceSampler]:NEEDS[MagicSmokeIndustries,CommunityTechTree,UnKerballedStart]:BEFORE[zzzUnKerballedStart]
{
	@TechRequired = offworldManufacturing
}

@PART[IR_MagneticGrabber|IR_MechanicalGrasper]:NEEDS[MagicSmokeIndustries,CommunityTechTree,UnKerballedStart]:BEFORE[zzzUnKerballedStart]
{
	@TechRequired = mechatronics
}

// IR_LockConnector is part from InnerLock mod, but it is installed in MagicSmokeIndustries folder along other robotic parts
@PART[IR_LockConnector]:NEEDS[InnerLock,MagicSmokeIndustries,CommunityTechTree,UnKerballedStart]:BEFORE[zzzUnKerballedStart]
{
	@TechRequired = nanolathing
}

 

[oOScarfacEOo]

Since I didn't find Unkerballed at GitHub I post it here. Compatibility for PEBKAC Industries: Launch Escape System:

 

//PebkacLaunchEscape2
//
@PART[pkLES_EscapeMk1v2]:NEEDS[CommunityTechTree,PebkacLaunchEscape2]:BEFORE[zzzUnKerballedStart]
{
		@TechRequired = enhancedSurvivability
}

@PART[pkLES_mk2_noBPC|pkLES_mk2]:NEEDS[CommunityTechTree,PebkacLaunchEscape2]:BEFORE[zzzUnKerballedStart]
{
		@TechRequired = recycling
}

 

 

[Jognt]

On 5/22/2019 at 10:05 PM, kcs123 said:

@theonegalen, is it possible to remove "FINAL" from this KAX config ?

//Hide Propelators, which asre useless without tiny SXT wings 
@PART[KAXVintagePropelator|KAXVintagePropelatorExtra|KAXVintagePropelatorS|KAXVintagePropelatorSS]:NEEDS[!SXT]:FINAL
{
	@TechRequired = unresearchable
	@category = none
	@TechHidden = true
}

I don't use SXT mod, but don't find those engines useless without it. And because of "FINAL" command, I need to comment out this piece of code each time when UKS mod updates. I can't create my own MM patches that could overrride that MM comand. It wont work. More apropriate thing would be to use BEFORE or AFTER UKS or something like that.

I understand that there is some people who want just to hide those parts, though.

Regardless, using FINAL should be a 'last resort' for stuff you definitely aren't going to distribute and don't want to tinker too much with. For most cases "AFTER[]" is good enough, for edge cases you can use "LAST[]", but FINAL?

[kcs123]

New postitions for Breaking Grounds DLC parts. Just slight movement trough tech tree that have more sense with UKS.
 

Spoiler

// Ground science parts
@PART[DeployedWeatherStn]:NEEDS[SquadExpansion/Serenity,CommunityTechTree,UnKerballedStart]:BEFORE[zzzUnKerballedStart]
{
	@TechRequired = advExploration
	//@TechRequired = precisionEngineering
}

@PART[DeployedGoExOb]:NEEDS[SquadExpansion/Serenity,CommunityTechTree,UnKerballedStart]:BEFORE[zzzUnKerballedStart]
{
	@TechRequired = spaceExploration
	//@TechRequired = miniaturization
}

@PART[DeployedSeismicSensor]:NEEDS[SquadExpansion/Serenity,CommunityTechTree,UnKerballedStart]:BEFORE[zzzUnKerballedStart]
{
	@TechRequired = scienceTech
	//@TechRequired = electronics
}

// robotic parts - OK
@PART[hinge_01|hinge_01_s|hinge_03|hinge_03_s|hinge_04|piston_01|piston_02|piston_03|piston_04|controller1000]:NEEDS[SquadExpansion/Serenity,CommunityTechTree,UnKerballedStart]:BEFORE[zzzUnKerballedStart]
{
	@TechRequired = actuators
}

@PART[rotor_01|rotor_02|rotor_03|rotoServo_00|rotoServo_02|rotoServo_03|rotoServo_04]:NEEDS[SquadExpansion/Serenity,CommunityTechTree,UnKerballedStart]:BEFORE[zzzUnKerballedStart]
{
	@TechRequired = advActuators
}

 

And if you need to mark new parts, to be more readable for further adjustment you can do this with following MM patch:

// marking BG parts in title
@PART[*]:HAS[@MODULE[ModuleGroundSciencePart]]:NEEDS[SquadExpansion/Serenity,CommunityTechTree,UnKerballedStart]:BEFORE[zzzUnKerballedStart]
{
	@title ^= :$: *BG GroundScience*:
}

@PART[*]:HAS[@MODULE[ModuleGroundExperiment]]:NEEDS[SquadExpansion/Serenity,CommunityTechTree,UnKerballedStart]:BEFORE[zzzUnKerballedStart]
{
	@title ^= :$: *BG GroundExperiment*:
}

@PART[*]:HAS[@MODULE[ModuleGroundCommsPart]]:NEEDS[SquadExpansion/Serenity,CommunityTechTree,UnKerballedStart]:BEFORE[zzzUnKerballedStart]
{
	@title ^= :$: *BG GroundCommsPart*:
}

@PART[*]:HAS[@MODULE[ModuleGroundExpControl]]:NEEDS[SquadExpansion/Serenity,CommunityTechTree,UnKerballedStart]:BEFORE[zzzUnKerballedStart]
{
	@title ^= :$: *BG GroundExpControl*:
}

@PART[*]:HAS[@MODULE[ModuleRobotArmScanner]]:NEEDS[SquadExpansion/Serenity,CommunityTechTree,UnKerballedStart]:BEFORE[zzzUnKerballedStart]
{
	@title ^= :$: *BG RobotArmScanner*:
}

@PART[*]:HAS[@MODULE[ModuleInventoryPart]]:NEEDS[SquadExpansion/Serenity,CommunityTechTree,UnKerballedStart]:BEFORE[zzzUnKerballedStart]
{
	@title ^= :$: *BG InventoryPart*:
}

// --------------

 

Edited June 1, 2019 by kcs123

[Bluehelmet]

Is the mod going to be updated with these changes anytime soon? Cheers

[kcs123]

2 hours ago, Bluehelmet said:

Is the mod going to be updated with these changes anytime soon? Cheers

It is hard to tell, SpinkAkron is busy lately, haven't be even able to visit forum in last week or two. Proposed changes may or may not be adopted in next mod update. I'm using those in my personal game and I provided those patches to help development when mod authors are able to make such changes. And to provide help for others, to customize their game if they want it until official mod update.

On 5/16/2019 at 8:01 AM, Steven Mading said:

Be aware that thrust plates only exist in the Making History DLC, not the stock game (which is annoying - they are an important base part for exactly this reason - multi-engine mounts are a basic rocketry idea dating back to the early days.)  Without thrust plates, most engines will refuse to surface attach to the bottom of a fuel tank so you can only mount one engine, in the center of the tank, on the attachment node.

The structural parts that fork multi-ways (2-way, 3-way, 4-way adapter) are the only other option I've found without DLC parts, and I don't think they're available at the start in the tech tree.

That gave me inspiration for new part propsal. Thanks, @Steven Mading.

When I was playing a bit more, I have created smaller versions of 2,3 and 4 way adapters. Basicaly, just scaled down of existing in game adapters. Those comes with trade-off, though, not ultimate solution. It will cost slightly more than if you use cubic truss to attach engines, weight is also increased, so you will end up with lower overall dV. But, it can help a lot with level one SPH/VAB building when you need to worry a lot about part count limits.

TVR-200Ls Stack Bi-Adapter:

Spoiler

+PART[adapterLargeSmallBi]:NEEDS[CommunityTechTree,UnKerballedStart]
{
	@name = UKS_adapterLargeSmallBi
	
	@rescaleFactor = 0.5
	@node_stack_top = 0.0, 0.0, 0.0, 0.0, 1.0, 0.0, 1
	@node_stack_bottom01 = 0.0, -0.75, 0.625, 0.0, -1.0, 0.0, 0
	@node_stack_bottom02 = 0.0, -0.75, -0.625, 0.0, -1.0, 0.0, 0
	@TechRequired = generalConstruction
	@entryCost = 7800
	@cost = 200
	
	@title = #LOC_UKS_adapterLargeSmallBi_title
	@description = #LOC_UKS_adapterLargeSmallBi_description
	
	@mass = 0.05
	
	
	@maximum_drag = 0.1
	@minimum_drag = 0.1
	@angularDrag = 1
	
	
	@bulkheadProfiles = size1, size0
	
	
}

 

TVR-300Ls Stack Tri-Adapter:
 

Spoiler

+PART[adapterLargeSmallTri]
{
	@name = UKS_adapterLargeSmallTri
	
		
	@rescaleFactor = 0.5
	@node_stack_top = 0.0, 0.0, 0.0, 0.0, 1.0, 0.0, 1
	@node_stack_bottom01 = 0.0, -0.75, 0.725, 0.0, -1.0, 0.0, 0
	@node_stack_bottom02 = 0.625, -0.75, -0.3625, 0.0, -1.0, 0.0, 0
	@node_stack_bottom03 = -0.625, -0.75, -0.3625, 0.0, -1.0, 0.0, 0
	
	@TechRequired = generalConstruction
	@entryCost = 6400
	@cost = 300
	@category = Structural
	
	
	@title = #LOC_UKS_adapterLargeSmallTri_title //#autoLOC_500715 = TVR-300L Stack Tri-Adapter
	@description = #LOC_UKS_adapterLargeSmallTri_description //#autoLOC_500716 = After realizing 'larger circles' wasn't a very patentable concept, O.M.B. Enterprises rolled out a new line of ingenious multi-connector adapters to fit Rockomax sized parts. Lawsuit still pending. Converts a single 2.5m stack into three 1.25m stacks.
	
	@mass = 0.075
	@dragModelType = default
	@maximum_drag = 0.125
	@minimum_drag = 0.125
	@angularDrag = 1.25
	
	@bulkheadProfiles = size1, size0
	
}

 

TVR-400Ls Stack Quad-Adapter:
 

Spoiler

+PART[adapterLargeSmallQuad]:NEEDS[CommunityTechTree,UnKerballedStart]
{
	@name = UKS_adapterLargeSmallQuad
	
	@rescaleFactor = 0.5
	
	@node_stack_top = 0.0, 0.0, 0.0, 0.0, 1.0, 0.0, 1
	@node_stack_bottom01 = 0.625, -0.75, 0.625, 0.0, -1.0, 0.0, 0
	@node_stack_bottom02 = 0.625, -0.75, -0.625, 0.0, -1.0, 0.0, 0
	@node_stack_bottom03 = -0.625, -0.75, 0.625, 0.0, -1.0, 0.0, 0
	@node_stack_bottom04 = -0.625, -0.75, -0.625, 0.0, -1.0, 0.0, 0
	
	@TechRequired = generalConstruction
	@entryCost = 7000
	@cost = 400
	
	@title = #LOC_UKS_adapterLargeSmallQuad_title // TVR-400Ls Stack Quad-Adapter
	@description = #LOC_UKS_adapterLargeSmallQuad_description
	
	@mass = 0.1
	@dragModelType = default
	@maximum_drag = 0.15
	@minimum_drag = 0.15
	@angularDrag = 1.5
	
	@bulkheadProfiles = size1, size0
	
}

 

And localization file with description for all parts:
 

Spoiler

Localization
{
  en-us
  {
	
	// TVR-200Ls Stack Bi-Adapter
		#LOC_UKS_adapterLargeSmallBi_title = TVR-200Ls Stack Bi-Adapter
		#LOC_UKS_adapterLargeSmallBi_description = After realizing 'larger circles' wasn't a very patentable concept, O.M.B. Enterprises rolled out a new line of ingenious multi-connector adapters to fit Rockomax sized parts. Lawsuit still pending. Converts a single 1.25m stack into two 0.625m stacks.
	// UKS_adapterLargeSmallTri
		#LOC_UKS_adapterLargeSmallTri_title = TVR-300Ls Stack Tri-Adapter
		#LOC_UKS_adapterLargeSmallTri_description = After realizing 'larger circles' wasn't a very patentable concept, O.M.B. Enterprises rolled out a new line of ingenious multi-connector adapters to fit Rockomax sized parts. Lawsuit still pending. Converts a single 1.25m stack into three 0.625m stacks.
	// UKS_adapterLargeSmallQuad
		#LOC_UKS_adapterLargeSmallQuad_title = TVR-400Ls Stack Quad-Adapter
		#LOC_UKS_adapterLargeSmallQuad_description = After realizing 'larger circles' wasn't a very patentable concept, O.M.B. Enterprises rolled out a new line of ingenious multi-connector adapters to fit Rockomax sized parts. Lawsuit still pending. Converts a single 1.25m stack into four 0.625m stacks.
	
	}
}

 

 

Edited June 9, 2019 by kcs123

[Jognt]

@kcs123 Y'know, I agree with your proposal to remove FINAL, but don't you think you should let the guy manage his own mod?

[SpinkAkron]

1 hour ago, Jognt said:

@kcs123 Y'know, I agree with your proposal to remove FINAL, but don't you think you should let the guy manage his own mod?

Totally cool. This sort of thing will save me a lot of time when I can get back to gaming. 

Sorry I've been AWOL. I have to paint my house this summer and all my formerly free time has to go scraping 120 years of paint and restoration generally if I'm to have any chance of getting my house done before I have to go to the old folks home. Thanks to @kcs123 for helping out with questions,fixes,and updates in the interim!

[kcs123]

2 hours ago, Jognt said:

@kcs123 Y'know, I agree with your proposal to remove FINAL, but don't you think you should let the guy manage his own mod?

I always respect mod authors, it is their finall decision should some of proposed be adopted on the end or not. Instead of just complaining about something, I have also proposed solutions. Even if something is not adopted as proposed, it will be easier to do additional adjustments for the next update. I post all my findings here on forum because I'm "lazy" to create github account (have already too much account to handle, both, private and at work). Also, I don't know how much time I would have in future, to create some kind of UKS config extension or similar add-on mod and continue to maintain it.

@SpinkAkron, take your time, private life commitments have always priority. Community will have to either, be patient for next update or learn how to create their own set of patches for personal needs.

[Jognt]

On 5/27/2019 at 12:13 AM, kcs123 said:

Found some more parts that does not seem to fit properly in tech tree. SIGINT parts from DMagic Orbital science apear too soon in tech tree, much sooner than most powerful stock RA-100 Antenna. While those parts serve as science part, their secondary role is over powered Relay in comparison to stock parts. Put one such part in geostationary orbit and your comm network is early covered for whole KSP universe.

So, I moved those for my peronal purpose much higher in tech tree. Also note that there is 3 similar SIGINT parts: "dmSIGINT.Small", "dmSIGINT" and "dmSIGINT.End".
Seems like "dmSIGINT.Small" was not covered at all in config files, so it apeared too soon in "miniaturization" tech tree node. To balance out changes I have also moved part "dmScope" (least powerful in terms of Science collection) to "miniaturization" node, it was just one tier less than before, but also that part should be available sooner than GORESAT (infrared scope).

@PART[dmSIGINT.Small]:NEEDS[CommunityTechTree,DMagicOrbitalScience]:BEFORE[zzzUnKerballedStart]
{
	@TechRequired = experimentalScience
	//@TechRequired = miniaturization // apear too soon
}


@PART[dmSIGINT.End]:NEEDS[CommunityTechTree,DMagicOrbitalScience]:BEFORE[zzzUnKerballedStart]
{
	@TechRequired = longTermScienceTech
	//@TechRequired = advScienceTech // previous tech node	
}

@PART[dmSIGINT]:NEEDS[CommunityTechTree,DMagicOrbitalScience]:BEFORE[zzzUnKerballedStart]
{
	@TechRequired = longTermScienceTech
	//@TechRequired = advScienceTech // previous
}

@PART[dmscope]:NEEDS[CommunityTechTree,DMagicOrbitalScience]:BEFORE[zzzUnKerballedStart]
{
		@TechRequired = miniaturization  // tier 5
		//@TechRequired = advExploration // previous tier 6
}

 

In that case, I think you could squish the above bit into

@PART[dmSIGINT.Small|dmSIGINT.End|dmSIGINT|dmscope]:NEEDS[CommunityTechTree,DMagicOrbitalScience]:BEFORE[zzzUnKerballedStart]
{
	@TechRequired ^= :miniaturization:experimentalScience:
	@TechRequired ^= :advScienceTech:longTermScienceTech:
	@TechRequired ^= :advExploration:miniaturization:
}

I haven't tested it but I think it should work, and it saves on lines

edit: In case I'm totally missing something, let me know.. Because part of me is facepalming in the back of my head, so I'm probably missing something obvious..

Edited June 10, 2019 by Jognt

[Bombaatu]

Knowing that This Way Leads Madness due to the sheer volume of parts, have you considered making configs for Bluedog Design Bureau?

[Snoman314]

Without reading 9 pages of posts, does anyone know if the reactor science nodes got moved back to come off the propulsion nodes? It's weird to have all the late-game nuclear engines and reactors that are all used for propulsion to sit off the electrics branch of the tech tree.

[Therese]

Mod compatibility request:

Is it possible to nerf the probodobodobodyne qbe when Kerbalism is installed? 

Kerbalism uses hard drive space, and early cores have 0.5-1.0 Mb of storage, but the qbe gets 80Mb, so it's OP in early career. 

Asking here, since Kerbalism dev team have other priorities before supporting this mod. 

[kcs123]

7 hours ago, Therese said:

Mod compatibility request:

Is it possible to nerf the probodobodobodyne qbe when Kerbalism is installed? 

Kerbalism uses hard drive space, and early cores have 0.5-1.0 Mb of storage, but the qbe gets 80Mb, so it's OP in early career. 

Asking here, since Kerbalism dev team have other priorities before supporting this mod. 

Yep, it is possible, but you would probably want to add some personal patch for that part for personal usage. I'm not familiar with Kerbalism mod, so I don't know what exact module name for disk storage it add to command module, but I can give you example that I used to add reaction wheels to it. Note that I don't know exact folder name for Kerbalism and for disk storage, so you will need to search trough Kerbalism config files to see what kind of new module is added to command probes.

See in spoiler section example how it should work. Sorry, I have no time right now to try Kerbalism and chase down all necessary exact variable names, but it may help you to do it by yourself. Post it here if you find exact proper solution, if not, I may do it later on when I grab more free time for it.

Spoiler

@PART[probeCoreCube]:NEEDS[Kerbalism,UnKerballedStart]:AFTER[Kerbalism]
{
	@MODULE[Kerbalism_disk_module_name]
	{
		@disk_storage_variable_name_amount = 0.5		
	}
}
// Use proper variable names, this is just example how it should work

 

 

[Therese]

5 hours ago, kcs123 said:

Yep, it is possible, but you would probably want to add some personal patch for that part for personal usage.

The devs for Kerbalism actually uploaded a supporting version yesterday, so it's not an issue after all.

Thanks anyway for your suggestion

[kcs123]

1 hour ago, Therese said:

The devs for Kerbalism actually uploaded a supporting version yesterday, so it's not an issue after all.

Thanks anyway for your suggestion

You are welcome. Good to know that you are sorted out that thing with Kerbalism developers.

[firefly_t]

Firstly, thank you for a great mod. It has encouraged me to get back into playing KSP, as I always played with Unmanned Before Manned.

May I politely request for mod support to be added for OPT Space Plane, please? This really helps fill the tech tree out and provides some later game options and fun choices

Thank you in advance!

[Ryan_Coates]

Thank you  for a great mod

 

[Joker58th]

Could I ask some help here with a modification I am trying to make with the tech tree and an SSTU upgrade.  Here is the original code from the mod.

PARTUPGRADE
{
	name = SSTU-SC-ENG-SRB-GeneralRocketry
	partIcon = SSTU-SC-ENG-SRB-A
	techRequired = generalRocketry
	entryCost = 2000
	cost = 0

	title = Modular SRB Efficiency Upgrade
	manufacturer = SSTU
	description = A new, more explosive fuel mixture improves the burning efficiency of solid rockets.
}

I have been making some changes with SSTU parts successfully so I thought I would try using the same structure like this:

//heavierRocketry
@PARTUPGRADE[SSTU-SC-ENG-SRB-GeneralRocketry]:NEEDS[CommunityTechTree,SSTU]:BEFORE[zzzUnKerballedStart]
{
	@TechRequired = heavierRocketry
}

But its not working.  Can someone give some guidance here?

[kcs123]

I'm not familiar that much with part upgrade, but have you tried this:

//heavierRocketry
@PARTUPGRADE[SSTU-SC-ENG-SRB-GeneralRocketry]:NEEDS[CommunityTechTree,SSTU,UnKerballedStart]:AFTER[zzzUnKerballedStart]
{
	@TechRequired = heavierRocketry
}

Although, I think that "zzzUnkerballedStart" that is written everywhere trough UnkerbaledStart patches does not do anything, because there is no such folder inside Gamedata folder or plugin with that name. I think that it is leftover of WIP version of Unkerballed Start mod, but have to check with @SpinkAkron to tell for sure. Any of those does not cause any harm, though.

To ensure that your patch is executed after all other patches applied in game, it is good practice to place your own patches in your own folder that start with "Z*". I used "ZX_CustomTweaks" for my personal purposes for example. If you want to execute some commands BEFORE some other mod patches are executed, that will work properly if you tell MM to do so, but placing your own patches in "Z" folder will make those that were executed last.

And you may want to execute your patches last, because if you put BEFORE command, some other MM patch may override your command. To check out if your filter clause of MM patch (needs, has, etc.) work properly, you may want to try with something more simple, like changing a title of part, to visualy detect if patches are applied properly.

Other than that, if above tips does not help, you may want to ask questions in MM thread instead. More people with better knowledge of MM follow that thread and you may find answer sooner.