Angelo Kerman

I haven't tried those recently, have you tried using Kerbal Inventory System/Kerbal Attachment System to attach them instead of stock EVA Construction?

That room was fun to make. I had to add the demotivational posters to it since it was a boardroom type thing. Best of all you can change the pictures just by clicking on them. Happy New Year!

You need to place the part on the tank that has resources that you want distributed. Once placed you can pump the resources throughout the vessel for local distribution, or to the remote vessel's resource tank that has a pump set to remotely receive the resources.

I would set DumpExcess to false and add FlowMode = ALL_VESSEL to your output resource. That way, when the ship's EC is full, the generator stops producing ElectricCharge.

Sorry but no. B9PS is too complicated to support

Blueshift 1.9.1 is now available: - Hotfix to auto-deactivate generators that are integrated with warp engines when the warp engine is shut down. Similarly, integrated warp coils will auto-enable/disable upon engine activation and shutdown.

If the gate lets you teleport even though it has no Graviolium but the gate should be paying the toll then it’s a bug.

If set to false then the gate itself pays the toll.

Yes. Unfortunately, kerbals gating to space and getting stuck is a known issue. The game can’t figure out that the kerbal is in space.

Lol, guard those bags of dried sea bugs like they're your lifeblood, Kerny! You know you can't eat just one... I wonder what's on that data stick? Old images? Documents? Firmware updates for an ASUS motherboard's BIOS?

Maybe you can help with that? I don't use B9PS for tank switching so I'm not too familiar with that system. I'd appreciate any help that you can provide. Yeah, it gives more stuff to do on EVA (Pathfinder was made for KIS for the same reason) back before Breaking Ground was a thing.

It's been a few years since I made that, but GoldStrike is a mini-game where you drive around, use the Gold Digger drill (Pathfinder) or the B2 Geology Lab (Buffalo 2) to find resource deposits. These resource deposits are limited, and don't show up in the stock scanners, but you'll see them via waypoints. You can find Aurum (gold) and Graviolium that way, and with Classic Stock Resources, you can find Gemstones and Precious Metals as well. You can define a resource that can be prospected via a GOLDSTRIKE node: //Each GOLDSTRIKE node tells Gold Strike what valueable resource is available as a lode, how much is available in a given area, and how much to increase the amount when striking it rich. You can easily add other GOLDSTRIKE config nodes. GOLDSTRIKE { resourceName = Aurum //Restricts where the resource can be found. Separate multiple types by semicolon. Options: Planetary;Oceanic;Atmospheric;Exospheric. Planetary is default. resourceTypes = Planetary //List of planet names, separated by semicolon, where the resource can be found. Default: Any, which means any planet can have the resource. planetsFound = Any //List of biome names, separated by semicolon, where the resource can be found. Default: Any, which means any biome can have the resource. biomesFound = Any //The minimum distance in kilometers between prospect attempts required in order to include the resource among the possible prospected resources. //Default is 3 kilometers. //Ex: Aurum, Gemstones, and PreciousMetals all require you to travel at least 3 kilometers before they become available. Assume that Blutonium could be found every 5km. //If you only travel 2km before making a prospect attempt, then none of the resources will be found. If you travel 6km, then Aurum, Gemstones, PreciousMetals, and Blutonium //will all be potential candidates for prospecting. You still need to make a successful prospecting check to obtain a node. minProspectDistance = 3 //Minimum required altitude in order for the resource to be a prospecting candidate. Can be negative for below sea level. Default is a double.MinValue. //minAltitude = 0 //Maxiumum required altitude in order for the resource to be a prospecting candidate. Can be negative for below sea level. Default is double.MaxValue. //maxAltitude = -1000 //If near an anomaly, some resources are more likely to occur than others. This parameter indicates how likely the resource will be found near an anomaly. //anomalyChance = 65 //Minimum units in the lode minAmount = 200 //Maximum units in the lode maxAmount = 4000 //Roll well enough, and multiply the lode size by this multiplier motherlodeMultiplier = 1.5 } As you can see from the config node, you can define resources for a variety of different locations and conditions. Technically GoldStrike supports all environments but I only really tested it on Planetary. But yeah, you can get creative, and only find Graviolium next to an anomaly, for instance, or other special resources on specific planets- without defining them using the stock resource definition system, thus preventing regular drills from finding them. Once you find a lode and park your craft next to the waypoint on the map, you can dig up the resource. Pathfinder has the WBIGoldStrikeDrill, which replaces the stock drill plugin and digs up every resource in the biome, not just a single resource like Ore. The drill will automatically dig up nearby lode resources as well, and automatically deduct what it drills from the lode's resource amount. I vaguely recall being smart enough to not dig up the lode's resource if you don't have tank space for it.

I love the landing during an eclipse.

"Ah sweah, tha ga durn acceleratah ga stuck!"

No, the variants are all integrated.

TBH I've had a lot of problems with stock EVA Construction, and not just with Buffalo 2. You could try using a combination of stock EVA construction to put the parts on the ground and Kerbal Inventory System to build them. Maybe that'll work? I seriously hope that KSP 2 has a much better construction system.

I think @linuxgurugamer's mod calculates the volume.

That ModuleStorablePart comes from Sandcastle, so any parts that have ModuleCargoPart would would need a ModuleManager patch to replace it with ModuleStorablePart. You'd have to make the patch so that it applies only if Sandcastle is installed, and it would have to be applied after KSP_PartVolume. Other than that, it would be straightforward to do.

Chapter 35 After sailing through space for months, Estonian 2, the improved version of the Ministry of Space’s Duna lander- and the last of the Second Duna Fleet- finally arrived at the Rusty Planet. Its predecessor suffered catastrophic damage during its attempt to land, and that was a fate that its successor hoped to avoid. If it worked, then the MoS would have what it needed to safely reach Duna’s surface and return to orbit. Soon, they’d find out. Two hours after entering the planet’s SOI, the spacecraft made a 900 m/sec orbital maneuver to reduce its periapsis and ensure that it orbited Duna in the right direction. Another 1,576 m/sec burn a day later circularized the spacecraft in low Duna orbit. A third, 400 m/sec burn aligned its orbit with the Duna Basecamp. Though extreme, the nuclear propulsion tug had ample propellant to accomplish the tasks even with its payload. Safely in low Duna orbit, Ministry of Space’s Mission Control started Estonian 2’s monopropellant power unit. Then they commanded it to perform final systems checks before separating from the interplanetary tug. It automatically plotted a deorbit maneuver that hopefully would land the craft near Knights Landing, the future site of the MoS’ Duna base. Thirty-three minutes later, it performed its deorbit burn. Four and a half minutes later, on Jool 20, 2003, Estonian 2 entered Duna’s atmosphere and began slowing down. Learning from the lessons of the past, the lander kept its descent motor in hopes of preventing the craft from flipping around like its predecessor did during its landing attempt. Combined with a shallow entry profile, that worked. At 38,000 meters altitude, plasma fire licked the sides of the craft as it continued its course. Within just a couple of minutes, it kept its proper attitude and sailed over the notable crater where Knights Landing was located. Unfortunately, a navigation error left the spacecraft several kilometers short of the target, but that was secondary to its mission. At 9,500 meters altitude, Estonian 2 discarded its descent motor and kicked open its heat shield to reveal its aerospike. The engine performed both descent and ascent burns. At 6,000 meters, the lander deployed its airbrakes and chutes. Unlike its predecessor, Estonian 2 only had drogue chutes- Estonian 1’s main chutes failed to deploy in the thin atmosphere. As the drogue chutes fully inflated, Estonian 2’s landing gear deployed, ready for landing. At 500 meters, the lander ignited its landing spike, but it was a little too late. The spacecraft landed hard- 23 meters per second- and crushed its landing gear. But it was otherwise intact. Estonian 2 landed 11 kilometers away from Knights Landing. Despite the mishap, they’d done it! Most of Estonian 2’s science instruments were useless due to Duna Schaffer arriving earlier, but the mystery goo still had some results to yield. And pretending like it had a crew aboard, the lander deployed its ladder. But there wasn’t much else to do- except for one more thing. Estonian 2 performed its final systems checks two hours later. Then, after shedding its entry, descent, and landing section, the lander reignited its aerospike engine and lifted off the surface, using its EDL section as a launch pad. It worked! Estonian 2 entered an 83.9 km by 87.8 km orbit, with delta-v to spare. Despite the initial setback, the Ministry of Space made history with the first launch into orbit from Duna’s surface. As a final test, Estonian 2 performed a series of burns that placed it next to Duna Basecamp just three hours later, proving that the lander had sufficient delta-v to rendezvous with an orbiting spacecraft. then, the lander performed an automated docking to one of the smaller service ports on the cluster of interplanetary tugs. There was no doubt about it, the Ministry of Space had the technology to send kerbals to Duna’s surface and back again. They just had to wait another year for the launch window to Duna to open again. * Back in Duna orbit, MoSMC had some tidying up to do. First, they shuttled MoS Tug 3 over to Duna Basecamp and donated its drop tanks before joining MoS Tug 1. Then, they did the same thing with MoS Tug 4. Next, they undocked Duna Basecamp, and moved the tank that previously hosted it to the back of the chain of tanks. Then, the cluster of MoS Interplanetary Tugs cast off from the new completed Duna Depot and temporarily reconnected with Duna Basecamp. Afterwards, the Duna Science Probe cast off from the Depot in preparation to return to Kerbin in 318 days. Then, Estonian 2 departed the MoS Tugs to be visited by future travelers. Finally, Duna Basecamp left the tugs so that they too could return to Kerbin in 318 days. At last, the Ministry of Space proudly announced that the Second Duna Fleet had accomplished its mission. * In the middle of the night, a Jool Wide Load lifted off from Pad B. But instead of heading eastward, it arced westward in a retrograde direction. That took considerable clout on Drax Aerospace’s part to pull off… Right on schedule, the solids dropped away and safely landed in the desert away from any populated area. A few minutes later, the Jool Propulsion Module dropped away from the stack after expending all the propellants in the core stage tank, and the core stage tank followed soon after. Within seconds, the stripped down Jool Upper Stage ignited its engines and continued the climb into orbit. Despite going retrograde, the rocket still attained a 141.4 km by 158.1 km orbit and then aligned orbital planes with its target. Then, having done its job, the Jool Upper Stage offloaded its payload- the Drax Asteroid Miner- and deorbited. A few days later, Drax launched a pair of tankers to fuel the Miner. Once refueled, Drax Asteroid Miner extended its solar arrays. Then at the right time, it performed a brief burn with its secondary KR-84 Ocelot motors as well as its six tertiary ion engines. Two days later, the Miner rendezvoused with Asteroid VPI-273, a B-class asteroid. To the disappointment of Drax Aerospace, it wasn’t like Orbital Dynamics' "Magic Boulder", with its glowing veins of strontium aluminate. Nonetheless, the Drax Asteroid Miner took aim, armed its grappling claw, and dove for the target. A few minutes later, the Miner latched onto the asteroid- and made history as the first spacecraft to grab an asteroid in interplanetary space. The World’s First Organization even recognized the event as the first construction of a “space station” in solar orbit. The spacecraft’s resource scanner took its readings and discovered a cache of blutonium, ore, water, rock, metal ore, gemstones, gray water, hexagen, hydrokerbon, minerite, precious metals, and zeonium. It also discovered a trace amount of a substance that the scanners could not identify. They’d have to table that mystery for later, though, they had a job to do. Using the same techniques pioneered by Orbital Dynamics- and possibly the same technology- the Drax Asteroid Miner sorted the resources that it drilled and stored them in the asteroid itself as it hollowed it out. But in an impressive first, the Miner fired up its DA-5 Catapult, a new engine that the company engineers designed. The Catapult took waste rock, heated it to a molten state, and expelled it to produce thrust. While not terribly efficient, the engine made it much easier to move asteroids around due to the steady supply of waste rock. Combined with its secondary LFO engines- which needed the craft’s fuel processors to produce propellant for- the Asteroid Miner could slow VPI-273 enough to enter Low Kerbin Orbit. The Drax Asteroid Miner made an intercept burn with Kerbin, followed by three course correction burns three days later. Seven days after that, the Miner would reenter Kerbin’s SOI. By that time, the resource extractors would be done processing the asteroid. * ULM-2 dropped down from orbit and landed at Minmus Base, carrying the base’s new command module and, at last, the lab. After it landed, Tesen took control of ULM-2 and wiggled the command module into place. Then, after undocking from the stack, she guided the lab module into its spot as well. And after refueling ULM-2, she detached it from the lab and sent it on its way back to Gateway Station. They had only one more module left… Nine days later, the last Minmus Base component, the Greenhouse Module, arrived at Gateway Station via JUS-4. Once delivered, the space tug departed the station and took up residence at Drax Fuel Depot 2… Back at Gateway, ULM-2 undocked from the station with the Greenhouse module in tow and headed for the surface. It landed at Minmus Base a half-hour later, where Tesen took control. She slowly walked it over to a spot next to the lab. Then she made some minor adjustments to dock it to the base. Once everything clicked into place, the whole crew cheered. Minmus Base was complete! KSP Mission Control congratulated the teams for all their hard work to make this momentous occasion possible and praised everyone for their cooperation. The base had everything it needed to be self-sufficient and was ready to accept more crews- once the second Ostrich-class lander pod was built and delivered. Minmus Base was also set up for expansion later- but that project was for another time. Today, they crew had cause to celebrate. * With their contract to build Minmus Base modules completed, the Orbital Dynamics Shipyard turned their attention once again to their own projects. First, they built the Finch Automated Command Module, affectionately called BirbStar, to support automated landing of spacecraft. BirbStar probes would take the place of the Finch OTV and could be stationed at Oasis, freeing up the kermanned OTV for other tasks. Once completed, Calming Kerman took a spacewalk to examine the construction manipulator and perform some maintenance work. Sometimes, the 3D printer nozzles got residue on them during their additive manufacturing, and they needed to be cleaned. The engineer carefully worked through the procedures and documented everything, including taking lots of pictures. When he finished, he went to the Sandcastle 3D printer module to run diagnostics. Once everything checked out, he had some free time on his hands, so he decided to record a video to his folks back home. That’s when Willorf Kerman, the ranking engineer in charge of the station, noticed the unusually high data bandwidth being taken up by Calming. “You’ve been sending a lot of videos lately, Calming,” Willorf said on a private channel. Calming froze and looked nervously about. “Uh, I’m just excited to be here in space,” he said nervously. “Just sharing with my family is all. I miss them.” “Okay,” Willorf answered. She knew what it was like to be away from family. “You’re using video compression, right?” “Yeah, highest setting,” Calming responded. “We uh, got an update recently, maybe it’s a new compression algorithm?” “Yeah, maybe,” Willorf conceded. She shrugged. Something was off, but she had to table the conversation for now. “How are the diagnostics looking,” She asked, changing the subject. “All good, we’re ready to build the next components,” Calming responded. He called up the next set of plans, the Finch Core Support Tank, and started up the construction manipulator. It would take a couple of hours to complete. He had time on his hands, so he decided to catch the latest episode of Galaxy Trek… A couple of hours later, the printer produced the Support Tank. After moving it over to the BirbStar, the shipwrights repeated the process with a second tank. Then, over the course of the next week, they built the new Converter Module, the Finch Core Tank, and finally, a Finch Landing System. These components were all needed for the next phase of operations on the Mϋn- a mining base to refine water into propellants. They needed that base to economically refuel the OCTV for the trip back to Kerbin. But before that, they needed Dauntless to fuel up the new modules for the trip to the Mϋn… After round the clock fueling flights, BirbStar departed the Orbital Dynamics Shipyard, aligned planes, and burned for Kerbin's nearest natural satellite. * It took several orbits to complete- and several times the engines nearly overheated- but at last, the Drax Asteroid Miner entered low orbit around Kerbin. As an added measure, the Miner matched orbital planes with Drax Fuel Depot. The feat proved once again that Drax Aerospace could compete in any space industry, and the press loved it. Drax Kerman looked at the resource manifest for VPI-273. It wasn’t impressive, but the primary mission was to test the technology needed to capture an asteroid and bring it back to Kerbin. At least the water and gray water would supply the depot for a while, and the combined value of the gemstones, precious metals, and other resources would pay for the test mission. The metal ore also had a useful purpose. The “mystery substance” that the scanners detected was puzzling, but the drills only recovered a little over 200 units of the stuff, so it could probably be safely ignored. As impressive a feat as it was to bring the asteroid into low orbit, Drax set his sights on a much larger asteroid, one that he hoped would be even more impressive than that “Magic Boulder” claimed by Orbital Dynamics… * Three days after departing from Orbital Dynamics Shipyard, BirbStar entered the Mϋn’s sphere of influence, and two hours after that, it executed a maneuver to correct its orbital direction. It took another two days for the spacecraft to rendezvous and dock with Oasis. Meanwhile, back at the Shipyard, workers completed assembly on the Finch Drill Module as well as an Oasis Power Tower, connected them to an OCTV, and sent them on their way to the Mϋn. Wasting no time, the shipwrights cleaned the yard and immediately began building three sets of Finch Core Tanks and stacking them one atop the other. By the time that they finished, the OCTV/Drill Module arrived at the Mϋn… Once the OCTV/Drill Module docked at Oasis, ODMC began reconfiguring the various spacecraft for their next mission. First, they remotely piloted the station’s PMV, programming it to relocate one of the station’s docking adapters. Next, they commanded it to move the spare Power Tower and placed it atop the Finch Converter module brought by BirbStar. Then, after grabbing onto BirbStar’s tank module, the propulsion section detached and moved over to the newly opened docking port, dropped off the tank module, and reconnected with the lander. Finally, the OCTV repositioned itself and the ODIN Fuel Depot onto Oasis’ forward docking port in preparation for its next maneuver. An hour later, it carefully performed an orbital plane change maneuver so that Oasis could reach any point on the Mϋn’s surface. Given how long it took, the tug needed to make a second plane change maneuver. But not before BirbStar had to depart. The automated lander undocked from Oasis and performed its deorbit maneuver eight minutes later. After an hour of falling, BirbStar approached a landing zone designated SK0-97. Ten minutes later, the lander lit its landing rockets - and promptly burned off its underside solar arrays. ODMC made a note to have a word with the Orbital Dynamics Shipyard crews to update their propulsion system designs. Fortunately, the spacecraft still landed successfully. Time was of the essence, so Orbital Dynamics Mission Control had to act fast. Once BirbStar found a relatively flat spot, it quickly rolled to a stop, undocked its front and back sections from the converter module, and connected them together, leaving the converter module and its power tower behind. Then, right after Oasis finished realigning its orbit, the automated lander lifted off to meet up with the station. It had a nine-hour flight, so ODMC took the time to rearrange the modules at the station and get ready for the next delivery… When BirbStar arrived at Oasis, ODMC directed it to the primary ventral port and then parked the propulsion section onto the drilling module. Then, after repositioning the front half to make room for the power tower, the back half rejoined the front. Some refueling later, BirbStar was ready for its next trip to the surface… The lander departed Oasis soon after, but it had a two-day wait for its deorbit burn. Meanwhile, Oasis used the OCTV to lower its periapsis to make it easier for landers to reach it in the future. Then, right on time, BirbStar made its deorbit maneuver and headed for the surface and landed a hour later. In a series of pre-programmed maneuvers, BirbStar separated into two halves, maneuvered the drilling module into place, and docked it to converter module. After rejoining the two halves, BirbStar docked with the growing mining station. Once ODMC deployed the drills and turned on the converters, the mining station registered positive flow for gray water, which was then converted into cryogenic propellants. At last, the Orbital Dynamics Mϋnar Mining Station was operational! All they had to do was wait a few days to refuel BirbStar before it returned to Oasis to pick up the additional core tank module for the mining station. Then they could deploy the second power tower and begin hauling propellants from the surface to Oasis. But for now, Orbital Dynamics had cause to celebrate. * For the last week, as Drax brought their asteroid into Kerbin orbit and Orbital Dynamics built their mining base, Adsii had been touring the warehouses of the vonKerman Republic’s Museum of Natural History in search of photographs. Specifically, he wanted to find pictures of expeditions to the Pyramid of Tut-Un Jeb-Anh. The Museum’s records were meticulously kept- except for piles of them that either displaced photos to different boxes- or different boxes in different warehouses- or went outright missing. Despite the difficulties, he still managed to find many pictures from various trips to the Pyramid. While what he found was fascinating, it wasn’t what he’d hoped for. But he was nearing the end of their list of records, and he was on his last warehouse for the day. Regardless of what he found, Adsii was looking forward to treating himself to a nice dinner as a reward. He really wanted to try some hamburger pannfisch… After going through the records on the first couple of floors, Adsii took a deep breath and climbed to the third floor of the warehouse. It’s so high up, he thought to himself as he told himself to not look down- and promptly did it anyway. He distracted himself by looking at the replica miniature monolith- at least that’s what it looked like- standing in the corner and collecting dust. It looked real to Adsii, and he wondered if the vonKermans visited Kape Kerman before the Kerman States built the Kerbal Space Center. With his tummy starting to growl, Adsii turned back to business and found the documents cabinet that he was looking for. Being methodical, he started with the bottom drawer, opened it, and began thumbing through the photos absentmindedly. One of the photos caught his attention, and suddenly, Adsii’s thoughts of dinner quickly vanished. He pulled the photo out to get a closer look. There it was, unmistakably, a black and white picture of a team of four scientists and two young students, with an intact wall of hieroglyphs. There were a lot of symbols that he didn’t recognize, so he’d have to wait until he got home to translate them. Adsii looked on the back of the photo. It was dated 4/15/1953, and it had the names of all the kerbals in the picture, from right to left, of the professors and students. He read the last name on the list, flipped the picture over, and looked at the leftmost kerbal. Then he gasped. The last name on the list was Drax Kerman. * Flying the new tiltrotor was a lot of fun! The aircraft was responsive, fast, and it had a lot of potential for shipboard storage- its wing could pivot until it was parallel to the modular fuselage. Speaking of fuselages, Scott liked the new Buffalo Base design that Frolie’s team put together from the modular rover system and looked forward to spending time in it- especially now that their obligations to KSP’s Minmus Base were now completed. Soon, the Shipyard would be finishing construction on Oasis, churning out Buffalo Base modules for their mϋnar tourist complex, and gearing up for their trips to Minmus. It had taken years to reach this point, but they finally had the infrastructure that they needed! It was also hard to believe that soon, this mission report will come to an end, but another is in the works Orbital Dynamics would fulfill their original tourism contracts. “Scott, it’s Sara,” the cockpit radio squawked, interrupting his reverie. “When you get done, can you meet me in my office?” “Sure thing,” Scott radioed back. Now he was curious. What’s going on? He thought to himself. He’d find out in a few minutes… “We got the results of the Magic Boulder audit,” she began. “They agree with our reported amounts of aurum, precious metals, nitronite, minerite, hexagen, gemstones, metal ore, and of course the blutonium.” She paused briefly before continuing. “As you know, the audit also required us to reveal that the Magic Boulder has 122,689 units of exotic matter,” Sara said. “They valued it at 1,200 Funds per unit, for a total of 147,226,800 Funds. That’s about 3.87 times the value of all the other valuables in the asteroid combined. The catch is that they want it.” “The exotic matter? How much,” Scott was afraid to ask. “Not just the exotic stuff, Scott. They want all of it. They want the entire asteroid.”

Thanks! You can find Da Choppah in the Ships/SPH folder.

Ok, here is 1.3.1 to disable the B9PS patch for now.

Try renaming B9PS.cfg to B9PS.txt and see if that helps. It is in the Patches folder. Are you using any of the configs in the Extras folder? Thanks! I am going to spend some time working on my mission reports and learning Blender (my 3D art program's license expires soon). Assuming that existing art assents can't be ported over, I expect to start over with my 3D models- but I'm limiting myself to 2-3 mods at most. This time around I want to play the game more than mod it... If by chance it's easy to port 3D models over then I can think about bringing the Mk33 to KSP 2.

@RobFalcon That looks great, thanks for sharing!

Mk-33 v 1.3.0 is now available: New Parts - Mk-33 Aft Tank (Hollow) - Mk-33 Cargo Ramp - KR-2200C "Tyranosaurus" Aerospike Engine Changes - Mk-33 now supports Community Category Kit. - Fixed mesh offset issues with the mid-tank. - Fixed landing gear lighting up the planet. - Fixed KSP complaining about missing part modules in the sample craft. - Fixed Module Manager patches in the Extras folder that support cryogenic propellants for Classic Stock Resources and Community Resource Pack. - Fixed Mk-33 Main Wing failing to surface attach when Wild Blue Decals is installed. NOTE: You'll need an updated version of Wild Blue Decals. Hard to believe it, but I've finished all the parts and mods that I want to use in KSP 1! Time to retire and enjoy the game for a few months...