Angelo Kerman

January 9

6 hours ago, JadeOfMaar said:

I discovered that one for myself recently, and backed off of it. It would make a fine addition to the list fo things handled by KSPCF. It's really nice that the TAC LS converter module does this properly. Maybe that's a major part of why that module exists.

Yeah, the only way that I could fix it is to override the converter's "GetInfo" method, which generates the text showing the inputs and outputs. Then I could account for EfficiencyBonus as well as adjust how those performance numbers are displayed. That's non-trivial, but it is doable.

January 9

4 hours ago, Rakete said:

Sorry for not having had the time to test the new BS version. Unfortunately my work-free time around xmas is over so I will have to give a try in the next days around weekend - as soon as i find the time. So please be not disappointed, that there's no report on the action group fix yet.

Have you had time to have a look? @Angelo Kerman

Ok, I've looked into this. The S3 Gravimetric Generator consumes 36 Graviolium/hr and 0.68 Fusion Pellets/hr. If you look at the config file, the generator (and the S3 Warp Sustainer) consume 0.01 Graviolium/sec. The S3 Heavy Warp Sustainer consumes 0.02 Graviolium per second, which is 72 Graviolium/hr (0.02 /sec * 3600 sec/hr = 72/hr) and 1.35 Fusion Pellets/hr. Based on my calculations, the Heavy Warp Sustainer produces twice as much as the S3 generator, and consumes twice as much resources, which is by design. Looking at the part model (it's been awhile since I've seen the older S3 sustainer), the Heavy Warp Sustainer even has two fusion reactors on it, so I definitely went "moar boosters" on it for the increased capacity.

I think the issue you're running into is how the game is reporting the numbers. For some reason, if the value is 0.01/sec, then you'll get that 36/hr that you see with the S3 Warp Sustainer and the S3 Gravimetric Generator. But bump that number up to 0.02/sec like I did for the S3 Heavy Warp Sustainer, and suddenly you have 0.02/sec being reported, when I'd think that it should report 72/hr. And on top of that, the readout doesn't even take into account the part's EfficiencyBonus! Technically, I could use the same numbers on the S3 Heavy Warp Sustainer as I do on the S3 Gravimetric Generator, set the Heavy Systainer's EfficiencyBonus to 2, and in flight it would be twice as efficient- but in the VAB/SPH, it would show the exact same performance values as the S3 Warp Sustainer & S3 Gravimetric Generator.

Yay KSP 1...

January 9

@Falki This looks like a great addition to KSP 2. I look forward to watching how it develops. Are you considering adding Discoverables to the display as well? I like the "?" feature of SCANSat displays that showed anomalies, and something like that in Orbital Survey would be great.

January 8

On 10/27/2023 at 9:27 AM, StormxWolf said:

Hi, I am looking to modify the alien jump gates such that I can access other gates before I have ever discovered them. I see you have a setting: "isKnown" which seems to do exactly that however I have set it to "true" and I seemingly cannot use other gates unless I have first rendezvoused with them. Could you let me know how I can edit a save to make a spawned gate usable without ever actually rendezvousing with it? Let me know if you know of some way to accomplish what I am trying to do or if I am being unclear.

Thank you for the fun mod!

I've investigated your issue and can verify that when anomalies are set to isKnown = true, you can reach the gates even without visiting them beforehand. You will need to visit at least one of them before order to visit any of the rest. You might need to disable jumpgates, save and reload your game. If that doesn't delete the gates then you can manually delete them via the tracking station. Once you've done that, install the patch below, set isKnown to true for the jump gate, restart your game, and re-enable jumpgates.

I've fixed a couple more issues and here is the latest pre-release update. The fixes are:

- Adjusted part costs for the Bussard Collectors and Plasma Vents.

- Fixed negative Funds cost of the Mini Jumpgate Platform.

- Fixed issue where space anomalies all had the same vessel name.

1 hour ago, Rakete said:

Sorry for not having had the time to test the new BS version. Unfortunately my work-free time around xmas is over so I will have to give a try in the next days around weekend - as soon as i find the time. So please be not disappointed, that there's no report on the action group fix yet.

Have you had time to have a look? @Angelo Kerman

I haven't had time to look at that yet but it is on my list.

January 8

Latest pre-release for Blueshift can be found here.

- Added Debug Mode menu item to the Blueshift Settings menu. This supersedes the "debugMode" field found in settings.cfg and various part module files.

- Added Sphere of Influence support for JNSQ's planet Nara.

January 6

3 hours ago, Rakete said:

So in my case I should define Plock (from Outer Planets Mod) as last planet for kerbol. And the others should be straight forward according to their definitions, I hope... uuufff.... I guess I have to learn to read kopernicus definitions e.g. Alpha Centauri has 3 stars on their way around a common barycenter. I guess, this has some name too, which would be the reference for the farest planet.

Remember that other stars will already have their own SOI. So you don't need custom definitions unless you want to alter what is considered the "last planet" for a particular star system.

January 5

20 minutes ago, Rakete said:

And this will make BS accept, that Kerbins SOI is smaller than defined in REX and thus enables interstellar speeds? You said it might extend Kerbins SOI extremely far.

REX adds separate solar systems. It adds nothing to the Kerbol system itself - at least not on the user side. It could be, that the stars out there techically move around kerbol so slow, they are almost static. Maybe ?! I don't know how REX is defined and how Kopernicus definitions work technically.

Yeah, REX might be messing with what is defined as the "last planet" in the Kerbol system. For non-JNSQ usage, that LAST_PLANET node will define Kerbol's SOI by specifying Eeloo as the last planet.

January 5

2 hours ago, Rakete said:

Sounds great. What does pre-release mean? Are there further changes incomming?

The description on github made me smile: yadaYada=true ??? I love such eastereggs in configs.

I will try this. I guess you mean the settings.cfg in the Blueshiftfolder, right?

So I will have to define a last planet for every Star. Including Kerbol (=Sun?) right? Have you done this for other planetpacks (where the vessels go interstellar speeds), or where do they get their configs from? Or did they configure blueshift for their mods in their configs?

I figured out a workaround it i fail to tell blueshift the starsystem config: REX has an option to lower the interstellar distances. As last resort I could tune them down, so that the interplanetary behavior of BS will suffice. I made myself an excelsheet to calculate the warp range of a vessel based on graviolium usage per time, max. Warpfactor and available graviolium on the vessel.

I will try out the new BS version as soon as i can. Probably tomorrow.

Pre-release means that the new update isn't done yet, but I'm rolling out changes as I make them so people can try them out. Think of it like "Early Access" for the next patch.

Yeah, you'll need to modify the settings.cfg in the Blueshift folder.

For other planet packs, like, say Galaxies Unlimited, I don't have to define the last planet for every star. That's because each star system already defines its own SOI. It's only the Kerbol system that doesn't do that, and I think the Grannus Planet Pack needed some help too. I guess it's possible that since REX is adding exoplanets to the Kerbol system, they're extending Kerbol's SOI pretty far out.

Try adding this to your Blueshift/settings.cfg file:

LAST_PLANET:NEEDS[!JNSQ]
{
	// Name of the last planet.
	// This is the name of the celestial body, NOT the display name!
	name = Eeloo

	// Name of the star that the planet orbits.
	// This is the name of the celestial body, NOT the display name!
	starName = Sun
}

January 5

First pre-release of the latest Blueshift: https://github.com/Angel-125/Blueshift/releases/tag/v1.10.0

3 hours ago, Rakete said:

Sounds great!

Before the next BS-release you might also want to have a look on the gravi-usage of the S3 heavy sustainer it uses 0,02 gravi /s (according to the part description in VAB) meaning 7,2 gravi /h where all other S3 parts are at 36 gravi / h. I guess you meant 72 gravi / h for the heavy sustainer? I can only speculate, that the low value is unintentional.

How can I do that? I'd e.g. aim for Kerbols SOI being twice the size of the orbit of the farest planet (for me Plock, since I use OPM). What do I have to edit?

Offtopic: I you are in the mood for bew BS parts,... maybe a S1 Warpcore and S0 coils would be funny for little warp-capable vessel that start from a bigger mothership. Just an idea if you should be in the mood for new parts.

Also an idea to go even bigger like Nerteas NF - Launch vehicles mod, thar come with 5m and 7m parts. Such super heavy and super expensive warpdrives might be capbleable of ferrying supergate-parts over to another solar system (Somehow the generarion of alien gates does not seem to work for me. Probably the same reason with REX as on the interstellar speed issue).

I think you can set it via:

// Blueshift can calculate the home system's sphere of influence based on the furthest planet from the star, but some planet packs
// don't make it easy. To help the mod out, you can define a LAST_PLANET node that tells Blueshift what the last planet is for the specified star.
// Each star needs its own LAST_PLANET node.
LAST_PLANET
{
   // Name of the last planet.
   // This is the name of the celestial body, NOT the display name!
   name = Cernunnos

   // Name of the star that the planet orbits.
   // This is the name of the celestial body, NOT the display name!
   starName = Grannus
}

// Blueshift can calculate the home system's sphere of influence based on the furthest planet from the star, but some planet packs
// don't make it easy. To help the mod out, you can define a LAST_PLANET node that tells Blueshift what the last planet is for the specified star.
// Each star needs its own LAST_PLANET node.
LAST_PLANET
{
	// Name of the last planet.
	// This is the name of the celestial body, NOT the display name!
	name = Cernunnos

	// Name of the star that the planet orbits.
	// This is the name of the celestial body, NOT the display name!
	starName = Grannus
}

I haven't tried this for Kerbol, however, and I'm not even sure what the name of the sun is in the game.

You might also try playing with

	// This multiplier is used to calculate a star system's sphere of influence based on the furthest planet from the star (if any).
	// We artificially calculate the solar SOI because the home system (Sun, a.k.a. Kerbol) technically has an infinite Sphere of Influence.
	// A value of 1 puts the distance at the semi-major axis of the furthest planet. 1.1 is 10% past that distance.
	soiMultiplier = 1.1

this is in the settings.cfg file.

January 4

Finally figured out the problem with generators and action groups, testing the fix is ongoing. I may have the first pre-release in the next evening or by the weekend; I need to finish up the S1 multi-coil prototype part first.

January 3

23 hours ago, Rakete said:

@Angelo Kerman I noticed that Blueshift has issues in detecting the active vessel being in interstellar space, remaining in interplanetary mode while using the REX planet pack:

I went halfway to another star, but blueshift stills shows interplanetary as spatial position , thus not enabling the muxh higher interplanetary speed limits.

I suspect the issue is that Blueshift doesn’t know about REX. If these exoplanets are orbiting Kerbol then yeah, Blueshift isn’t aware of REX. I had to manually define the interstellar SOI of Kerbol due to the way that the game works. My guess is that with REX installed Blueshift will need to adjust the Kerbol interstellear SOI.

12 hours ago, RayneCloud said:

Welcome back to it and happy new year, please take your time and focus on your own health and well being first. I wont speak for everyone, but I am glad to have you back at it @Angelo Kerman Thanks for the best FTL mod in KSP. <3

Thank you. I intend to take it slow, especially given my workload for my job and family concerns. That said I intend to publish incremental previews as I fix things so you’re not waiting forever for all the fixes. They will be pre-release builds.

The action group issues have proven to be elusive due to the Blueshift generators using stock part modules for the generator code. My stuff just adds special effects on top of the existing stock part module. Not sure why that is a problem. Once I finish the S1 multi coil prototype I will look at the generator code again.

January 2

4 hours ago, Rakete said:

Happy New Year, dear god of most kerbally warpdrives

(i really love your mod(s)).

Will this be a compatible change, or will have all existing crafts, that use warpcoils already have to be adjusted to keep their look and functionality ? (in other words, will the new multi-length coils be technically new parts while keeping the old deprecated ones in the folders to be found by older crafts?

Especially warp-sstos have a hard time balancing Center of mass things for full and empty states, so it would be nice, if the old parts could still be found in the files (maybe just hidden from the VAB/SPH to be not placed anymore on new vehicles)

While you are planning a new Blueshift release, could you maybe have a look at the reason why some actions can only be assigned to actiongroups while in flight and not in the VAB? e.g. the aux displ. wave generators can not get their toggling assigned to an actiongroup while building. It can only be assigned to an AG while in flight. Thats kinda odd. Can I repair it myself by editing the config? If so, what so I have to change, to repair it myself?

P.s.: Excelsiorclass-Warpcoils should promiss transwarp. And not fullfil that promiss

The multi-coils will be new parts. The existing warp coils won't be going away. You'll be able to visually tell the difference in the editor; the new parts will show two segments in their part icon.

The action groups thing is definitely perplexing and I don't know what causes it, but it's on my list to investigate.

P.S. They should have high warp capacity, require a large amount of GravityWaves, and produce a correspondingly high StaticCharge.

January 2

Happy New Year!

A little bit at a time so I don't burn out, I'm investigating Blueshift's issues and what can be done about them. First up: multi-segment warp coils! These will come in 2, 4, 6, 8, and 10-segment variants for the S1, S2, and Mk2. No more warp coil spamming!

I'm also thinking about a Mk3 form factor warp coil, something akin to the USS Excelsior, but we'll see. Right now in Blender, I can modify 3D models that I've already built, but making something from scratch is gonna take more learning...

Anyway, the mult-segmented warp coil will automatically adjust its mass, cost, and performance based on the desired part variant.

December 31, 2023

DSEV 3.3 is now available:

- Added D2 Hab Ring: This is a variant of the Nautilus Centrifuge that has a Size 3 hub. It cannot retract its ring, and it sports 4 Omni Converters instead of the Pathfinder template system, but it's otherwise identical to the Nautilus Centrifuge.
- Added D2 Conference Room: This is a half-height version of the D2 Briefing Room's upper floor.

I can't figure out what's wrong with the Estonian IVA...

December 30, 2023

On 12/18/2023 at 9:07 PM, Ooglak Kerman said:

Hey @Angelo Kerman Glad you've come and rejoined.
@JadeOfMaar got me sorted out on taking out the most problematic (for me) waterfall effects for the warp drive.

Heh... I've grabbed and warped both asteroids and tetrahedrons around and about. The afterburner bit you added to blueshift is oh so helpful there.

Have you had any opportunity to have a look at the resource utilization issue for the warp drive when in interstellar space? (goes to zero)

I've actually been on vacation and will tackle this in the new year.

December 22, 2023

And now for something completely different and unrelated to the story...

Spoiler

December 22, 2023

I made more suits...

December 20, 2023

Chapter 13

Emma stepped outside once again to install Pyramid Base’s second solar array. It didn’t take long for her to complete the work thanks to the electrical connectors on the Multipurpose Roof Rack. Next, she grabbed an extendible light fixture and attached it to another MRR that she’d mounted atop one of the Casa modules attached to the base’s lab. Finally, as the sun crept below Duna’s lowlands, she mounted a communications antenna that the Buffabus’s 3D printers had just completed. At last, she had the pleasure of turning on the lights.

“It’s very cold in here,” Emma said, sitting in the lab, “but the air pressure is steady. The heaters will warm the place up in time… Pyramid Base is open for business- at least for the next crew. They’ll have to bring the instruments that we can’t make...”

“I just want to personally congratulate the Buffabus crew on a job well done,” Charles McKerman, head of the Ministry of Space, said a few minutes after Emma returned to the Buffabus. His eyes kept flickering between the camera and something beside it and out of view. From the tone of his voice, it was clear to Calbro that Charles was less than enthusiastic about delivering his speech.

“The crew has made some smashing finds such as the unusual rock formations, the ‘Dunalith,’ the Face, and of course the Pyramid. Your efforts to adapt to the changing situation and the extra work you provided to build the Pathfinder bases have- uh- have paved the way for future expeditions to the anomalies that you discovered.”

Charles paused a moment. “Not acknowledging us by name,” Ferwin noticed.

The Director of the Ministry of Space continued. “As there are no more anomalies near your location, and given the current state of the Buffabus, I agree with Sir Randal’s assessment that you should return to Duna Base post haste. Unfortunately, a trip to the South Pole would be unwise at this time. It’s time for the Buffabus to return to base. Again, well done. Sir Randal has the specifics about your journey,” Charles concluded. The screen switched to a kerbal in MoSMC.

“We estimate that it will take approximately a month and a half to return to Duna Base, accounting for regular maintenance stops as well as unscheduled breakdowns,” Sir Randal McKerman, Flight Director for DBE-1 began…

*

“It’s an engraving, like what you’d put on a tombstone, and, interestingly, an apology,” Adsii said, during his presentation. Several kerbals moved closer to the edge of their seats. Adsii took a deep breath and continued. “The pyramid is the final resting place of Tut-Un K’vin-Anh. Curiously, I haven’t found any other references to Tut K’vin, but there’s much of Kermantian history that’s either lost or missing. Anyway, the inscription reads, ‘Here lies the great Tut-Un K’vin-Anh, leader of Kermantians, who let our spirits soar.’

“The builders of the pyramid also apologized to Tut-Un K’vin-Anh for not building a larger pyramid befitting his status. They stated that they had limited time and resources to build his tomb, and they hoped that he liked the view of the aurora australis dunae, more popularly known as Duna’s Southern Lights, and what the Kermantians called ‘dancing spirits.’ The Kermantians hoped that after some rest, his spirit would be able to join them. There’s no mention of why Tut K’vin was entombed out in the middle of nowhere on Duna, but we presume that the site had some significance to the Kermantians.

Finally, there’s an odd quote on the tomb. It reads, ‘When we left Kerbin, we didn’t see ourselves as giants. We were humbled as our world became small.’ The way it was phrased was… out of character… with the rest of the inscriptions, but we don’t know why.

“Now, I’ll take your questions…”

*

The discovery of the small Kermantian pyramid on Duna spurred the spacefaring nations of Kerbin to ratify the International Space Consortium Charter sooner rather than later. Shortly after Adsii delivered his press conference, the six space agencies- the Kerbal Space Program, the vonKerman Space Agency, the Ministry of Space, and three newcomers- signed the charter and had the networks air the event. Not long after, the ISC took over the Deep Space Exploration Vessel (eXperimental) program.

With gravitic technology in its infancy, conventional rockets were still very much in use. Hence, the Ministry of Space fielded their Arrow 6 launch vehicle, which blasted off its pad and flew into space a few minutes later. Upon reaching orbit, A6-5, the reusable upper stage- its companion booster had already landed on an awaiting barge- opened its payload bay and revealed the passenger pod contained within. Three hours later, the upper stage arrived at its destination…

With Newton (DSX-01) and Halley (DSX-02) completed, the ISC brought a flight crew to each ship to begin their evaluation. Each crew would spend time flying to the Mün and Minmus and back while evaluating the ship’s performance, and then swap spacecraft and repeat the process. Once completed, both crews would compare notes and present their findings to the ISC to make a final decision. In the case of A6-05's first stop, Hanse vonKerman (PLT), Samny Kerman (PLT), Danwig Kerman (SCI), Richny Kerman (ENG) and Karl vonKerman (ENG) formed the first evaluation crew of the Newton.

As the first crew boarded DSX-01, Frolie couldn’t help but feel envious as Steve Kerman, one of his protégé engineers and Orbital Dynamics’ liaison, said his goodbyes and joined the evaluation crew. Frolie would’ve loved to join them- as would Scott- but as the “Father of Gravitics,” his celebrity status would have given Orbital Dynamics an unfair advantage in the evaluations, so he recused himself from the crew. At least he got to see the Newton leave the shipyard and begin its journey…

“You are free and clear to navigate,” Dildun Kerman, Air Traffic Control for Magic Boulder radioed. Hanse vonKerman acknowledged the clearance, pitched the ship upward, and gave the gravitic engines a brief pulse. The Newton immediately shot away from the shipyard, but the crew felt no acceleration. “Remarkable,” Hanse said.

A couple of hours later, Newton arrived at her first destination: the retired Starlab Kerbin Orbiting Station. The crew noted some abnormalities in the engine ~~exhaust plume~~ operations and ~~didn’t grab any screenshots~~ Steve ~~fixed the plumes~~ made some adjustments to correct the issues. Truth be told, the ship was overpowered, and it took several tries to match velocities with the station. Hanse had to be careful touching the throttle to avoid overshooting. But thanks to his careful maneuvering, Newton approached within a few meters of the aft docking port.

Once the crown jewel of the Kerbal Space Program, Starlab was retired and replaced by Sky Reef, Orbital Dynamics’ Oasis-class commercial space station. But in her heyday, Starlab was one of the first permanently staffed stations that was constructed in orbit thanks to numerous Space Shuttle flights. KOS also formed part of the transportation hub that enabled kerbals to venture to both of Kerbin’s müns on a regular basis. But Starlab’s increasing breakdowns required KSP to shut down the aging space station and boost it into a higher “museum” orbit to reduce the increasing traffic in low Kerbin orbit.

A few minutes later, Hanse deftly maneuvered DSX-01 to Starlab’s secondary Shuttle docking port and linked up with the old station. Given its condition, they didn’t stay long. This was a test flight, not a service call, after all… The ship took on some xenon gas to replenish their reserves as well as some water that the station no longer needed.

“We used more propellium than I would have liked,” Hanse said, taking notes, “and she’s far more powerful than I thought. Pilots will need to be gentle with the throttle, especially when fine tuning our position. Shooting past the station multiple times was a bit embarrassing, I must admit…”

“Steve, can we rig up some electrolysis stations in the habs,” Richny asked. “Might as well make use of the water and compost that Magic Boulder stuffed into the cargo pods…”

“Absolutely,” Steve responded. It didn’t take long for the engineers to configure the habitation modules’ omni converters.

“Can’t we just use the gravitic engines for reaction control too? That would eliminate the need for propellium altogether,” Karl vonKerman said.

“That’s… well, actually, now that I think of it, the engine module was built before we had fine control of the gravitics,” Steve admitted. “The Buffapod doesn’t have traditional RCS thrusters, it uses gravitics. So, yeah, I can make a note of that and make sure that the DSX can use them too.”

With the first leg of their journey completed, Newton departed from Starlab and the crew said farewell. Hanse programmed the autopilot to orient the spacecraft prograde. Thirty minutes later, DSX-01 performed a maneuver burn towards the Mün. It took a mere 5 seconds to build up the 1km/sec delta-v needed to break Kerbin orbit. The crew barely noticed the acceleration.

“Newton can easily enter solar orbit if we’re not careful,” Samny noted. “We’ve got a 3-day coast to the Mün, but with this ship’s engines, we probably could get there in a matter of hours…”

*

As Newton departed Magic Boulder and headed for the Mün, Arrow 5 also departed the enigmatic construction station and docked with the Space Operations Center an hour later. Hensen Kerman (PLT), Sofia vonKerman (PLT), Rolf vonKerman (ENG), Maxbret Kerman (SCI), and Guest Astronaut Munvan Kerman (SCI) all boarded the Halley (DSX-02). When A6-5 arrived at the Space Operations Center, astronauts could see the contrast between the large cargo shuttle and the smaller Galileo-class shuttle. The Ministry of Space was debating whether to discontinue the Galileo, with its expendable service module in favor of the fully reusable Arrow 6. Both used the Arrow 6 booster, but while Galileo could carry six astronauts, the Arrow 6 Crew Pod could carry twice that.

“Reactors on, centrifuge started, fusion engine charging,” Hensen stated as Halley pulled away from the Space Operations Center. The Kerbodyne KF-1 graviolium-catalyzed fusion engine took a full minute to charge before igniting its fusion reactor. Given the amount of electric charge required, the ship’s flight computers stopped the centrifuge’s rotation and paused the redundant recycling systems.

Finally, the engine started, and the centrifuge and recycling systems came back online. “Power hog” was the nicest comment that Rolf could make about the engine startup sequence. But at last, the fusion engine became self-sustaining, providing all the power that it needed. The long startup time was a tradeoff for using far less graviolium than the Newton.

The Halley lit its engine for the first time to increase its orbit as the first leg of its journey. The crew noted that the spaceframe flexed as the burn continued. The ship’s RCS thrusters compensated for the flexing, and the ship remained on course. Some ~~autostruts~~ software tuning of the engine’s thrust pulses to avoid resonating frequencies resolved the issue. But even with the software changes, the ship had problems staying on its burn path. Leaving the fusion engine on during the coasting burned through some of its fusion pellets, which gave the crew some concerns. At least the ship’s propellium supplies gave it an impressive 25,000 m/sec of delta-v… Three hours later, Halley arrived at its first destination.

In contrast to the mothballed and dormant Starlab, Sky Reef was a bustle of activity. The lights were on everywhere, its greenhouses and labs and habitation units were in use, and even its centrifuge module- a leftover from Project Laythe- was spinning. Phildas Kerman, Sky Reef’s current commander, gave the crew of Halley a tour of the new space station. “We have all the amenities of Oasis,” Phildas explained, “including a dedicated Sandcastle 3D print lab, a mobile processing lab, and Homestead habitation modules. The design is less complicated than Starlab while offering more habitation space and modernized facilities.”

A couple of orbits later, Hensen and his crew thanked their hosts for their hospitality and then departed Sky Reef. A half-hour after that, DSX-02 performed a four minute, 30-second burn to put it on course for the Mün. Like the Newton, Halley had a 3-day coast to Kerbin’s nearest natural satellite. As planned, Newton had a day’s head start on them, though. Not long after shutting down the fusion engine, Rolf started sneezing uncontrollably, and his eyes itched like crazy. He knew exactly what was happening. “Mulch,” he said, exasperated, “I’ve caught a cold…”

*

In a first for space vessels, DSX-02 had a sickbay to handle medical situations ranging from minor diseases and injuries to major surgery. It was a breakthrough capability, especially given the microgravity conditions that made medical procedures more challenging to accomplish. Halley’s sickbay could hold up to six patients, though today, as Halley coasted towards the Mün, Rolf was the only patient, and Maxbret took up residence.

“I’ve no idea how I caught a cold,” Rolf began, “I was careful and never broke quarantine before launch.”

“Maybe you touched a contaminated surface,” Maxbret responded. “I’ll ask the crew to help wipe down anything you touched. Nobody else seems to have contracted anything.”

“It’s just embarrassing,” Rolf admitted. “I was supposed to test out the Compact PMV today.”

“It’ll wait,” Maxbret declared. “You need to rest. There’s plenty of time in the schedule to test it later. Oh, and check your email.”

To distract from his misery, Rolf checked his email. His inbox was full. Not only did he receive well wishes from his own crew, but he 4also received them from the DSX-01 crew and from Mission Control as well. All the good cheer made Rolf even more embarrassed.

*

As Rolf received his diagnosis, Phoenix Aerospace launched Phoenix Station, a renovated backup to the old Starlab module that formed the core of the now retired Kerbin Orbiting Station. The former Starlab 2 languished for years in storage until the Kerman Air Force acquired it. At the time, Starlab 2’s new mission was to serve as the core of a station designed to discreetly process blutonium from Magic Boulder. When that idea was shelved in favor of simply returning the blutonium to Kerbin, Starlab 2 was shelved along with it. The station module again sat in storage until Phoenix Aerospace found a use for it: the company wanted to use the refurbished module as a waystation for trips to the Mun’s surface. Phoenix Aerospace hoped to offer tourist trips to paying customers, but business analysts questioned their ability to compete with Orbital Dynamics and their polar orbiting Oasis station. It was a desperation move; things were not looking good for Phoenix Aerospace…

Phoenix Station blasted off from Pad A at KSC early in the morning courtesy of an Edna 1F- itself a relic from the early days of Münflight. Though on the verge of retirement many times, Edna survived into the modern day thanks to repeated upgrades. But with gravitic technology making its debut, Edna’s days were finally numbered. Nonetheless, the launch vehicle lifted off the pad flawlessly and climbed into the sky. One minute later, it jettisoned its reusable side boosters while the core booster continued its trip uphill. Five minutes after that, the expendable core stage departed the spacecraft, leaving the upper stage to finish the job. Phoenix Station entered a 119.4 km by 130.6 km orbit and deployed its solar arrays and high-gain antenna. At long last, the venerable station core reached orbit!

Four hours later, the E1F upper stage dropped off the module and got out of the way to enable PPE-1 to dock with the module. With its business completed, the upper stage flipped retrograde and made its death burn. Then, after a few false starts, PPE-1 lit its ion engines and propelled Phoenix Station towards the Mün. A course correction six hours later ensured that it would reach its target in three days…

A day after Phoenix Station blasted off, Phoenix Aerospace launched a spare Resupply Module along with a tank of xenon gas to refuel PPE-1. The REMO, named Williams after an obscure movie reference, sat in orbit awaiting PPE-1’s return from the Mün…

*

A day later, Newton entered the Mün’s sphere of influence. A quick calculation showed that the ship would hit the ground if it continued its course, so three hours later, she made a quick correction burn to raise her periapsis to 223.7 km. Once again, the crew had to gently increase the throttle to avoid overshooting their required delta-v. It took another half-day before DSX-01 entered münar orbit and lower it to 22.8 km by 30.5 km. Hanse only cursed twice as he overdid the sensitive throttle…

Once safely in orbit, Samny, Karl, and Danwig got the privilege of testing one of Newton’s unique features: its Buffalo Shuttlepod! The trio boarded the diminutive craft, powered up its systems, and extended its wings. Hanse then gave the go ahead to depart, and Pod 1 undocked from Newton. Samny let the shuttlepod drop away for a few seconds before starting its gravitic engine. It was hard for the away team to believe that such a small craft could go anywhere on the Mün from any orbit, but such was the advantages of advanced technology.

Five minutes later, Pod 1 executed a 224 m/sec burn- technically an incorrect term, but tradition dies hard- to drop out of orbit. Within minutes they halted their forward velocity and hovered over the ground as they searched for their target. “Amazing,” was all that Samny could say. They searched and searched, and then realized that they missed the target and had to turn around. That was a trivial maneuver for the shuttlepod. “We have to have at least one of these on every DSEV,” Samny said.

“If we can find more graviolium,” Karl countered.

“Drax found some in their asteroid,” Danwig pointed out, “so we know it’s out there. We just don’t know how much.”

“There! 12-o-clock low,” Karl yelled, interrupting the conversation. “We’ve found it.”

Samny set Shuttlepod 1 down on the ground- with a heavy thump that broke two of the static electricity dischargers. They’d have to repair them when they get back to the ship. Nonetheless, the craft became the first gravitic-powered spacecraft to set down on another celestial body.

“Nice landing,” Danwig quipped.

“Hey, you try flying this thing for the first time,” Samny growled.

Resting on its side just a few meters away was Miss Piggy, the original Münar Ground Module Rover that Bill and Jeb drove during their famous “road trip” on the Mün. They held the record for the longest off-world land driving distance for many years until the Buffabus utterly demolished that record on Duna. Unfortunately, in an attempt to drive Miss Piggy to Billstown’s new location, the rover hit a rock and broke apart on the landscape as it tumbled to a stop. The Newton away team were the first to visit the wrecked rover in over fifteen years.

“With a shuttlepod, rovers are going to be obsolete,” Samny said. “Let’s go take a look.”

The away team suited up, depressurized the shuttlepod, and stepped outside for a closer look. They were careful not to disturb the crash to preserve history, but they did take a few pictures of the wreck for closer analysis back home.

“Look at that construction,” Karl vonKerman said, admiring the handiwork. “Designed in the Munflight era- you can see some of the standard connections over there. Remarkable. If the vonKerman Republic had resources like your Kerman States did back then…” He walked over to the other side of the wreck. “Look at how sturdy the chassis is. The fuel cell tanks are still intact. Too bad the crew cabin wasn’t as durable.”

Once the away team took their pictures and made their damage assessment, it was time to go. They piled back into Shuttlepod 1 and lifted off to their next destination. The craft had no trouble restarting its gravitic engine and effortlessly floated away from the surface. Samny had hoped to find the landing stage of the Own Münar Excursion Module but the away team was unable to do so. With their excursion time running out, Samny elected to point Shuttlepod 1 at Newton and firewall the gravitic engine. A few minutes and failed rendezvous attempts later, Shuttlepod 1 docked to Newton once more.

“What an amazing spacecraft,” Samny concluded. “We landed, explored the surface, and got back to the ship before Newton went over the horizon. Absolutely amazing.”

*

Karl was about to print some replacement electrostatic dissipators for Shuttlepod 1 when he realized that Newton’s 3D printer was out of ore. Then he checked the ship’s stores and found the ore bins empty. “Huh,” he said quizzically.

“What’s up,” Richny asked while searching for the EVA maneuvering packs. The search wasn’t going well.

“We’re out of printer ore,” Karl stated.

“Well, that’s a problem,” Richny answered.

“Yeah. Any luck finding those jetpacks?”

“No, and I’ve looked everywhere that they should be, and a few places where they shouldn’t.”

“Who puts to space without a full load of printer ore and jetpacks,” Karl wondered aloud. They looked at each other.

“Better call Halley,” they both said…

“Halley, this is Newton,” Sofia vonKerman heard on the ship’s radio. She was taking a turn at piloting the ship while Hensen had other tasks to do. It sounded like Hanse’s voice.

“Hallo, Hanse,” Sofia said in their native vonKerman.

“Hallo! How is Rolf,” Hanse asked in vonKerman.

“Still embarrassed,” Sofia said, chuckling. “Rest of the crew is fine.”

“Good to hear! We’ll leave him some get well cards when we swap ships.” Hanse’s voice became more serious. “Uh, Halley, Newton,” Hanse said, switching back to Kerman- the official language of the ISC- “do you have any printer ore aboard, or any jetpacks?”

“Uh, that’s an unusual question, Newton, any particular reason why you ask,” Sofia asked.

“Humor me,” was all Hanse would say.

With Rolf out sick, Maxbret conducted the inventory. “We don’t have any jetpacks,” he reported a few minutes later.

“Huh,” Sofia responded. “Well, we can print them up in the ship’s Sandcastle printshop. How much ore do we have?”

“None,” Maxbret said.

“Ok, great. We can- wait, none?”

“None,” Maxbret repeated.

“Uh, Newton, Halley,” Sofia began over the radio. “We have zed jetpacks and no printer ore.”

“Same here, Halley,” Hanse radioed back. “Someone forgot to stock up our inventory and resource stores- on both ships.”

*

Forgetting vital provisions for one ship was an oversight. Forgetting them on two ships was a process error, one that the ISC intended to correct. That would take some time and wouldn’t alleviate the situation aboard DSX-01 and DSX-02. In the meantime, Mission Control scrambled to find jetpacks, ore, and repair kits, which both ships also lacked. While looking through their resources, they realized that Sky Reef had what the two ships needed- they just needed to get them out to the Mün. Fortunately, Phoenix Aerospace had the answer: their REMO Williams, currently waiting in orbit for PPE-1 to return. A quick consultation and negotiation session later, Phoenix Aerospace agreed to fly REMO Williams over to Sky Reef to be refueled and have some of its monopropellant replaced with some ore for Newton and Halley. The station crew would also add a small cargo box stuffed with the needed jetpacks and repair kits.

So, while neither ship was originally scheduled to dock with a space station while orbiting the Mün, ISC quickly changed their plans and directed both Newton and Halley to rendezvous and dock with Phoenix Station when it arrived in münar orbit, and then wait for REMO Williams to reach the station as well. It wasn’t ideal, but it would give the two DSX crews opportunities to compare notes on their respective vessels, and Phoenix Aerospace would get their REMO to the Mün sooner…

When the Sky Reef’s station crew got their new directives, they were in the process of replacing their Power Tower solar array. An accident with their PMV shattered most of the Payload Maneuvering Vehicle’s solar arrays and both arrays on the Power Tower. Orbital Dynamics quickly printed up a replacement and sent it over. The station crew swapped out Power Towers without incident, and the broken tower deorbited since its support vehicle didn’t have the propellant needed to return to the Orbital Dynamics Shipyard. By the time that they finished their work, Sky Reef experienced its latest orbital dawn…

As Halley crossed over into the Mün’s SOI and plotted a maneuver burn to raise its periapsis, Phoenix Aerospace worked with ISC to bring REMO Williams to Sky Reef. As soon as it docked with the station, the crew refueled its propellants and converted four of its monopropellant tanks into ore tanks. Then, the station’s 3D print lab got to work printing up a pair of small cargo containers and veteran astronaut Gerrim Kerman stepped outside to attach them to REMO’s flanks. Finally, she filled the containers with jetpacks and repair kits. With the work completed, REMO departed Sky Reef for its trip to the Mün.

*

Back at the Mün, Halley took several minutes to power up her fusion engine in preparation for her orbital insertion burn. Once again, the ship’s flight computer stopped the centrifuge to conserve electric charge, but this time it shut off several lights as well. Nonetheless, Halley powered up her engine in time for the insertion burn. By engine stop, DSX-02 entered a 412.6 km by 416.9 km orbit. “The problem is the amount of charge needed to start the engine,” Rolf said between coughing fits. “We need about ten times more electric charge than the ship has. We could probably retrofit the Halley to add extra batteries, but we need a shipyard to help us...”

Three hours later, Phoenix Station and PPE-1 entered the Mün’s SOI. It took another eight hours to settle into low münar orbit, but once completed, it waited for its first visitor. DSX-02 arrived first and docked to the forward docking node. Once it took over support and power generation for the diminutive station, PPE-1 folded its solar arrays and antennas in preparation for the next phase of operations. Then, Halley demonstrated another one of its unique features, a hangar!

DSX-02 had a small hangar bay to house the ship’s Compact Payload Maneuvering Vehicle. The Compact PMV made it possible for the ship to maneuver components around without the need for a space station. In this case, the PMV latched onto PPE-1 and docked it to Halley’s dorsal docking port to make room for Newton’s arrival…

Two hours later, Newton docked with Phoenix Station, and for the first time, the two spacecraft met each other in space. Both ship crews welcomed each other and gave their counterparts a tour of their ship- something they weren’t supposed to, but there wasn’t much else to do while they waited for REMO Williams to arrive. “How do you like the sickbay,” Danwig asked. “What’s it like flying the Shuttlepod,” Sofia asked, and so on. Granted, the two crews were supposed to compare notes, but not until they swapped spacecraft…

It took another two days for REMO Williams to arrive at Phoenix Station, where Hanse vonKerman took manual control and docked the craft to the station’s ventral port. Everyone at Mission Control breathed a sigh of relief when it docked and brought much needed supplies to the two prototype Deep Space Exploration Vessels. REMO Williams resupplied PPE-1 as well as Newton with xenon gas; Shuttlepod 1 used up more than expected. Both crews also unloaded the supply ship’s stores of repair kits, jetpacks, and printer ore. Next, with its larger print shop, Halley made several new sets of plasma contactors to repair Shuttlepod 1 with. Finally, both ship crews gave REMO Williams’ Edna 1F Upper Stage a grateful sendoff as it departed Phoenix Station for its destructive deorbit. Its münar adventure was at its end. Mission Accomplished!

With both prototypes resupplied, it was time for them to depart Phoenix Station and resume their respective space trials. Newton departed first, using her gravitic engines in reverse to back away, to free the aft docking port for PPE-1. Then, after putting the Power and Propulsion Element back in its place, Halley stowed its Compact PMV and resumed its mission as well. And on behalf of the International Space Consortium, Gene Kerman sent Phoenix Aerospace’s CEO a personal thank you letter for their help with resupplying both experimental spacecraft.

Little did Gene know that Phoenix Aerospace was in serious financial trouble.

*

Newton (DSX-01) and Halley (DSX-02) both departed the Mün not long after resupplying at Phoenix Station. Halley’s crew were envious of Newton; they had to wait a few minutes to charge up the fusion engine before igniting it, compared to just a few seconds to start Newton’s gravitic engines. Both ships exited the Mün’s SOI within hours of each other…

The boring parts of spaceflight stuck again as both ships fell back down Kerbin’s gravity well and executed another burn to reach Minmus in a couple of weeks. Someone suggested that they “try out” each ship’s cryobay to relieve boredom, but with no stasis fluid aboard either ship, that was out of the question, So, both crews occupied their time by running various drills to test their respective ship’s capabilities, met with the designers over video link, and gave their feedback. They had hundreds of comments like:

‘We love the shuttlepod!’

‘The sickbay is a must for DSEV.’

‘The hangar is great for protecting small craft from micro meteors.’

‘We have gravity engines. Do we really have to wait for orbital launch windows?’

‘With a crew of 12, we could have three standard watches of four hours each.’

‘Can we get actual beds to sleep in? I feel like a hitchhiker stuck in a storage can. Even hot bunking would be better than this!’

‘Every time we power up the fusion engine, we lose the lights!’

Both design teams recorded and collated everything and tried not to take the criticisms personally. They also knew that they’d have to repeat the process when the crews swapped ships…

As the Buffabus reached the midpoint of their journey back to Duna Base, DSX-01 and DSX-02 reached Minmus’ SOI. For the all-veteran crews, it wasn’t anything new to them, but they welcomed the sight nonetheless. For their next stops, Newton navigated towards Gateway Station while Halley headed towards Drax Aerospace’s Minmus Fuel Depot to refuel. Strictly speaking, Halley didn’t need to refuel as she had over 75% of her propellant remaining. But the space trials required both experimental Deep Space Exploration Vessels to test their refueling capabilities.

DSX-02 had no trouble docking to the Minmus Fuel Depot, but DSX-01 had to perform some careful maneuvering to link up with Gateway Station, including flipping upside down relative to the station’s orientation- it was a tight fit! “Halley better park on Magellan’s nose,” Hanse vonKerman noted.

Newton’s arrival at Gateway Station provided a stark contrast between DSX-01- one of the most advanced spacecraft in Kerbal history- and Magellan, the Mϋnar Shuttle Module, first flown during the Shuttle era. Originally just a simple orbital transfer vehicle that used a cryogenic space tug to get around, Magellan underwent several refits as it gained and lost various space tug designs, obtained a laboratory/support module, and was eventually cut apart and rebuilt- in orbit- to add additional crew quarters. Its final configuration, Magellan was powered by a nuclear variant of Orbital Dynamics’ Orbital Cargo Transfer Vehicle while its laboratory/support module sprouted various converters and external storage boxes and other equipment tacked on in “after the fact” fashion. For its day, Magellan offered much more comfortable living and working arrangements for crews heading to and from Kerbin’s müns compared to the cramped quarters of the Münflight-era K-20 KerbalSoar. But its days were numbered- the winner of the DSEV(X) competition would replace Magellan and help train crews to fly the next-generation Deep Space Exploration Vessels.

*

With Karl vonKerman finally feeling better, he and Hanse vonKerman took Shuttlepod 1 down to Minmus’ surface for their away mission. They had no trouble undocking from Newton and deorbiting; a half-hour later, the two kerbonauts were hovering over the surface and searching for their landing zone. “The Shuttlepod needs lights,” Hanse commented- Shuttlepod 1 was landing at night.

“There it is,” Karl said, pointing towards the ground. Despite the years, the object’s LED lights still functioned. Shuttlepod 1 landed on Minmus for the first time, right next to a piece of history. Drakken Hause 3 was just over eleven years old, but it had been abandoned not long after Project Laythe reached Jool. It was a product of the latter half of the Kold War, what the Kermans had called the “Shuttle Era” after their Shuttle Launch System.

While the Kermans focused on launching and building their “Starlab” Kerbin Orbiting Station via their Shuttle orbiters, the vonKerman Republic used their tried-and-true Fliegenross (“Flying Steed” in Kerman) rockets to launch their own stations- the Drakken Hause series- into orbit. Though ailing and badly in need of retirement, Drakken Hause 1, known officially as Drakken Palast, was still in use today, circling endlessly in Low Kerbin Orbit.

Drakken Hause 3 was a product of the Kold War, built during a time when the vonKerman Republic and the Kerman States competed for the prestige of space exploration. The outpost was the VKR’s answer to Billstown, the Kerman States’ outpost on the Mün. Originally slated to expand Drakken House 1, the third Drakken station was hastily fitted with wheels and further modified to handle landing on Minmus. Later, the VKR sent three additional modules to extract ore and process it into propellants that were then shipped to awaiting tankers parked at Unity Station. The whole operation was a testament to vonKerman ingenuity- but it was rendered obsolete thanks to the vehicle sitting next to it.

The two kerbonauts spent the better part of an hour switching on the base’s lights and performing diagnostics and noting the smell of aging plastic in the air. By Minmus sunrise, they’d completed their tasks and headed outside to inspect another Kold War relic sitting a couple hundred meters away.

“A first-generation Drakken Tanker Tug, modified to handle landing on Minmus,” Karl said, whistling. “My dad worked on these. The original design lacked a heat shield up front and landing legs on the bottom. This iteration was the first attempt at bringing propellants back to Kerbin.”

“They didn’t work too well, as I recall,” Hanse mentioned.

“No, they didn’t. They kept exploding during aerobraking. We eventually switched to the inflatable heat shield design, of course, but we kept this one around to ferry propellant up to Unity Station…”

The two kerbals made their way back to Shuttlepod 1 for the return trip to orbit. Karl noticed that the lower plasma contactors were gone- again. “Those bottom contactors are in the wrong place,” Hanse noted. Before long, they were back in orbit and on their way to their next destination. Three and a half hours later, they arrived. They found an old Fliegenross Upper Stage that had orbited Minmus for over fifteen years. There were no records of what mission it belonged to, but it looked like one that delivered a landing craft to Minmus’ surface. There was nothing else they could do with it, so Shuttlepod 1 headed back to Gateway Station and arrived after a day of travel…

With their tasks completed at Minmus, Newton and Halley departed the Mint Mün and headed back to Kerbin. 11 days later, they both docked to Sky Reef for a brief stopover and crew swap. Over the next three weeks, the two crews evaluated the other ship, provided their feedback, and wrote endless evaluation reports before the two vessels returned to Sky Reef and boarded their ride for the trip home. The International Space Consortium thanked both DSEV(X) teams for their efforts and began their final evaluation process.

December 1, 2023

Rex Wall IV from Aviation Leak here, can you elaborate on what a "landing pylon" is?

November 25, 2023

I finished some new Slim suits based on an old mission report...

November 25, 2023

I've spent too much time on this, but I've gone ahead and recreated the Kerbfleet uniforms:

Anyway, if allowed, I'll publish the Kerbfleet mod for those interested.

Spoiler

November 24, 2023

Spoiler

Kerbfleet Pilot Slim suit, WIP

In case the original suits can't be found

November 23, 2023

I built some gravimetric generator nacelles to enable Scout to haul asteroids:

It can just barely move JNSQ Type A asteroids around, so I needed more powerful generators:

Now she can haul the mail.

November 23, 2023

@Nimzo Kerman:

This recreation is as faithful as I can get while adhering to modernized KSP and mods. Some parts of the ship had to change due to limited screenshot coverage and updates to the game and mods. Hopefully Bill can explain the differences...

At a minimum you'll need:

Wild Blue Tools: https://github.com/Angel-125/WildBlueTools/releases/tag/v1.89.2

Kerbal Planetary Base Systems: https://spacedock.info/mod/173/Kerbal Planetary Base Systems#

Kerbfleet Flags (with the craft file, minus life support parts): See DM.

I highly recommend Restock and Restock Plus if you haven't seen those already.

I also found the Counter-Kerbin: by @GregroxMun: https://spacedock.info/mod/502/Kerbfleet Planet Pack: The Kerbulus System

One more teaser image and a theme song: