NHunter

Well, unlike the shuttle, it carries all of the fuel inside... IIRC launchpad dV in LFO configuration is somewhere around 5k if you haven't loaded it with super-heavy cargo. So, I'd say it is for stock - to JNSQ scale.

I also have Pathfinder so WBI omnistorage is present as well. The issue comes from me being able to independently set up resources in the part both via B9 and via OmniSrorage configuration with the latter not updating when the former is used.

It looks like CryoTanks is the most likely source of the bug I'm experiencing. It *does* have forced tank conversion.

This is a neat new (though not little) toy to play with. And it will only be getting better as you improve and expand upon it. That said: Why does the game think that Aft tank also has a docking port? I wasn't able to find one on it. Futhermore, I was able to make "double" tanks by setting it to LFO via B9 and then configuring storage to LH2. I don't think this is intended and is likely caused by MM patch not choosing a tank setup method cleanly. Also, can RSC modules please be squashed together? Having 3 of them takes a lot of space on PAWs and not everyone can run KSP even at 1080p. And, if possible, switch fuel type? LH20x would be really cool for those of us who would rather make a more light-weight version of X33

I've removed unneeded parts from my interstellar KSS Venture ("landing legs" that were needed for the ship to be correctly deployed by Extraplanetary Launchpad) and moved it to Rhode's orbit using remaining fuel in the launch engines. Next up is refueling it with antimatter and attaching exploration vessels. Once all is done, it will depart for Kerbol.

I'd actually say that K crew tank should be either 6 or 8. Definitely not more. As for K-lab, it might actually be better to increase science (not data - though 1050 I'm seeing is a weird number regardless) storage (so that you don't have to transmit it as often). I'd also like to have a K-body deployment bay (since flipping cargo bay upside down isn't always a solution) eventually, but that's not a priority. H-body cargo bay that could be useful for a small science-"shuttle" as a place to store the science equipment. Perhaps, its half-sized version and a half-sized fuel tank too? Either way, H-mount that actually has properly-aligned engines, I feel, is a much more needed improvement.

My pure-LH2 K-body spaceplane Take of is done with Nebula engines in turbojet mode, but those are switched to scramjet mode halfway through ascent to ensure most efficient fuel usage - despite being, well, a K-body space plane, it can easily achieve orbital velocities while in atmosphere with Nebulas in scramjet mode. After coasting to apoapsis - if everything went as intended - this spaceplane will only need a small (~160 m/s) circularization burn, done with ARI-73 engine. Despite being the only vacuum engine for this machine, it still allows for a very decent 0.6 TWR and some 1000 m/s dV even when carrying an orange tank of LFO. To power the engines, a nuclear reactor, mounted at the front of the cargo bay, is used (with a pair of RTG to power reaction wheels and probe core even when the reactor if offline).

Today, after a long and arduous construction, KSS Venture was deployed from the Armstrong surface base: It is a ginormous interstellar craft, capable of nearly 200km/s dV with its mighty antimatter engine. I'm yet to detach liquid-fuel boosters that were used to achieve Armstrong orbit, though, as there is still some fuel left in them. And since "legs" are rigidly attached to those fuel tanks, they stay for now as well. Once the ship is fully fueled (there is no antimatter factory on Armstrong), it will depart for Kerbol.

ask @Gameslinx, it's from his mod (Beyond Home)

@taniwha, thank you for your efforts. I assume that the patch will take some time. So, in the meantime,.. removing the ReStock patch (and re-adding clamps to the craft design) should let me build a ship starting on clamps, right?

It appears that LaunchClamps do not substitute correctly if ReStock is installed. The following code in ReStock MM config is a possible cause: !MODULE[LaunchClamp] {} MODULE { name = ModuleRestockLaunchClamp trf_towerPivot_name = obj_girdercap trf_towerStretch_name = obj_stretch trf_towerGirder_name = obj_girder trf_towerYoke_name = obj_yoke trf_anchor_name = obj_ground trf_animationRoot_name = restock-clamp-1 anim_decouple_name = RestockLaunchClamp_Deploy }

Finally, landed on Kohm: Now, one last shot of Gateway, before the mission departs back to Rhode:

Moved my Gateway mission crew lander to Kohm:

Near Future suite, SSPXr, DMagic for science, tweakscale, and I don't remember where those engines I have in the radial pods come from.

Today, I've landed on Proxim: Now, it's one last moon to visit - Kohm - and this mission can finally head back home.

Having completed exploration of the outer Gateway system, I moved my crewed lander (and its tug "stage") into the inner system and then into Proxim orbit:

Landed on Jade: Gateway abovehead! Jade's relatively-high gravity coupled with relatively-low TWR of lander's engines resulted in the landing being a bit rougher than intended: it slammed into surface at nearly 5 m/s. Thankfully, landing legs and the docking port were able to absorb the shock and nothing was broken.

I've began exploration of Jade of Maar Gateway.

Today, I've landed on Ansia: Spikey! Next up: Jade.

Nothing much happened today. Mostly, station-keeping, but I did move a mapping satellite to Ansia and the crewed lander is now in transit there as well (scheduled arrival is in 9d5h)

Today I've landed on Eidos: A tug with the lander enters the moon's orbit. Lander separated and ready for the descent. Landing on Eidos, next to ice(?) crystals. Gateway rising Departure

Exploration of Gateway system continues, and the crewed lander has finally arrived. Their first destination will be Eidos. Meanwhile, a mapping satellite has been moved from Kohm to Proxim:

Today, I landed a probe on Gateway: Transitioning into lower orbit since the craft can handle only so much heat during the re-entry, even with an inflatable heat shield and a couple of normal ones stacked behind it to protect the squishy parts. De-orbiting burn. Propulsion module detached. From this point on, the probe has no ability to control where it (eventually) lands. Inner fairing deployed as it has served its function. The actual probe is now visible (yes, that tiny little thing sitting on a truss decoupler). Weather report from high above Gateway oceans: it's sunny with a small chance of floating ice spikes. Wow. Those are quite impressive stone pillars. The probe is still three-or-so kilometers above the ocean's surface! Parachutes away! And we have a successful splashdown in Gateway's Sagen Sea.

that's... outdated? Current Module Manager is 4.something. Also, I don't think current OPT even needs Firespitter anymore