Jump to content


  • Posts

  • Joined

  • Last visited


836 Excellent


Profile Information

  • About me
    Inveterate Tinkerer
  • Location
    Third star to the left

Recent Profile Visitors

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

  1. You're problem might be because the dependency "Recovery controller" is still marked as KSP 1.12.2 max on CKAN so FMRS does not show up as compatible with 1.12.3 on default settings. In CKAN, go to Settings -> Compatible game versions and enable the checkbox for 1.12. When you refresh the list, FMRS should be available to install
  2. Not really surprising since the thread is 8 years old and the site gets redesigned and moved to newer forum technology ever now and then. To get you started try searching for "Stockalike" in the Add-on releases forum: https://forum.kerbalspaceprogram.com/index.php?/search/&q=stockalike&quick=1&type=forums_topic&nodes=34&search_in=titles
  3. @linuxgurugamer You could pre-patch with a default value where an existing value is missing: @PART[*]:HAS[!MODULE[ModuleCargoPart],@MODULE[ModuleInventoryPart],!MODULE[KerbalEVA]]:FINAL { @MODULE[ModuleInventoryPart] { &packedVolumeLimit = 1 // & means add value only if not already present - you can use a different default if 1 isn't appropriate } } // rest of patch as before @PART[*]:HAS[!MODULE[ModuleCargoPart],@MODULE[ModuleInventoryPart],!MODULE[KerbalEVA]]:FINAL { MODULE { name = ModuleCargoPart packedVolume = -1 } MODULE { name = ModuleInventoryPart InventorySlots = #$/MODULE[ModuleInventoryPart]/InventorySlots$ packedVolumeLimit = #$/MODULE[ModuleInventoryPart]/packedVolumeLimit$ } MODULE { name = KSPPartVolumeModule } !MODULE[ModuleInventoryPart] {} } You could also use @MODULE[ModuleInventoryPart]:HAS[~packedVolumeLimit[]] on the first @PART clause to filter only for ModuleInventoryPart modules without packedVolumeLimit values but using the & makes that mostly redundant (might save a little processing time and reduce total patch count)
  4. No but you can export the current blocked list and then import it to another save. (Permaprune does apply across saves)
  5. Only by changing which body is the HomeWorld. You can't define KSC locations on multiple worlds. If you do want to change which world is the "HomeWorld" then you could look at how Alien Space Programs does it:
  6. While you can add the statics for launch pads to other planets with KK, the "launch sites" feature only works on the current HomeWorld. If you want to launch newly constructed vessels from another world you'll either need to change which world is the HomeWorld or use a different mod:
  7. I thought that at first but confusingly it didn't work. After checking the source code I found that the fields were named differently between the two mods. e.g. diameterStepLarge (PF) vs diameterLargeStep (PP)
  8. Here's the equivalent patch for Procedural Fairings: @PART[*]:HAS[@MODULE[ProceduralFairingBase]]:AFTER[ProceduralFairings] { @MODULE[ProceduralFairingBase] { %diameterStepLarge = 0.625 %diameterStepSmall = 0.15625 } }
  9. Missing parts will always break craft, so if you use the rover controller part on your rover it will break if BV is uninstalled. However if you use a MM patch to add the module to an existing rover part then you will only get a "Missing module" warning that can be safely ignored in most cases.
  10. I'm trying to figure out how to apply local HiRes decals to launch sites (like RSS Canaveral HD does) but I could use some help. I downloaded a set of high res. images from USGS and stitched them to form a surface patch. Cropped it and scaled to 8192 x 8192 px and also created a lower res preview at 1024 x 1024 px for fiddling about with fine tuning the positioning. I used the following MM patch to try to apply it to the surface but nothing is showing up (or at least not where I expect it to show up)
  11. I'd suggest using KerbalKonstructs.Core.LaunchSiteManager.getNearestBase to find the nearest KK base.
  • Create New...