MKSheppard

Members
  • Content Count

    64
  • Joined

  • Last visited

Community Reputation

7 Neutral

About MKSheppard

  • Rank
    Rocketeer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Here's a CFG file to add NEXUS to whatever tree. Just do a FIND-Replace and replace the node with one of your choice. @PART[NexusFuelTank] { %TechRequired = advanced_liquid_rockets @description = #$description$ <color=#FF0000>[Tiktaalik's NEXUS]</color> } @PART[Nexus25mShell] { %TechRequired = advanced_liquid_rockets @description = #$description$ <color=#FF0000>[Tiktaalik's NEXUS]</color> } @PART[LF70f-B] { %TechRequired = advanced_liquid_rockets @description = #$description$ <color=#FF0000>[Tiktaalik's NEXUS]</color> } @PART[NexusEnginePlug] { %TechRequired = advanced_liquid_rockets @description = #$description$ <color=#FF0000>[Tiktaalik's NEXUS]</color> } @PART[NexusRCS] { %TechRequired = advanced_liquid_rockets @description = #$description$ <color=#FF0000>[Tiktaalik's NEXUS]</color> } @PART[supermaxiLandingLeg] { %TechRequired = advanced_liquid_rockets @description = #$description$ <color=#FF0000>[Tiktaalik's NEXUS]</color> } @PART[NexusL30AHExpansionDeflection] { %TechRequired = advanced_liquid_rockets @description = #$description$ <color=#FF0000>[Tiktaalik's NEXUS]</color> } @PART[Nexus150fInterstage] { %TechRequired = advanced_liquid_rockets @description = #$description$ <color=#FF0000>[Tiktaalik's NEXUS]</color> } @PART[Nexus150fHeatShield] { %TechRequired = advanced_liquid_rockets @description = #$description$ <color=#FF0000>[Tiktaalik's NEXUS]</color> } @PART[airbrakeNex1] { %TechRequired = advanced_liquid_rockets @description = #$description$ <color=#FF0000>[Tiktaalik's NEXUS]</color> } @PART[fairingSize15] { %TechRequired = advanced_liquid_rockets @description = #$description$ <color=#FF0000>[Tiktaalik's NEXUS]</color> } @PART[fairingSize11] { %TechRequired = advanced_liquid_rockets @description = #$description$ <color=#FF0000>[Tiktaalik's NEXUS]</color> }
  2. How do you represent negative numbers in MM? I'm trying to multiply a number by a negative value (-0.2807) but I can't get it to go negative; even when II start with: NegativeA = 1 NegativeA -= 0.2807 //we have to do this repurposed bovine waste to get a negative number NegativeA = 1 NegativeA -= 0.2807
  3. This one is going into my techtree mod. just ADORE the EVA you made for the 0.625m command pod.
  4. I'm trying to fix some of the exponents used in tweakscale to be more accurate. I've been able to fix engine thrust scaling to be accurate with actual rocket propulsion software with the following code: //This is for engines to fix their size/scaling. @TWEAKSCALEEXPONENTS[ModuleEngines] { %minFuelFlow = 2 //original was set to 2.5 %maxFuelFlow = 2 //original was set to 2.5 %maxThrust = 2 //original was set to 2.5 } But I'm hitting a rock in trying to fix engine mass scaling: //this fixes mass scaling for engines. @TWEAKSCALEEXPONENTS[Part]:HAS[#category[Engine]] { %mass = 2 //original was set to 3 } Doesn't work. Has anyone made a custom CFG that adjusts ONLY engine mass scaling? EDIT: If you want liquid engines to scale correctly; you must use: type = stack_square This correctly scales their mass without the need for a patch
  5. Question. How do you get the APUS Airlock and the APUS Cargo bays to line up in autosnap?
  6. This appears to work in 1.9.1 Here's a CFG file to make you have unlimited parts from the start in the VAB, being limited only by vehicle size and tonnage on the pad, in more logical increments: @CUSTOMBARNKIT { !VAB{}// We nuke the old VAB. VAB { levels = 3 upgradesVisual = 1, 2, 3 upgrades = 50000, 75000, 112500 actionGroupsStockUnlock = 2 actionGroupsCustomUnlock = 3 partCountLimit = -1, -1, -1 } //------------------------------------------------ !LAUNCHPAD{}// We nuke the old LAUNCHPAD LAUNCHPAD { levels = 6 upgradesVisual = 1, 1, 2, 2, 3, 3 upgrades = 50000, 75000, 112500, 168750, 253125, 379688 craftMassLimit = 18, 45, 145, 400, 1200, -1 craftSizeLimit { size = 15, 20, 15 //width, height, length Level 1 Start size = 22.5, 30, 22.5 //width, height, length Level 2 size = 33.8, 45, 33.8 //width, height, length Level 3 size = 50.6, 67.5, 50.6 //width, height, length Level 4 size = 75, 100, 75 //width, height, length Level 5 size = -1, -1, -1 //width, height, length Level 6 } useBuilding = false } //------------------------------------------------ } //END OF FILE This makes you have a launch pad that goes: 18 tonnes (20m height) START 45 tonnes (30m height) Level 2 145 tonnes (45m height) Level 3 400 tonnes (67.5m height) Level 4 1200 tonnes (100m height) Level 5 UNLIMITED UNLIMITED Level 6
  7. Here's a little patch I made to fix a hole in the 1.25m station part list: It converts the PTD-6 Star Utility Module into a combined science-utility module: @PART[sspx-utility-125-1] //Station Parts Expansion Redux 1.0.0 -- 1.25m utility pod { %title = PTD-6 'Star' Science-Utility Module %description = This crewed science-utility module has enough space for the station engineer to poke his head in every once in a while and hope things aren't going *too* wrong. Additionally, it contains provisions for a scientist to do a small amount of research. %category = Science MODULE { name = ModuleScienceContainer reviewActionName = #autoLOC_502204 //#autoLOC_502204 = Review Data storeActionName = #autoLOC_502202 //#autoLOC_502202 = Store Experiments collectActionName = #autoLOC_238018 //#autoLOC_238018 = Take Data evaOnlyStorage = True storageRange = 0.5 allowRepeatedSubjects = True } MODULE { name = ModuleScienceLab containerModuleIndex = 0 dataStorage = 50 crewsRequired = 1 canResetConnectedModules = True canResetNearbyModules = True interactionRange = 5 SurfaceBonus = 0.1 ContextBonus = 0.25 homeworldMultiplier = 0.1 RESOURCE_PROCESS { name = ElectricCharge amount = 10 } } MODULE { name = ModuleScienceConverter dataProcessingMultiplier = 0.5 // Multiplier to data processing rate and therefore science rate scientistBonus = 0.25 //Bonus per scientist star - need at least one! So 0.25x - 2.5x researchTime = 7 //Larger = slower. Exponential! scienceMultiplier = 5 //How much science does data turn into? scienceCap = 25 //How much science can we store before having to transmit? powerRequirement = 2.5 //EC/Sec to research ConverterName = #autoLOC_502055 //#autoLOC_502055 = Research StartActionName = #autoLOC_502056 //#autoLOC_502056 = Start Research StopActionName = #autoLOC_502057 //#autoLOC_502057 = Stop Research } MODULE { name = ModuleKerbNetAccess MinimumFoV = 17 MaximumFoV = 63 AnomalyDetection = 0 DISPLAY_MODES { Mode = Terrain,#autoLOC_438839 //#autoLOC_438839 = Terrain Mode = Biome,#autoLOC_438890 //#autoLOC_438890 = Biome } REQUIRED_EFFECTS { Effect = ScienceSkill } } MODULE { name = ModuleExperienceManagement costPerKerbal = 0 } }
  8. Some help for when you click on WRITE NODE DATA If your cfg file is named KWCS_Nuclear_Pack.cfg it outputs into KWCS_Nuclear_Pack_NH.cfg in the same folder.
  9. Specifically, the data for each level of KSP facility, i.e. Level 1 launchpad is 18 tonnes, level 2 is 140 tonnes, etc... I tried a brief look through in the folders, and then tried searching the forum, but can't find it easily.
  10. If Atlas expansions make you hard; there's a guy who worked on Atlas (his first launch was in about '85) who is compiling drawings of the proposed Atlas variants over here at: https://forum.nasaspaceflight.com/index.php?topic=26915.0;all You have to go all the way down to get to the interesting stuff.
  11. “Fat Core” Titan III Proposals Note: The name comes from an Aerospace Technology article on 29 January 1968, which went: Asked what he foresaw as the launch vehicle beyond an uprated Titan III-C (Titan III-M, seven-segment solid rocket motors and a stretched first stage), Col. Taliaferro said: "That is about the extent of the growth potential of the present Titan III. Beyond that, if and when a firm requirement exists for a booster in the 50,000 to 100,000 lb. payload class, I like the fat-core Titan with optimized 156-in.-dia. solid rocket motors." Col. Taliaferro defined "fat core" as a Titan III vehicle with the diameter extended to 156 in. Four of the current Aerojet liquid-fuel engines are clustered and fed from common tankage. Martin-Marietta Corp. has funded an in-house effort of this nature for some time and such a vehicle has been well defined. TITAN IIIG: "The Titan IIIG has a 15 ft. diameter core with a 4 engine first stage, and can use 7-segment 120-inch or 5-segment 156-inch diameter SRM. Low earth orbit payloads up to 100,000 lbs are claimed. Martin has generated a serious sales effort to sell this vehicle in competition to the Saturn derivative intermediate family (e.g., INT-20)." Selected Comments on Agena and Titan III Family Stages, Case 720; 26 March 1968, Titan III Large Diameter Core (LDC) Family (aka Titan IIIL) Notes: This family was proposed from mid-1971 onwards by Martin Marietta. It would have increased the core stage diameter up from the existing 10 feet (3m) and would have used a varying number of UA-1207 SRMs developed for the Titan IIIM program.
  12. Found some data on the Titans for you. ABOVE: standalone Titan IIIL. BELOW: Titan IIIL as Space Shuttle Booster:
  13. Any chance a properly kerbalized Navaho series of engines could be done? They form the "missing link" between the early V-2 style engines and heavily simplified (Redstone) engines and the Atlas/Thor/Delta engine configurations. The Navaho engines were: Navaho Phase I Notes: Two German-built V-2 engines were reconditioned for this phase, which consisted of taking the engines and operating it with water substituted for propellants at flow rates corresponding to 56,000 lbf of thrust for 64 seconds. Rocketdyne XLR-41-NA-1 (Navaho Phase II) Notes: Simplified V-2 engine made from US-built parts and built to US pipe size and fitting standards. Was water-flow tested, and as it was ready to be hot fired; the program was cancelled in favor of hot testing the early US-designed thrust chambers that would eventually lead to the Redstone NAA-75-110. Rocketdyne XLR-43-NA-1 (Navaho Phase III) Propellants: LOX/Alcohol-Water 75% Thrust (sl): 75,000 lbf Chamber Pressure: 300 psia Rated Lifetime: 60 seconds Notes: Developed for Navaho missile booster which would push the missile to Mach 2.85 at 38,000 feet before burnout. Test fired ahead of schedule in May 1950. This engine formed the basis for the Redstone’s NA 75-110 A-1 to 7 engine. Rocketdyne XLR-43-NA-3 (Navaho Phase IV) Propellants: LOX / 92.5% Alcohol, 7.5% Water, Gas Generator Thrust (sl): 120,000 lbf at 230 ISP Dry Weight: 1,230 lb T/W (sl): 97.5 Notes: First US engine to use “spaghetti” (tubular wall) configuration for the thrust chamber, which reduced weight by 50%. A high speed turbopump was developed for this engine which used a gas generator that was powered by the propellants themselves, eliminating the need for a separate hydrogen peroxide tank to run the turbopump. Rocketdyne XLR-71-NA-1 (G-26 Navaho II / Navaho Phase V) Propellants: LOX / 92.5% Alcohol, 7.5% Water, Gas Generator O/F Ratio: 1.375 Thrust (sl): 240,000 lbf @ 229 ISP Thrust (vac): 278,000 lbf @ 265 ISP Chamber Pressure: 438 psia Dry Weight: 2,501 lbs T/W Ratio (sl): 95.96 T/W Ratio (vac): 111.15 Engine Length: 117 inches Engine Diameter: 77 inches Expansion Area Ratio (ε = Ae/At): 4.6 Rated Lifetime: 65~ seconds Notes: “Doubled up” version of XLR-43-NA-3 with two thrust chambers. This engine proved the feasibility of running two separate thrust chambers fed off a single common gas generator, but retaining separate turbopumps. First test fired September 1953. Rocketdyne XLR-83-NA-1 (G-38 Navaho III / Navaho Phase VI) Thrust (sl): 405,000 lbf @ 245 ISP Propellants: LOX / JP-5 Rated Lifetime: 93 to 100 seconds Notes: “Tripled up” version of XLR-43-NA-3 with three thrust chambers and modified with better cooling to allow the burning of hydrocarbon fuel. Each thrust chamber had it’s own turbopump, but all three chambers were fed off a single common gas generator. First fired January 1956. Navaho Engine Development in Retrospective Despite the program being canceled before any operational missiles could be deployed, the Navaho engines helped rocket technology in the United States take a dramatic leap forward. Instead of a simple welded sheet metal thrust chamber (Redstone and earlier), Navaho pioneered the brazed regeneratively cooled tube wall thrust chamber. Additionally, instead of using HTP to drive the engine turbopump, a bipropellant gas generator which used the same propellants as the engine itself was used; eliminating run time limitations imposed by HTP tank sizes. Finally, the Mark 3 turbopump which was used in various forms on the Thor, Atlas, and Saturn I/IB engines was introduced with Navaho. ************************************** Essentially, you don't need to do all of these engines; just Navaho Phase IV / Navaho Phase V / Navaho Phase VI; which are basically "lets add more combustion chambers for MOAR THRUST".
  14. Martin had many many "fat core" Titan projects proposed. Titan IIIG was the first, and would have been a 180" diameter core and would have had option of two UA-1207 or UA-1565 (156" diam 5 segment SRM) boosters, and would have had four engines. No idea if these were stock LR87s or the 'cut down' single chamber LR87s of only 226 klbf used in Titan IIIL-1207-4 (Spread). Titan IIIL-1207-4 (Spread) had a 192" core and would have been the booster for the Grumman H-33 Shuttle Orbiter. Titan IIIL 2/4/6 (Straight) had a 196" core. Titan IIIM (LDC) (LDC = Large Diameter Core). Will edit to add more information.