disembodied

Can you make it possible to edit the UT by clicking and typing in the box? Also, a +1 orbit/-1 orbit button would be really handy.

The Isp and thrust values are wrong. Looking at KER without the mod, this silly craft should have a starting TWR of 2.02 at Duna sea level - 758.1 Isp and 56.858kN thrust. edit: eh, you had already mentioned that in the OP. Oops.

1. The radiators drain electricity. You don't need even a single radiator for that ship. 2. Loading the ship up into KER shows it as having 7353 dV, which is more than enough to land and return from Mun. 3. The ship is slightly unbalanced because of that mystery goo, but probably not enough to cause issues. More importantly, those radiators create a lot of lift and drag above your center of mass, which makes the ship flip happy. Put fins on the bottom, get rid of the radiators at the top. EDIT:You also put the heatshield on wrong. It has to go to the bottom of the stack, otherwise everything below it will likely melt. Hilariously, your craft manages to avoid the problem by having another one - namely, those radiators. On reentry, the capsule flips parachute-first and they manage to cool the capsule and parachutes off just enough that they don't explode. It flips because the heatshield is above the science junior with no decoupler between them, so the center of mass is toward the top of the craft. I'd suggest leaving the science jr. with the lander stage, collecting the science on EVA and reentering Kerbin with a simple parachute/capsule/heatshield combo. Here's a simple guide: Get your ascent speed close to 100 m/s, then tip the rocket over 5 degrees east, wait for the prograde marker to start dropping and follow it without deviating from it during the first ~30 km, or your ship will do more somersaults.

[quote name='Person012345'] What's going on here, why won't this thing complete?[/QUOTE] Look at the moving dots around the orbit. Is your craft traveling in the same direction as they are? If not, there's your problem.

[quote name='Arsonide']The only change to Explore contracts in the latest version is that they were reeled in a bit. In the last version they could target three planets ahead of the player, meaning the moment you orbited Kerbin, they could target Duna and Eve. I scaled this down to two planets, so that they should only be able to target Kerbin's moons initially. The rewards have not been modified at all.[/QUOTE] Hm, odd. On a new career, I never did get the "Explore Mun/Minmus" contracts - it gave me Duna, Ike, Eve, Gilly, then Jool and its moons. The only Mun/Minmus related ones I got were fly by and orbit and at some point it started asking me to plant flags there.

Is there a way to make the "time to node burn" time be calculated in 6h days, rather than 24h?

If I enable it and then go back to the space center, it always seems to default to "off", so I have to enable it every time.

KSP shows the date as Year 2, day 88. Precise node shows it as Year 1, day 88. It makes using transfer window planner with it... problematic.

Engineer is calculating how much delta V you have with a fairing, but it doesn't show you how much you'll be left with after staging it before you actually launch and stage it.

Bug report - solid rocket fuel burns out over twice as fast as it does without this mod installed.

Thank you for this mod. It's a very welcome addition.

Yeah, I didn't think they were affected while on rails. Having to take care of every single ship you launched every couple of months manually might become annoying, though. If you do implement them, maybe have manned vessels automatically use their spare parts for maintenance whenever it's necessary while you're not paying attention to them, with some pop-up message when they start running low on spare parts? Some way of checking the status of unmanned ships while not focused on them (but with some randomness, so you don't always know for certain when something's about to break) might be nice, too. Not sure how/if those would work. Just a thought. Keep up the good work, by the way. I'm enjoying the mod. I wasn't all that interested in something that randomly damaged your rockets before, but after I tried it it pretty much changed the way I was building rockets. I'm a lot more cautious when launching now and I finally have a use for that stock launch escape system, in case my rocket decides to do its best Proton-M impression.

A repair contract might be nice, but it's not that necessary, as far as I can tell. On my current hard mode career I've put 4 stations and a ton of probes around various planets and absolutely nothing has broken yet. Had to do maintenance on a few nuclear engines, but that's about it. Rolling around with 2+ million kesos at all times. The only actual broken part I've had was in a sandbox mode launch on a monopropellant tank 20 seconds after liftoff, so you might be getting unlucky.

Ion engines having the same 1 hour lifetime as the other chemical/nuclear engines seems a bit low, considering one ion engine takes 24 minutes to burn through a single PB-X150 xenon container and is used for probes.

It works now, "splashed down". I took a surface sample, but it doesn't let me do an EVA report while the kerbal is in the water. Context menu option is missing (it still thinks I'm in the "oceans, landed" biome if I try it while on top of the craft. EVA/Surface sample reports show up fine there).

Well, I'd understand if it was with a rover, but... clicky for image. Highlighted debris is where I landed. The debris about 60km to the west is the first attempt. KSC is another 20-30 km away from that one.

Are the oceans not supposed to give science? I get the tinkertech invalid biome/situation notice for "landed in ocean".

A minor bug - I took an aerial survey mission on Kerbin which involved going over both poles. Aircraft didn't have enough fuel to reach both of them, so I just went to the North Pole and landed there. Recovered the craft and launched again, but the waypoints I had already flown across on the North Pole appeared again on the map view. Contract finished without issue when I went to the South Pole and got the last waypoint. That took about 60 minutes ingame time for a relatively minor reward. I'd recommend clustering the waypoints closer together in order for it to feel like a more focused mission. As is, you're basically zig-zagging across the whole planet in a single contract. Maybe have it be a couple of waypoints wihin 300-400km of eachother, then returning to the runway and landing safely?

Yes, but the thermometer should be giving you science. Bugs: Sputnik 1's description is breaking the window, like so. Some other descriptions are missing. Luna 1 has no experiments, blocking progress.

Another weird bug, which is probably RSS related - I unlocked the aircraft parts in order to get some biome science. There's no control surfaces on the first aircraft node(intended?), so I had to improvise. Lifting off, it says I'm flying above Kerbin's Highlands. It continues to say that until about 590km straight east of there, after which it changes to "Grasslands" (at this point there is ocean all around). At 640km, it changes to Highlands again and continues until at least 850km out, at which point the aircraft landed on water... and proceeded to bounce around? Weird. VVV No. I've only installed the mods listed as "essentials" for now (except RT2). I'll use that, thanks.

No, no. Sorry I misspoke - I meant for the other probe core, the Vanguard one. I hadn't tried the stock experiments before - they seem to transmit at 100% just fine.

No, that only fixes it requiring 750 data when the WAC only had 500 base. I have no idea how to fix the science bits. For me it goes: 7, 5, 3.6, 2.6, 1.9, 1.4, 1, 0.7, 0.5 etc. Only the first one at 100%. It does the same thing for all other experiments as well.

1. - GameData\Tweaks\RO\RPL_03MBumperCorepart.cfg ExperimentCost and MaxDataAmount - either set both to 500, or to 750. 2. - GameData\RPL\Parts\Vanguard\RPL_Vanguard.cfg TargetSituation = FlyingHigh - change to TargetSituation = InSpaceLow and GameData\RPL\Science\RPL_ScienceDefs.cfg requireAtmosphere = True - requireAtmosphere = False By looking through the sciencedefs, it seems like the Vanguard also has the requireAtmosphere = True for HEO experiments. Another bug - not sure if that only happens when you do the changes above, but if you resume a flight (only did sub-orbital for now) with the Vanguard, the model reverts back to the - 0.625m model Stayputnik.

The scoop-o-matic & scoop jr. cause a big decrease in FPS. Goes from 60 without them, to below 25 with 2.

I can get a lot more or the same amount (depending on fuel types, and even then the O engine usually wins out in TWR, mass or both) of dV out of an engine with ~400 isp over one with 850 with the same fuel tank and about the same overall mass. I imagine the baloon tanks will boost the regular engines' dV as well, so I basically can't see a reason in using the LV-N at all, unless I'm missing something obvious.