Enorats

Edit: Found the answer. Altering the "Gameseed" value under ResourceScenario in persistent.sfs rerolled the entire system's resource distribution. Not quite what I wanted but as I have no other land bases just yet to worry about displacing with the nuclear option, it got the job done. I'm sure this has been answered before, but I can't for the life of me seem to be able to find anything on it. I'm using Kerbalism and scansat, and trying to set up a fuel refinery on the Mun (I'd use Minmus, but I despise super low gravity worlds, they make bases and rovers just.. unfun). Problem is, with Kerbalism if you don't have access to water you're basically SOL.. and scansat is telling me that there is no water anywhere near the poles where I'd like to set up shop (permanent sunlight). In fact, the only water is more or less at areas between the equator and poles.. making it less than ideal. I'd like to change that, but I can't seem to find anything that screams "alter this to add water to Mun's polar lowlands!" I assume it's in the save file, persistent.sfs. I've found a section for the Mun, with a SCANResources bit.. but it's all nonsense to me. Is this what I'm looking for, and if so.. what would I need to change to add water to the Poles and Polar Lowlands?

Not sure what is causing this, but I noticed that when I'm building a craft in the VAB everything works fine.. until I add a greenhouse. The moment I click the greenhouse in the part menu my FPS drops down to a stuttering mess. Playable, but quite annoying. Discard the greenhouse, and it goes back to the normal smooth FPS. When loaded onto the launchpad it's better, somewhat. The difference between having a greenhouse and not is noticeable but not quite cringe-worthy. I've a pretty powerful PC (it's set up to run a Vive), and it normally handles KSP just fine.. so I can't help but think something must be wrong with this particular part. Edit: Just to be clear, it's the planetary greenhouse I'm having trouble with. The little greenhouse container (and kerbalism's greenhouse) work just fine. Edit 2: Oddly, today the part seems to be working fine. Nothing changed, so I'm not sure what was causing the problem before. In fact, where before it was causing massive lag as the only part loaded.. now I've got it sitting on a 2 million ton 146 part rocket with no problems at all. Though, now that I think about it I did change one thing (not that it's necessarily related). I disabled Kerbalism's part failure module because I got sick of pieces I couldn't possibly replace on my station having critical failures (or high quality solar panels that are supposed to last 20 years failing en route to minmus).

One trick that I've found that makes docking super easy is to have one vessel face radial+ (away from planet) and the other radial- (towards planet). Mechjeb does a great job with this, but even the stock game's SAS works. Target+/- works too.. but things start wobbling as the two vessels get closer. Radial+/- changes very slowly as you orbit, and is unrelated to vessel seperation distance. You can then rotate the vessel to whichever orientation you want, and you've eliminated any problems with the docking ports not lining up because you've already put them in the same plane. Then you just move "up/down, left/right" to move the little purple "target" circle to the center of your nav ball, and then move the green prograde circle there too.. now you're lined up and just have to move forward with minute adjustments as you get closer and the navball predictions get more accurate.

Well, I'm fairly certain anything I send up is going to work.. but for me, it's Max-Q. It's hard to be sure everything will fly correctly at that point. Switching to a landed base or time warping at one is also stressful because there's a high chance it'll just blow up. Biggest flaw in the entire game in my opinion.

Adding storage should be easy enough. Just find a KIS part with storage, look through its .cfg (using a text editor like notepad) for the module that adds storage to the part, then copy that whole bit and drop it into this part's .cfg file. Edit the volume to your liking, save and play.

Depends on what body you set them up on, like all science. If memory serves it's about what the experiments on your standard stock mun lander would net you, so maybe doubling the science gain from each "landed" biome.. minus surface samples. Personally I find they fit in well with the community tech tree, NEOS (an orbital experiment pack similar to this), and Kerbalism (which eliminates science lab science generation). That, and it feels more like "gameplay" than simply go here, press button to get science, go home. In more stock-ish games I tend to stop using most stock science entirely (to keep some challenge) and just rely on this and some of the other science mods that have better gameplay value.

I'm in 1.3 KSP, and the KerbalHealth.version file says 0.6.4.0. As for steps to reproduce, I'm not sure. I just copied my stock KSP game, dropped in mods from my mod game (except for USI-LS) and put kerbal health in instead. Mostly using BDB parts, if that matters at all. The station was entirely out of BDB lab/hab units, and the apollo mission was using their Saturn V remake minus the ullage motors. The mission was an apollo lunar rendezvous profile, that went fine until I realized Val had all but died.. and a bug caused by BetterTimeWarp started screwing with my orbits and rendezvous nodes. Their lossless physics option is.. experimental. That caused me to miss several intercept attempts, leading to several phasing orbits to line up others.. and Val's demise. As for the demise of the entire station crew and LEM crew upon docking following hyperediting them home.. I can't begin to imagine what happened there. I'd offer logs, but I deleted that install of KSP after settling on giving Kerbalism a go in my next playthrough.

The landing legs are insanely useful on larger landers. They're heavy, but when you're landing a 50 ton cryogenic lander that's half the height of the VAB on its own.. then they're worth it. The superdraco engines are so much more fun than parachutes, but landing can be a pain. Might be able to trick the stagerecovery mod into autorecovering the capsule as a "spent stage" though.. Carrying what would normally be discarded service module engines home can be financially effective.

How about rescale mods like Sigma Dimensions? I'm playing a 2.5x stock system, could I drop this in and have my Duna replaced by a 2.5x version of this Duna?

In my 2.5x rescale stock system, Kerbalism isn't displaying the radiation belt overlays. Am I correct in assuming the issue is due to the rescale, or is there some toggle I'm missing to show them? The belts appear to work fine, and radiation hits at the appropriately higher altitude.

Not sure if anyone's noticed this.. but the chemical plant has some issues with physics. Namely, conservation of mass. The gases are all really light weight, so anything that turns gas into a liquid (especially fuel) just destroys physics. For example, I created a simple test vehicle consisting of a big orange tank, some landing legs, an engine, a constant power source (itinerant service module I believe it was, from near future?), a chemical plant turning hydrogen/oxygen into oxidizer, and enough hydrogen/oxygen tanks to give me a bit more than what I'd need to fill the oxidizer on the orange tank. At the start of the test my vehicle weighed around 27 tons (the liquid fuel was still full), and after 110 days (with just one chemical plant) it weighed something like 52 tons after converting all the gases to oxidizer and filling the orange tank. Now, this means I could upper stages totally empty of fuel but with a chemical plant and some gas tanks, then fill my oxidizer en route or in a parking orbit, halving my payload mass at launch. Liquid fuel can be similarly produced, with water as a byproduct. I haven't tested if monopropellant production is advantageous though, but again it converts oxidizer to mono/water.. and oxidizer can be made from super lightweight gases. Altogether, the combination of these processes can be used to launch a vehicle into orbit that weighs a tiny fraction of what the final product will, though the entire process is self contained. This seems.. wrong.

I was afraid it was something like that. Kerbalism pretty much tells the stock science system where it can stick it.. or, well maybe not in this case. I'll probably just disable that module for now as it doesn't play entirely too well with other mods in general. KIS activity of any kind on a vessel carrying science data totally erases all that data, and I'm a bit worried it's not going to play nicely with the surface experiment pack either.

Not sure what's going on here, but the "analyze science" button doesn't seem to do anything. I drive up to a red dome, it turns green.. the button appears, but when clicked nothing happens. I'm using the Kerbalism mod too, anyone know if that could be interfering with Rover Science somehow? It changes a bit about how science is collected.

Interesting. Unfortunately that doesn't help with the KEES experiments as they work a bit differently as one time use experiments that aren't really meant to be "removed" at all. I like how they interact with kerbalism in that I can "remove" the data and process it in a lab instead of actually returning the experiment to the surface, but if the data disappears as soon as I collect the experiment with KIS then they won't work at all. Suppose I'll just have to keep this in mind and maybe place the components on pieces that I'll be decoupling anyway, that way I won't need to remove the experiments at all. A bit of experimentation and I might come up with a workable solution. Edit: "Finalizing" the KEES experiments so that Kerbalism removes the data and puts it in the pod, then EVA'ing a kerbal and having them remove the data from the pod before disconnecting anything with KIS will prevent KIS from destroying the data stored in the ship.. because the data isn't stored in the ship anymore. Unsure if putting something in the kerbal's inventory will do anything though, as I used my scientist as the data holder (floating off in space) while the engineer did renovations.

It seems that this mod removes all the orbital level biome specific stuff. EVA's from low orbit no longer have a biome specific experiment either, instead only a single "above the Mun" EVA needs to be done. This seems to drastically reduce the science you get from anything that isn't a landing, but that's okay by me because it balances out all the other science mods I use like bluedog design bureau's multitude of experiments.

I'm having the same issue myself. Spent a half hour trying to set up an Apollo style Mun intercept I should have been able to do blindfolded and asleep with one arm tied behind my back, and eventually my poor kerbals expired from lack of life support after a dozen failed intercepts. It's not just the nodes that are having problems though, orbits actually change too. If I burn for the Mun and get a 60 km periapsis (as an example), as soon as I stop burning the periapsis starts dropping as though I'm still in Kerbin's atmosphere. Within about 10 seconds it had dropped to 57 km, though it froze once I time warped and remained stable after I entered the Mun's SOI. At that point my trajectory outside Mun's SOI started changing instead.

Damn, I'm having this same issue myself and it's driving me nuts. It's not just the maneuver node that's changing though, any intercepts and the like outside of your current orbit actually change too. For example, I might get into a stable orbit around Kerbin then burn to get a Mun intercept that'll pass me by with a periapsis of 60 km. After I've finished the burn though that 60 km slowly drops to 59.. 58.. 57.. over about 10 seconds. If I time warp, it freezes.. and once I'm within the Mun's sphere of influence it goes back to being stable again (though my trajectory beyond the Mun's SOI will now begin changing). Something about that mod is preventing the game from accurately predicting course alterations - everything works fine until you ask the game what'll happen when you take the ship off rails.

Not entirely sure what is going on here, but I keep going EVA and then losing all the science data in my pod when I reenter. I've got a dozen different "data files" from various instruments/reports/eva's as well as a few "samples" from Nehemia Engeering Orbital Science experiments (the KEES experiments). I go EVA to disconnect a KEES experiment from it's holder and put it in a KIS container (they don't survive reentry in the zero-g experiment racks by design), and when I get back in the pod all my science data is entirely gone. It's happened two or three times now. Not sure if this is a conflict with the KEES experiments (which have been giving me tons of trouble with lots of mods due to how they have to be "recovered" to actually get science and require time for the experiment to complete in orbit), or if this is unrelated. Anyone ever have an issue like this?

So, I like the idea of this mod because I absolutely hate how the stock game punishes you for building reasonably realistically instead of putting a kerbal in an external command seat for a 10 year trip. I've used USI-LS for a long time because of that, but it has some major shortcomings when it comes to landers and transfer vehicles.. namely, when you get to your destination and undock the lander, everyone up and throws in the towel because suddenly they don't have a cot to sleep in for a few minutes. This mod solves that wonderfully.. but I'm having some major problems with it. First, I had to turn the EC requirements down to something like .1 per kerbal/sec because early game batteries just cannot support a station on the night side of Kerbin without hundreds of batteries. Trying to build a skylab type station with some Bluedog Design Bureau parts, and finding that you need dozens upon dozens of batteries to prevent the life support from shutting down a quarter of the way through the night isn't fun. Another issue is that the calculator doesn't appear to accurately calculate health drain when a ship isn't focused. If I have my station focused, my kerbals settle in around 65% health and stay there.. slowly gaining and losing health due to the marginal gain granted by 4 cupolas. However, if I go to another ship or KSC and time warp.. they don't get their marginal gain at all. So they die. I also just had a very strange issue where I was doing an apollo style mission. Val stayed behind in the command pod, and two others went down in the LEM. They're a day into the trip (using a 2.5x scale system) on descent, and they more or less ascend again a few minutes after touchdown. I encountered a very strange bug unrelated to this mod that has my maneuver nodes and intercept distances constantly changing (no clue what is doing that, but it's making what should be an intercept I can do in my sleep utterly impossible) and after missing like a half dozen intercepts and having a couple days pass I look at my command pod and see that val is exhausted and for some reason has a health drain of -46. She promptly died, and I reloaded.. focused the command pod, and now she's got a -2.67 drain.. However, now that she's so badly injured she won't survive the trip back. The other two actually have a twice the drain she does (they're at -6 in the LEM) but they're still at half health while Val's almost dead. Finally gave up and used hyperedit to just bypass this strange intercept bug (seriously.. my apoapsis/periapsis on both vessels is totally steady, but after setting up a maneuver node to give a close intercept it immediately starts changing, the delta-v on the node goes up and down and the intercept distance just keeps rising). Anyway.. docked the two vessels, and Val has like 5 health left. Transfer one of the LEM crew members to the command pod and Val immediately loses her last 5 HP and dies instantly. No clue what happened there, transferring another member over shouldn't do anything to her current health level at all.. just the drain on it over time. I'd have thought that she'd actually have a lower drain too since she wasn't alone anymore. And another very strange bug. To save Val from this strange bug, I just hyperedited her home. I then did the same to my LEM, though the plan was to dock it with an orbital lab to process the data in LKO. I did so, and my both crew members on the LEM promptly died the moment I docked, even though they were at half health and the other four crew members on the station have happily lived there for a year.

Yeah, I know that over long periods of time I should slowly drift out of alignment as Kerbin orbits. It should only be something like 360/ (days in a kerbal year) degrees per day though. Since Kerbin takes well over 400 days (450 something maybe?) I should be seeing less than a degree per day of alignment loss. Instead I'm seeing 20+ degrees every time I go around Kerbin. It seems the problem gets worse the higher the timewarp gets too, if I keep it at a lower time warp I only see a couple degrees per orbit. That's still an order of magnitude more rotation than I should see though, as an orbit only takes less than an hour (1/6 of a day, so I should see (360/(days in kerbal year))/6) at my altitude. If I use the higher time warps granted by the Better Time Warp mod (which lets you warp faster near bodies) it gets absolutely insane. I like that solution though Streetwind. I'll have to give that a try.

So, I'm trying to wrap my head around this and totally failing. All logic tells me that this shouldn't be happening, or well.. it should, but not remotely at the rate that it is. Here's the issue: I'm using Kerbal Health as a "life support" type of mod. Even with the power drains cut in half in the .cfg's it's still utterly insane and I should probably cut them down to more like 1/10th. My station is currently powered by six mod solar panels from BDB that are similar to the large stock ones, but smaller and slightly weaker. I rotate my station to point the panels at the sun at 100% exposure. As I orbit Kerbin I expect that my panels will stay at that same exposure, as my ship should not rotate in its orbit - there is no force acting on it making it rotate. Eventually, after enough time passes Kerbin will move far enough in it's orbit that I'll slowly need to adjust my orientation, but that should only require something like half to three quarters of a degree a day. What I'm finding though is that when I time warp I stay around 100% exposure, then drop behind Kerbin.. and when I come back to the day side I'm only at ~80%.. go back around to night, and on day side I'm at 50%.. then 20%.. With each "sunrise" I've somehow rotated ~20-30 degrees for no apparent reason, causing my solar panels to fail to recharge my batteries I go back to the night side, causing my life support systems to fail. Now, am I right in assuming that this is not supposed to happen? Thankfully the simple solution of just putting more batteries and panels facing in the other two directions as well takes care of the issue.. but this uber-fast complete 360 rotation in a day thing is breaking the part of my brain that thinks about physics.

I just had this same issue, not sure what the problem is yet but I got to the Mun and went to deploy surface experiments only to find my kerbals only have a 1 liter inventory. Will investigate further I suppose. Edit: Guessing I figured it out. My KIS and KAS were still in their um.. packaging? I dropped the entire KIS (version number) / Game Data / KIS etc folder into the Game Data folder instead of taking only the stuff inside. Oops.

Well, that was interesting. In a last ditch effort and attempt to see if I could replicate my eternal darkness problem with an otherwise mod-free game I copied my game folder and then proceeded to remove all but Kopernicus/Sigma. No problems encountered. Put mods back in a few at a time until they're all back in.. and still no problems. Not quite sure how copying everything, ripping it all out, then putting it back in fixed the sun.. but my sun is now shining again. Did I void the warranty?

I think they had micrometeorite impacts, radiation detection, and a camera.. so BDB already has the parts needed in that regard.

Lol, it's kinda sad that I knew what that was just based on the pictures and that this mod is recreating Apollo era architecture. Then again, I suppose there weren't all that many things it could have been.