adm-frb

Change Log added.

Dumb question How to create the change log?

Just getting used to github

Do I tell it to merge?

Created a development topic as this is no longer really a discussion/experiment [WIP][1.8.1] KAE SYSTEMS Welded Parts

WELDED PARTS By adm-frb Licence: CC BY-NC-SA-4.0 Github ChangeLog: This mod pack idea was partly inspired by my desire to reduce my part count by turning my subassemblies into single parts and watching Bob Fitch's [Felbourn] Project Gateway and Odyssey. In it I discovered the possibility of welding through the UbioZur Welding Ltd. Continued mod. Unfortunately, it is not currently being maintained and doesn't work in KSP 1.8.1 which is the most recent version I'm using... What this pack will amount to is a collection of subassemblies that I have welded - the hard and tedious way - into single parts much like Felbourn used to do with the afore mentioned mod. At present, I just have a single part, but intend for it grow over time. At present, it just needs stock KSP with the Making History DLC, but that could change as it grows... Well, without further ado, let's get into the first part. KV Reentry Module Adapter The part does work as it currently stands. A lower module for the KV Series Reentry Modules to turn them into Soyuz Descent Modules. It has a fairing with an integrated fuel tank (I usually swap out the LFO for Monopropellant), that also includes a reaction wheel. But I do have a couple of issues that is preventing me from releasing it quite yet. I'd like to give it some electric charge and maybe command ability so that it can operate the KV Module unkerbaled I'd much rather it used the restock models and textures which are much nicer, but my attempts to make them use them all fail and the part ceases to appear in the VAB This is the part that is supposed to add electric charge to the unit. But it seems to do nada... RESOURCE { name = ElectricCharge amount = 150 maxAmount = 150 } } Full config file Help would be appreciated

Thanks...

Speaking of that, I have set up a GitHub account, but I have a question on licencing, I know which licence, you use, but which option does that come under in GitHub? I can't seem to find it as there are a few similar ones Btw, the 'KAE SYSTEMS' is a play on BAE SYSTEMS as I'm British and if the UK had a space program that was at the same level as NASA's you could bet BAE SYSTEMS would be the primary contractor.

// lowerModule.cfg v1.0.0.1 // KAE Systems // created: 2020 03 04 // updated: 2020 03 05 adm-frb PART { name = WELD-lowerModule module = Part author = adm-frb,zer0Kerbal MODEL { model = SquadExpansion/MakingHistory/Parts/FuelTank/Assets/Size1_5_Size1_Adapter_02 // mainTextureURL = SquadExpansion/MakingHistory/Parts/FuelTank/Assets/Size1_5_TankAdapters_ALT02 // _BumpMap =SquadExpansion/MakingHistory/Parts/FuelTank/Assets/Size1_5_TankAdapters_ALT02nm position = 0, 0.31, 0 } MODEL { model = Squad/Parts/Aero/fairings/fairingSize1 //position = 0, -0.041, 0 scale = 1.5, 1.0, 1.5 rotation = 0.0, 180, 0.0 // TextureNormalURL = Squad/Parts/Aero/fairings/FairingBaseNormals } MODEL { model = Squad/Parts/Aero/fairings/AutoTruss scale = 1.5, 1.5, 1.5 // position = 0.0, 0.22, 0.0 position = 0, 0.179, 0 } rescaleFactor = 1 node_stack_top = 0.0, 0.55438, 0.0, 0.0, 1.0, 0.0, 2 node_stack_bottom = 0.0, -0.2, 0.0, 0.0, -1.0, 0.0, 2 node_stack_interstage01a = 0.0, 0.94, 0.0, 0.0, -1.0, 0.0, 1 node_stack_interstage01b = 0.0, 1.0, 0.0, 0.0, 1.0, 0.0, 1 node_stack_interstage02a = 0.0, 1.69, 0.0, 0.0, -1.0, 0.0, 1 node_stack_interstage02b = 0.0, 1.75, 0.0, 0.0, 1.0, 0.0, 1 node_stack_interstage03a = 0.0, 2.44, 0.0, 0.0, -1.0, 0.0, 1 node_stack_interstage03b = 0.0, 2.50, 0.0, 0.0, 1.0, 0.0, 1 node_stack_interstage04a = 0.0, 3.19, 0.0, 0.0, -1.0, 0.0, 1 node_stack_interstage04b = 0.0, 3.25, 0.0, 0.0, 1.0, 0.0, 1 node_stack_interstage05a = 0.0, 3.94, 0.0, 0.0, -1.0, 0.0, 1 node_stack_interstage05b = 0.0, 4.00, 0.0, 0.0, 1.0, 0.0, 1 node_stack_interstage06a = 0.0, 4.69, 0.0, 0.0, -1.0, 0.0, 1 node_stack_interstage06b = 0.0, 4.75, 0.0, 0.0, 1.0, 0.0, 1 // use the below to adjust nodes (or adjust by model positions): // attN = interstage01a,Null_0_0|0.939999998|0_0|-1|0_0|0.939999998|0_0|-1|0 // attN = interstage01b,Null_0_0|1|0_0|1|0_0|1|0_0|1|0 // attN = interstage02a,Null_0_0|1.69000006|0_0|-1|0_0|1.69000006|0_0|-1|0 // attN = interstage02b,Null_0_0|1.75|0_0|1|0_0|1.75|0_0|1|0 // attN = interstage03a,Null_0_0|2.44000006|0_0|-1|0_0|2.44000006|0_0|-1|0 // attN = interstage03b,Null_0_0|2.5|0_0|1|0_0|2.5|0_0|1|0 // attN = interstage04a,Null_0_0|3.19000006|0_0|-1|0_0|3.19000006|0_0|-1|0 // attN = interstage04b,Null_0_0|3.25|0_0|1|0_0|3.25|0_0|1|0 // attN = interstage05a,Null_0_0|3.94000006|0_0|-1|0_0|3.94000006|0_0|-1|0 // attN = interstage05b,Null_0_0|4|0_0|1|0_0|4|0_0|1|0 // attN = interstage06a,Null_0_0|4.69000006|0_0|-1|0_0|4.69000006|0_0|-1|0 // attN = interstage06b,Null_0_0|4.75|0_0|1|0_0|4.75|0_0|1|0 // attN = top,Size1p5.Size1.Adapter.02_4293497416_0|0.219999999|0_0|1|0_0|0.219999999|0_0|1|0 // attN = bottom,Null_0_0|-0.200000003|0_0|-1|0_0|-0.200000003|0_0|-1|0 TechRequired = advRocketry entryCost = 1550 cost = 160 category = Payload // FuelTank subcategory = 0 title = KV Reentry Module Adapter manufacturer = KAE Systems description = Valentia cried when she was shown this adapter, exclaiming: "This is just what the KV Reentry Modules needed!" Includes an integral Fuel Tank. Warranty void during re-entry. tags = fueltank ?lfo liquid oxidizer propellant rocket aero )cap cargo cone contain drag fairing hollow inter nose payload protect rocket shroud stage (stor transport weld attachRules = 1,0,1,1,0 mass = 0.25 dragModelType = default maximum_drag = 0.2 minimum_drag = 0.3 angularDrag = 2 crashTolerance = 9 breakingForce = 250 breakingTorque = 250 maxTemp = 2600 thermalMassModifier = 2.0 skinMassPerArea = 4.0 skinInternalConductionMult = 0.25 // heatConductivity = 0.06 // half default emissiveConstant = 0.8 fuelCrossFeed = True bulkheadProfiles = size1, size1p5, srf explosionPotential = 0.5 stageOffset = 1 childStageOffset = 1 inverseStageCarryover = false stagingIcon = FUEL_TANK MODULE { name = ModuleProceduralFairing nSides = 32 nArcs = 2 nCollidersPerXSection = 8 TextureURL = Squad/Parts/Aero/fairings/fairings_diff CapTextureURL = Squad/Parts/Aero/fairings/fairingsCap TextureNormalURL = Squad/Parts/Aero/fairings/fairings_normals panelGrouping = 3 pivot = 0,0.17,0 axis = 0,1,0 baseRadius = 0.9375 maxRadius = 2.25 capRadius = 0.2 snapThreshold = 0.1 xSectionHeightMin = 0.2 xSectionHeightMax = 2 edgeSlide = 0.15 edgeWarp = 0 noseTip = 0.7 UnitAreaMass = 0.015 UnitAreaCost = 6 //Needs balance stagingToggleEnabledEditor = True stagingToggleEnabledFlight = False stagingEnableText = #autoLOC_502000 //#autoLOC_502000 = Fairing Not Staged stagingDisableText = #autoLOC_502001 //#autoLOC_502001 = Fairing Staged } MODULE { name = ModuleCargoBay DeployModuleIndex = 0 closedPosition = 0 lookupRadius = 0.75 // nodeOuterAftID = bottom // nodeInnerAftID = top } MODULE { name = ModuleStructuralNode rootObject = Cap1 attachNodeNames = interstage01a,interstage01b } MODULE { name = ModuleStructuralNode rootObject = Cap2 attachNodeNames = interstage02a,interstage02b } MODULE { name = ModuleStructuralNode rootObject = Cap3 attachNodeNames = interstage03a,interstage03b } MODULE { name = ModuleStructuralNode rootObject = Cap4 attachNodeNames = interstage04a,interstage04b } MODULE { name = ModuleStructuralNode rootObject = Cap5 attachNodeNames = interstage05a,interstage05b } MODULE { name = ModuleStructuralNode rootObject = Cap6 attachNodeNames = interstage06a,interstage06b } MODULE { name = ModuleStructuralNode rootObject = Truss1 attachNodeNames = interstage01a,interstage01b,interstage02a,interstage02b,interstage03a,interstage03b,interstage04a,interstage04b,interstage05a,interstage05b,interstage06a,interstage06b } MODULE { name = ModuleStructuralNode rootObject = Truss2 attachNodeNames = interstage02a,interstage02b,interstage03a,interstage03b,interstage04a,interstage04b,interstage05a,interstage05b,interstage06a,interstage06b } MODULE { name = ModuleStructuralNode rootObject = Truss3 attachNodeNames = interstage03a,interstage03b,interstage04a,interstage04b,interstage05a,interstage05b,interstage06a,interstage06b } MODULE { name = ModuleStructuralNode rootObject = Truss4 attachNodeNames = interstage04a,interstage04b,interstage05a,interstage05b,interstage06a,interstage06b } MODULE { name = ModuleStructuralNode rootObject = Truss5 attachNodeNames = interstage05a,interstage05b,interstage06a,interstage06b } MODULE { name = ModuleStructuralNode rootObject = Truss6 attachNodeNames = interstage06a,interstage06b } MODULE { name = ModuleStructuralNodeToggle MeshMenuName = #autoLOC_502002 //#autoLOC_502002 = Truss Structure NodeMenuName = #autoLOC_502003 //#autoLOC_502003 = Interstage Nodes showNodes = false } RESOURCE { name = LiquidFuel amount = 72 maxAmount = 72 } RESOURCE { name = Oxidizer amount = 88 maxAmount = 88 } MODULE { name = ModuleReactionWheel PitchTorque = 15 YawTorque = 15 RollTorque = 15 torqueResponseSpeed = 15 RESOURCE { name = ElectricCharge rate = 0.45 } } // CC BY-NC-SA-4.0 // adm-frb and zer0Kerbal I forgot to paste the code... LOL

LOL I updated the config file. Everything works the way it should. It can now serve as an SAS Unit for the KV Reentry modules Val, Karen and Annabelle testing the Bullet Descent Module on the test stand Testing the fairing Sunrise over the test stand Did I just create a mod?

F I found the charring module just as you posted...

LOL Currently looking at something different. A module to add scorching to fairings like happens to the KV reentry modules when ablator is set to zero. I'm studying the squad configs for those pods

Might try later...

That was something I suspected... Dissapointing

Is it possible to convert subassembly files into new parts? If so, how? I've put an example at the bottom I'm just curious, as I'd really like to try to keep my part count down and I'm aware that 'UbioWeldContinued' is not currently being maintained. It doesn't work in 1.8.1 (my current version of KSP) and probably quite a few previous versions either. I don't think there are any other mods that can do this.. I'd love a converter, and would be willing to create one, but also don't know the first thing about doing this. If I was to do this, I'd need a [bleep] lot of help... Example subassembly

Hey Navot, I was just wondering if you'd ever considered adding your decoupler shroud function to engine plates? EDIT Reason I'm asking is that sometimes I use decoupler shroud to override stock shrouds, but I can't do this with engine plates as the decoupler shroud function is not available with the engine plates

Works with no issues... For me anyway...

Hey, was just wondering if you'd considered adding new Launch Escape Systems for the mk1 command pod, the mk2 command pod and a redone stock launch escape system for the stock mk1-3 command pod?

Yes. You need to whitelist the stock Mk1-3 Command Pod, then create a new configuration file I’ve quoted myself below. I also stated where I saved it to That will give you both versions of the command pod

@Streetwind Added this config file +PART[mk1-3pod]:NEEDS[ReStock]:FIRST { @name = mk1-3pod-old @title = Mk1-3L Command Pod @description = Many Kerbals have asked what the 'L' means. Verner's answer was beyond simple. "This is the old version of the Mk1-3 Command Pod. It does not mean 'Lunch!'" } GameData>Mk1-3L>Mk1-3L.cfg

Will try later

I know next to nothing about module manager, unfortunately. I've created new parts before, but only through copying stock config files, changing the part names and tweaking variables and have never published anything. What I'd really like to do is learn how create true variants like you have with the mk 1 command pod, the cheetah engine and the stock version of the F-1 (I forget what it's called)

Done... Got the original mk1-3 command pod back!!!!! Yes

Really nice mod and much better than stock My only quibble is with the mk1-3 Command Pod which no longer fits sumghai's excellent SDHI Service Module. https://forum.kerbalspaceprogram.com/index.php?/topic/48073-16x-sdhi-service-module-system-v401-25-december-2018/&tab=comments#comment-683549 I've tried whitelisting the stock mk1-3 Command Pod to get it back but to no effect. Would be nice if the part was switchable as I really don't want to remove the restock version mk1-3 command pod

Jeb and Val are really looking forward to that improvement Jeb said it was a fun ride not knowing if the chutes are deployed or not while Val was quoted as saying "Really glad they managed to squeeze though the gaps in the fairing! Otherwise I might be dead or have a broken back...