• Content Count

  • Joined

  • Last visited

Community Reputation

624 Excellent


About Aelfhe1m

  • Rank
    Inveterate Tinkerer

Profile Information

  • Location Array

Recent Profile Visitors

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

  1. Basically yes. Each Kerbal needs 4 nom-o-matic 5000 type greenhouses to keep them supplied. (Well they actually only need 3.78 each but you need to round up the total so that supply exceeds demand, e.g. 3 Kerbals need 11.4 greenhouses - rounded up to 12). Also note the small greenhouses don't benefit from having a specialist in the crew for improved conversion efficiency but some of the MKS agroponics parts do which can be taken into account when designing a larger vessel.
  2. It's all defined in ModuleManager patches so it should still be fine. The change to science labs is applied to specific named labs only so only some mod added labs are affected.
  3. Your Kerbals are using the supplies faster than the greenhouses are producing them. Assuming you haven't changed the default rates then each Kerbal turns 0.0005 supplies into 0.0005 mulch per second (0.0015 /s for 3 Kerbals). Each Nom-o-matic 5000 takes 0.00012 mulch and 0.00012 fertilizer to produce 0.000132 supplies (0.000528 /s for 4 greenhouses). That's a shortfall of 0.000972 supplies per second. So your Kerbals drain the supplies down to zero (slowed somewhat by the greenhouses producing some replacements). Then once it hits zero then each time KSP updates the resources the greenhouses make a small amount which immediately gets gobbled up by the Kerbals putting the supplies back to zero.
  4. Each docking port in KSP is defined in a ModuleDockingNode section of the part's config. This includes a referenceAttachNode field that names which node (also defined in the part config) should be used to dock to. The orientation of that node defines the roll axis and I believe that DPAI uses the Z+ direction as the zero point.
  5. Since the normal goo experiment doesn't care whether it's on the surface or not (and I can't see anywhere JNSQ modifies that) it sounds like you've got an interaction with some other mod.
  6. The patch seems to be outdated for the current Kerbalism patching mechanism. It tries to apply updates to the habitat modules during the :AFTER[Kerbalism] ModuleManager pass but the Kerbalism patches don't create that module until the later :FOR[KerbalismDefault] step. All the other patches in the same folder (PlanetaryBaseInc/ModSupport/Config/Kerbalism) use the :FOR[PlanetarySurfaceStructures] pass which would work for this purpose as well. I suggest (untested) changing the patch to be: Looking at some of the other patches in KerbalismConfig/Support for the likes of HabTech and SSPX which are both space station type habitat parts there may be need to add some additional patches for other life support systems (CO2 srubbers, recycler, sabatier processors etc.) to the KPBS parts but I haven't gotten far enough in the Kerbalism career game I'm currently playing to have a proper feel for what might be needed.
  7. Tourism+ only disables the stock tourism contracts. It could be that another contract pack/mod is disabling the stock "recover asset" contracts or that you haven't yet met the stock requirements for the contracts to appear (can't recall offhand but you may need to unlock manoeuvre nodes before rescue contracts are offered?) You can check which contract types are enabled in a particular save by loading it then choosing settings in the pause/KSC menu; clicking on the difficulty button at the top of the settings dialog and then the Contract Configurator tab. You will see a column of radio buttons representing the contract packs and another column representing stock contracts (and mod added contracts that use the stock contract method). As I mentioned earlier the rescue contracts are grouped under the "RecoverAsset" option in the stock contracts column so make sure that is enabled.
  8. Hi, the AGX dialogs in the screenshot you posted looks like what I would expect to see when you've unlocked "basic" action groups (first VAB upgrade) but haven't yet unlocked "custom" action groups (second VAB upgrade). The Abort group shown in the picture has fewer editable options than the numbered custom groups. What does look wrong in the picture (and when I did a quick test myself) is that the stock action groups panel is showing custom groups available when they shouldn't be. I normally don't see this since I enable the "Always allow action groups" option on the difficulty settings advanced whenever I start a new career save.
  9. Look in the first post of this thread. Waypoint Manager is what you want.
  10. You'll need to "roll back" to an older version of KSP (1.7.3 or 1.8.1 are good choices for JNSQ): Just make sure to pick the correct version of each mod you install to match the version of KSP you're using. (Or you could just wait until Kopernicus is updated for 1.9.1. No idea when that will be though).
  11. Create a new ModuleManager patch file containing the following: CC_EXPERIMENT_DEFINITIONS { name = SSPX EXPERIMENT { name = sspxFishStudy ignored = true } EXPERIMENT { name = sspxPlantGrowth ignored = true } EXPERIMENT { name = sspxVisualObservation ignored = true } } That will cause Field Research to ignore the three experiments introduced by SSPX when generating contracts.
  12. MM allows the use of folder paths in NEEDS (added in version 3.0.7) so CC-core and CC-full could be distinguished based on the presence or absence of theConfigurableContainers/Parts folder (at least based on the way they are configured in CKAN)
  13. Obvious question but are you dragging the items from the part list to the KIS inventory panel? KIS doesn't use the click to pick up/click to place that the rest of the editor does.
  14. In CKAN go to the Settings menu and "Compatible KSP Versions" and check the boxes for 1.7, 1.6, 1.5 and 1.4 that will tell CKAN that you want to allow it to install older versions of mods. For KSP 1.7.3 most, but NOT all, mods released for the 1.4 to 1.7 versions of KSP are usually compatible - always check the mod's forum page for any information about compatibility. For 1.7.3 you should never try to install a 1.8 version of a mod. There were a lot of changes to the way KSP works with plug-ins between versions 1.7.3 and 1.8. The only exception would be pure part mods with no plug-in DLL which MAY work depending on how their shaders are configured.
  15. To plan for the return trip then yes you generally read the DV map backwards but there's no need to include all the values all the way back to Kerbin since you can take advantage of Kerbin's thick atmosphere to aerobrake for capture and re-entry and ignore any legs with the little arrow symbol pointing towards Kerbin. Launching from a planet's surface back to low orbit should take the non-aerobrake DV listed for landing (1450 m/s for Duna and over 8000 m/s for Eve). For a return from Duna orbit the DV is thus about 360 + 250 + 130 (+ up to 10 plane change). A return from Eve orbit would be 1300 + 80 + 90 (+ up to 430 for plane change) Note for going to and returning from other planets timing is very important. You want to make sure the angle between Kerbin and your target planet is correct for both legs (see for a helpful online guide for eyeballing the angles). If you don't make your transfer at the right time it can cost a LOT more DV than shown on the chart. There are also some tutorials you might want to check out on the wiki section of this site: