Robin Patenall

It might be a good idea if the vessels spawned on the taxiway next to the correct entrance to the given runway, rather then actually on the runway. Mostly as spawning on the runway might cause issues for multiplayer depending on how it's implemented. Imagine coming into land and another player decides that they want to take off on the same runway, at least spawning on the taxiway could check if it's obstructed first.

Today, the second part of the mission to investigate Moho was sent on its way. The "Hot Shots part deux" mission will extend the original "Hot Shots" mission (which consisted of a lander and a rover) with: A science and refuelling station with comfortable living accommodations and a grabbing adaptor that will allow the station to refuel and reuse some of the existing infrastructure that is already in orbit about Moho. An ore harvester which will land on Moho and refine fuel and is carrying an additional set of communication satellites. Two tankers that will carry the refined fuel from the harvester to the station. These components, along with the six brave kerbals, will allow more science to be wrung out of the nearest planet to Kerbol and the return to Kerbin of the reusable components from both of the missions. The departure was complicated by the narrowness of the Moho transfer window and the low thrust of the vessels, requiring burn sequences that overlapped each other. But the result is that each vessel has over 4000m/s of deltaV which exceeds the amount needed to capture at Moho (about 1800m/s) by a wide safety margin. The inline boosters that helped improve the ejection burns have been successfully decelerated and will begin the slow process of returning to the Mun refuelling buoys so that they can be reused. Spoiler contains some non-action views

Thanks. I'm glad that they at least have the issue in mind and hopefully will have it all work out.

Do we have any information about whether there is going to be save game compatibility during the early access phase of KSP 2? That is, if I start a game when it first comes out, is it likely that I can continue to use the same save up until the final release? or is it more likely that I'll have to keep restarting? I understand the point of early access, and issues that may cause a save to become incompatible are always a possibility, but does anybody know how likely that is to occur? Did it happen in KSP 1?

Bill and Bob took a souvenir picture at the canyon. No, not that one, it's wider, more tropical, cousin on Moho. Once I get them back, I might send them to Dres so they can make a an informed comparison.

For the last week or so, I have been driving Bill and Bob out of Moho's Northern region, and have eventually managed to do so. I made the mistake of thinking I could rove to all the Moho biomes and made my way to the North Sinkhole (not the Mohole) and realised a bit too late that my planned route (a) was a steep slope down to the sink hole and (b) it was in shadow. This meant that I couldn't drive out the same way I drove in with my solar powered rover and had to find a way out that was in sunshine (or wait until it was). Things to note when roving on Moho: The North is very hilly, with steep slopes Take some RTGs. It sounds odd but if the route you need to take is in shadow, it's going to be in shadow for a long time, possibly (at high latitudes) forever.

My "Hot Shots" mission has landed on Moho. The science rover (left) and the main lander (middle) both have (with some transfer of fuel) about 1450m/s which should get them back to the orbital elements of the mission. In an emergency there's a rescue craft (an ion powered lawn chair) that should have enough Xenon to get everybody off the surface if needed. Bill (left) and Bob (middle) have gone off with the rover to do Science! from different locations while Jeb has stayed behind to make sure that nobody makes off with their ride.

I've got a couple of Kerbals that might have been given the grand opportunity to be the first Kerbals to set foot on Plock when they decided to stow away on a rescue craft and required the poor Kerbal being rescued to hang on to the ladder on the outside for several orbits until I could rendezvous with one of my space stations. Luckily for them, I can't remember which ones they were any more.

Finally, the year 3 day 310 transfer window from Kerbin to Duna opened and I've managed to get all the hardware I had ready in Munar and Kerbin orbit sent on its way. The first element is Duna Station, which has been on a fitting out cruise about the Mun and will end up in Duna equatorial orbit. Pictured here is the core, a couple of tug components and the reusable propulsion systems. Currently, the core is actually docked backwards and once it gets to Duna, there will need to have some rearrangement to put the orbital adjustment engines on the right end. Connected to the core station is a large fuel tank, a lander and an intra-system mover (under the gold fairing). If you are wondering why the intra-system mover is using Puff engines and mono-propellant , I had a "upgrade this station" contract and needed a lot more mono-prop to complete it. The next component is the Rover / ISRU system. The rover was originally used to gather science from the Mun which has been, and continues to be, processed in the lab aboard Duna station and will give the scientists something to do on their long trip. With its auxiliary stage, it has enough dV to land on Duna from orbit and will gather science, either under remote control or possibly with a crew, delivered by the station lander, aboard. The rover is being transported on top of the ISRU system that is going to be landing on Ike and consists of a Kerbaled ore harvester / fuel converter and two large transfer tanks which will haul the fuel to orbit. This was also undergoing testing on the Mun and a similar system has been tested on Minmus. The last large component is the Ike station core, which was added to act as an anchor in orbit to allow the ISRU tankers and the main nuclear propulsion units, used to push Duna station, to have somewhere to dock and transfer fuel between themselves. In addition, there is a small facility for Kerbals and in an emergency explosives will destroy the central corridor and then the crew can use the fordecks as a lifeboat, with either the propulsion module, one of the ISRU tankers or a nuclear propulsion units to get them back to Duna station or Kerbin. Two sets of additional satellites were also sent, one for an equatorial orbit about Ike to give almost full coverage for the ISRU system and one set for polar orbit about Duna to augment the existing equatorial set that was placed in the last transfer window. Each set consists of three small relay satellites and a bigger relay on the carrier vessel. (The KSC PR department apologises for another picture of this particular satellite deployment system that fails to show the mounting point that joins the small satellites to the main carrier craft. We understand that our followers are interested in the construction of our space infrastructure and we would like to say that all the rumours that the mounting system is "nothing" or "magic" that keep cropping up with regard to this particular system are completely untrue)

Kerbal's can get their stars from new experiences without returning to the KSC by visiting a vessel with a Mobile Processing Laboratory on it and using the Level Up Crew option from the MPL Paw menu.

Today, Jeb, Bill and Bob arrived in the second half of my Moho mission "Hot Shots" and docked with the first part. We have the rover component with the tiny pathfinder rover on the top and the main science roved beneath. The science rover supports two and with the orange and grey long range tank has a total of 3260m/s deltaV (1700m/s in the long range tank for going down and 1560m/s in the rovers booster packs for going up). It will definitely get down but I'm not going to rely on its ability to get back into orbit on its own. The lander supports three and has 2160m/s of deltaV, which is enough to get it down once and return. It includes storage with a set of surface experiments. This will probably not initially be landed as if the rover breaks down or gets stuck, the lander can go and retrieve the Kerbals on the surface. Of the three nuclear pushers, two are empty (of fuel, they has some mono-prop) and Pusher 7, the hitchhiker storage container and the MK1-3 command pod form the return stage with about 6500m/s of deltaV which should be enough to get the Kerbals back without aerobreaking. That deltaV is the minimum as there is quite a lot in storage, including parts for an ion powered lawn chair that should be able to get two Kerbals back into orbit from the surface. In the case of a serious system failure, in about 100 days a rescue ship should arrive which would allow the Kerbals to be rescues and returned to Kerbin, having over 7000m/s once in orbit of Moho, as long as they don't mind being rather cramped. It should have arrived already (before the Kerbals) but there was a slight issue with transfer window timing (If you put a vessel outside Kerbin's SOI, the transfer window moves by a few days and, in the case of Moho, that makes a lot of difference)

They said they wanted a small asteroid to study. but they didn't give a delivery address.

Hi @linuxgurugamer, The other day, I turned on the "Process manipulatable-only parts" feature and it got stuck in a loop, complaining that new parts had been detected every launch. I think I've identified the issue through. What happened was every time KSP started, the mod would extend the partVolumes-v3.cfg file entries for each of the the manipulatable-only parts, like it wasn't noticing that it had already fixed them. Each part gave an entry like: // SquadExpansion/Serenity/Parts/Robotics/RotorEngine_02/RotorEngine_02 // Dimensions: x: 1.26, y: 0.88, z: 1.25 // Bounding Box Size: 1381.887 liters // Volume adjustment: 10% // @PART[RotorEngine_02]:HAS[@MODULE[ModuleCargoPart]]:Final { @MODULE[ModuleCargoPart] { packedVolume = 1521 KSP_PartVolume = true } } This edits the existing ModuleCargoPart module, but I'm pretty sure that it adds a new packedVolume value to the module, so there are two and when the mod looks it gets the the original -1 value and thinks that it hasn't been processed. Changing it to: @PART[RotorEngine_02]:HAS[@MODULE[ModuleCargoPart]]:Final { @MODULE[ModuleCargoPart] { %packedVolume = 1521 %KSP_PartVolume = true } } with the leading %, to make MM edit or create the values (rather than add) seems to fix the issue when I edited my partVolumes-v3.cfg file. It looks like a couple of changes around [email protected] would fix the issue but I haven't tested this as I don't have an environment set up to compile and I was having some issues following the code generating the popup (the call seems commented out on [email protected] and the text of the pop up is different, is master the correct branch?)

Hi @Angel-125, I noticed today that I couldn't manipulate the Printshops and Cargo containers while in EVA construction mode. It looks like it is intended that you should be able to this, as those parts have a ModuleCargoPart with packedVolume=-1 but that module needs to come before the ModuleInventoryPart one for it to work. I made the changes to the 2 printshops and 3 cargo containers and tested it and it all seems to work. I'm pretty sure that I've managed to submit a pull request with the fix on github, but it is the first time that I've done one.

Let me introduce the KPS Glom of Nit (Yes, KPS, the Kerbal Post Service). Used for when your Gilly mission is missing a small but vital part, and your engineer has a Kamazon Super Platinum Hyper Prime subscription. The part was missed because almost all of the Gilly mission was recycled from older missions and right at the moment a Kerbin to Eve transfer is about 5.5km/s of deltaV so I had to build a rocket with about 10.6km/s on the launchpad for sending a 50kg part. I over built a bit as I'm going to have about 2000m/s to rendezvous with and land on Gilly after a loose capture about Eve.