Angelo Kerman

Can you provide the exact steps to how you are adding graviolium into your Blueshift FTL Propellant tanks? I have both Kerbal Flying Saucers and Blueshift installed and I have no issues with Graviolium being empty when I launch my starships. And if you have Kerbal Flying Saucers installed then you can also collect Graviolium using the Stardust Graviolium Collector, and from the Space Center you can produce Graviolium for purchase. You can also mine Graviolium from Dres...

Makes sense. So I would need to find the furthest planet from Kerbol, whatever planet that is, and use that as a reference for the SOI of Kerbol.

Great, thank you for the information, this helps! It sounds like what I would need to do is for the central system, define an artificial SOI based on the last planet to orbit it- like Eeloo in the stock game, and then look at the SOI parameters for satellite stars. Those two pieces of information will tell me where interstellar space is. I would also need to identify Kerbol...

Thank you, that definitely helps. Is your setup typical for making planetary mods with multiple star systems? Do I understand that other stars have an SOI like planets do?

I've been writing software as a profession for many years, so I had a head start on how to write code. For KSP itself, I went to the add-on development forum and looked at the getting started guides and found the KSP API that gave me a sense of what's possible. And since plugin authors are required to post their source code, I also looked at what others did to see how they used the API- and am happy to provide the source so others can do the same. As for the photonic boom, that's a sound byte from a NASA video of a space shuttle coming in to land. I'm partial to that sound clip, but you're certainly welcome to change the sound in your game. Can you provide the exact steps to reproduce this issue? I don't see it on my end. I'm able to use the cheat menu to fill the Blueshift tanks with Graviolium. Only the tanks from Kerbal Flying Saucers presently remove all Graviolium before launch.

@StarCrusher96 For a mod like Galaxies Unbound, which has multiple star systems, how is that set up? Does each star orbit around a common central object? Do stars orbit each other? I ask because I am trying to figure out how to tell when a vessel reaches interstellar space. If I can figure it out then I can give a boost to a vessel’s warp speed...

Well, I spent the day trying to figure out how to make warp travel work while in timewarp. Suffice to say that the way to do it it really messes with the vessel's velocity. It's doable but there's a lot of work involved to make it work right. It occurs to me that instead of trying to warp during timewarp, the ship ought to warp faster when outside of a solar system, much like there's a speed brake while inside a planetary SOI. My original concept for the Mk2 Warp engine parts were exactly that: What I found is that the part would be unwieldy on a space plane, and add a lot of mass to a craft trying to reach orbit. It would also need extra bits and pieces to protect it from the airstream while folded. Plus, folding warp rings have been done for a long time, and I decided that it was time to do something different. What I haven't seen are a variety of warp coils- especially rings that you can dock to and fly away with.

I'm not seeing that issue with Graviolium going missing. Anybody else seeing that? Definitely keep thrust limiter to 100%.

When you arrive in a planetary Sphere Of Influence, the warp engine won't go as fast, and you can use its thrust limiter to slow down even more. That will let you move your craft around and use the planet's gravity to your advantage. So, after arriving, warp around until gravity will pull your ship towards the planet. As your velocity carries you away from the planet, you'll slow down due to the pull of gravity. As you move away from the planet, warp back down towards the planet to lose even more speed. Once you've done that a few times, you can then warp around to circularize your orbit. I'll add an infographic to explain that along with where to get Graviolium from. The jump gates and jump engines will not have this problem. You'll just select the target and perform the jump. Your ship will end up in a stable orbit (barring weird KSP issues) next to the target... or somewhere else if you misjump... Not at present. KSP automatically cuts the engine throttle during timewarp, and the warp engine is no different. But next update I can add a "Cruise Control" feature. If enabled, the warp engine will remember your previous throttle setting when you enter timewarp and continue going warp speed.

LOL! Sounds like something that Squad did messed up EVA resource consumption. That didn't happen before KSP 1.11. I'm waiting on KSP 1.11.1, but I'm also already thinking of a Snack Pack stock cargo part that the kerbals on EVA would consume. Thinking aloud here... You'd be able to "Pack Snacks" in a crew module like a Hitchhikker, Mk3 cabin, or Mk2 cabin. That will pull resources from your vessel to create a Snack Pack and store it in your stock inventory. Then take a Snack Pack with you on EVA. When the snack timer goes off, for kerbals on EVA, you'll receive a message ("You're not you when you're hungry") have a minute or so to consume your SnackPack before you incur penalties. Finally, you'd have a new "Take a Snack break" in the EVA part action window that will consume the Snack Pack.

I've not seen that issue. Make sure you install everything into the GameData/WildBlueIndustries/Mk-33 folder I've not tested this with RO.

Chapter 3 “We proposed the Mk-33 as a single stage to orbit launcher,” Lyta A. Kerman, President of the Polecat Spaceworks Division said. Formerly known as Polecat Ironworks, a division of Stonewell Aviation (the company that built the Lindor 5’s second stage), the division earned a reputation for creating innovative aircraft designs during the Last War. When the Shuttle Launch System was proposed, Polecat set up shop on Welcome Back Island after the previous tenants moved out so that they could be closer to Kerman Space Center, and they changed their name to Polecat Spaceworks as part of their bid to win the Shuttle contract. They had hoped to revitalize their division with a revolutionary launch vehicle, but their gamble failed. The division barely survived thanks to subcontracts from the Shuttle Program, but with that program concluded, things were looking grim… “It was a novel approach to the shuttle program at the time,” Lyta continued. “It still is. We finished about eighty percent of the spaceframe before we ran into manufacturing problems with the karbon komposite fuel tanks. They kept losing lamination and exploding when pressurized. We proposed to solve the problem by using metal tanks but that incurred a significant payload penalty. So, KSP moved on with the Drax shuttle… We tried to get our parent company to revive the project for KOTS, of course, but they denied our request. They said they wanted to focus on their commercial aviation business instead.” “So, it could fly if you finished it,” Scott said. It was not a question. Lyta nodded. “We’d need new linear aerospikes- the test models are in museums. We’d have to dig up the plans and build new fuel tanks, finish the fuselage, attach the wings, add the A.R.M.O.R. panels…” “Armor, the Mk-33 was armored?” “Advanced Robust Metallic Operable Reusable thermal protection system,” Lyta explained. “It’s a more durable heat shield than what they use on the shuttle. One good foam strike on the underside tiles, and the Shuttle wouldn’t survive reentry. They’ve been lucky so far… Anyway, she needs work, but she could fly. Why, do you have some spare aerospikes laying around?” “I just might,” Scott suggested. “Well, uh, okay…” Lyta responded. She did not expect his answer. “You do realize that the payload isn’t great though, right?” “What if I told you that I know how to make karbon komposite tanks that hold up under pressure,” Scott asked. That got her attention. “I would be curious to know how,” Lyta said. Scott grinned and quickly changed the subject. He pointed to the front of the craft. “Can you add a cockpit in that space in the forward tank?” “Uh, we could,” Lyta said, puzzled, “but why? The Mk-33 was designed to be fully automated- no crew needed. We didn’t feel the need to have crew and cargo on the same flight. Instead, we designed a passenger module. Just swap out one of the payload bay modules and put the passenger module in its place.” “Oh, I still want the automated capability,” he admitted, “Being optionally kermanned is great for missions where a crew isn’t needed. But I’m a pilot. I don’t want to be a passenger when I’m aboard, I want to fly the thing.” “I… see...” Lyta answered. She clearly was not going to win that argument. She thought for a moment before broaching the subject. “Are you… interested in… having us finish the Mk-33?” “Indeed, I am,” Scott said as he beamed. He pulled out a list. “And I have some other changes that I’d like to make…”

Yup, Single Stage To Warp. The Mk2 warp engine parts are probably the smallest I'd go for warp tech, but if there's a huge demand for Size 1 warp tech I might consider it. Meanwhile, last bit for today: I'm still working on the warp core, but this is how it'll sync up with the Mk2 Warp Ring. It will also dock to the Mk2 Gravimetric Displacement Generator.

Working on the Mk2 "Starflight" Warp Core:

Moved to Add-on Discussions

Last bit for tonight: This is the Mk2 Gravimetric Displacement Generator. There's some heritage from the Flapjack combined with some alien tech and a modern miniaturized fusion reactor.

Thanks! Simple but versatile is what I'm aiming for. Probably the hardest thing would be mining asteroids for the Graviolium that you need, but you can enable the resource cheat on the part action window and add the stuff during design time. Also, once I get the Mk2 parts done, I'll be working on the jump gates and jump engines, so you'll have three different FTL methods. Speaking of Mk2, here is the Mk2 Warp Coil:

Way to go Restock team! This looks fabulous!

Indeed... Thanks! Yeah I noticed that and fixed it.

Last Bonus Chapter! Chapter 2 Pad A- the historic launchpad that sent the first spacecraft into space, the Mϋn, and a host of other important missions, was about to send off another historic first. In this case, a new space company, Phoenix Aerospace, was about to launch their first rocket. They were just minutes away from launch. When KSP created the KOTS program, CEO Phil Kerman resigned from his previous company and immediately gathered several investors to form Phoenix Aerospace. The company then quickly licensed KSP’s retired Edna launch vehicle, famous for launching the K-20 KerbalSoar and for escaping retirement many times- and their K-24 Kerbal Return Vehicle design that served as Starlab’s lifeboat. They also bought all the production tooling for the two craft before anybody else could. So, while other companies could license the same technology, it would take them years to build the production tooling that they would need to make new vehicles, and that gave Phoenix Aerospace a big advantage. Not content with expending the Edna on each launch, Phoenix Aerospace made several changes, First, they standardized the first stage and boosters to become the Common Core Booster. While the Edna 1E used an RE-M3 “Mainsail” motor in each booster and an RE-I5 “Skpper” motor in the core stage, all three CCB stages used the Mainsail. Next, they gave the side boosters a set of grid fins and landing legs just like the ones on the vonKerman’s Fleigenross. The central CCB lacked grid fins and landing legs since it would be too high and going too fast for a safe recovery. Instead, a set of guidance fins took the place of the landing legs. The company planned to convert used side boosters into an expendable core stage, but for this flight all three cores were brand new. Finally, they left the upper stage largely unchanged, but it did have a new set of small solar panels and a probe core to control its deorbit. With all the changes, Phoenix Aerospace appropriately dubbed their rocket the Edna 1F. For its inaugural “resurrection” flight, the Edna 1F carried a new Sentinel satellite that was designed to hunt for asteroids that could potentially threaten Kerbin. Like the rocket it flew on, the Sentinel was rescued from the scrap heap after funding ran out. “Service arm retracted,” Phoenix Aerospace’s mission announcer proclaimed. Sighs could be heard in PA’s Mission Control. The Edna Launch Tower hadn’t been used since the Skybase 3 mission over a decade ago. “Seven, six, five, main engines start, two, one, liftoff! Liftoff of the first Edna 1F, rising from the ashes of retirement and carrying the Sentinel satellite on a mission to search for near Kerbin asteroids!” As many Edna rockets had done before, the new 1F rotated to the desired launch azimuth and pitched over. At 25 km, the side boosters detached. This time though, as the vehicle continued to climb, the stage recovery team took over and soft-landed them on awaiting barges. The barges they built and the recovery technology they licensed from the vonKermans were expensive, but if they kept recovering boosters, they would pay for themselves in a few flights. The central core and upper stage were another story. They both worked as expected, but they had no chance of recovery. And rather than attain orbit, Sentinel ignited its kick stage and continued to escape Kerbin’s gravity. The probe left Kerbin’s SOI 12 days later...

First Bonus Chapter! Chapter 1 “Tell me about this ‘Shuttle-C’ of yours,” Gene said, looking at the vehicle poised on its launchpad. It used much of the same hardware as the Shuttle Launch System, but a squat cylindrical vehicle took the place of the Orbiter, and the nose of the external tank was replaced by an enormous payload fairing. The twin solid rocket boosters also looked taller. “Shuttle-C is part of our SLS Block 2 system,” Drax Kerman, head of Drax Aerospace began. “If you recall, when you awarded us one of your KOTS contracts, you expressed a desire to launch payloads larger and heavier than your first-generation orbiters could. We have addressed that. Shuttle-C is a cargo-only launcher that can deliver 34 tonnes into Low-Kerbin Orbit- twice that of our new Block 2 Mϋnraker-class orbiter, after accounting for the extra propellants in the orbiter’s ‘wet wing’ tanks. “Shuttle-C uses the same 5-segment solid rocket motors that Mϋnraker does, and a nearly identical super lightweight external tank, which simplifies our manufacturing and operations processes…” “That payload fairing looks as wide as the tank,” Gene interrupted. “Indeed,” Drax hid his annoyance and continued. “Shuttle-C is a semi-inline design that offers a substantially larger payload volume than the Block 2 Orbiter. We moved the payload to the top of the stack for better performance. It can accommodate payloads up to 10 meters long and 4.8 meters in diameter.” “Hm. We have something in mind that’s wider than the tank,” Gene thought aloud. “We anticipated as much,” Drax said calmly. “The fairing can be replaced with a wider design, albeit one not as long.” “I’m sure we can work with your designers to fit our needs,” Gene responded. “You said that Shuttle-C is a semi-inline design?” “Indeed,” Drax replied. “In order to maximize the use of existing launch infrastructure and minimize development costs, we kept the engine placement comparable to the Block 2 Orbiter. Hence the side-mounted propulsion module…” “Uh, ‘propulsion module?’” “In- Yes, Gene. The side-mounted vehicle that replaces the Orbiter is the propulsion module,” Drax said. “It is functionally equivalent to the aft section of an Orbiter. In fact, the thrust structure and engines separate from the launch vehicle after the deorbit burn and parachutes to a soft landing. We will refurbish the module, much like how we refurbish the Orbiter for another flight. We intend to land it back at Kerbal Space Center to simplify our operations. Our only expenditures become the external tank, boosters, and payload fairing, which accounts for about half the cost of the vehicle. That may seem low compared to Shuttle, but it is significantly better than expendable vehicles in its payload class.” “Impressive,” Gene admitted. “Will flying Shuttle-C disrupt Mϋnraker flights?” “Not at all,” Drax answered. “with four high bays, we can process Mϋnraker 1- formerly your unfinished OV-205 orbiter that we purchased- along with up to 3 Shuttle-C vehicles simultaneously depending upon your needs.” “Excellent’” Gene smiled and replied. “We will need that increased capacity… Well, shall we head to Launch Control and watch it fly?” “Indeed,” Drax said and smiled slightly. After Gene, Drax, and the ground crew cleared the launchpad, CSLS-1- the first Commercial Shuttle Launch System flight- lit its three KS-25B “Rainbird” motors a few seconds before igniting its twin 5-segment solid rocket boosters. Once the boosters ignited, a fraction of a second later, the vehicle was cut free of the bonds holding it to the mobile launch platform. It immediately roared into the sky atop pillars of fire, cleared the tower, and rolled into its equatorial launch trajectory. A couple of minutes later, the solid rocket boosters expended their propellant and were discarded, leaving the rest of the stack to continue its climb. A second after exiting the atmosphere, Shuttle-C jettisoned its cavernous payload fairing. Unfortunately, the propulsion module’s aero cone failed to automatically jettison as well, forcing Mission Control to manually trigger the jettison sequence. Engineers made a note for future launches. Since it was a test launch, the vehicle only carried a mass simulator in the form of a pair of large ore tanks. But Shuttle-C successfully climbed into a 214.3 km by 223.7 km orbit. A day of system checks and evaluations later, Shuttle-C ignited its Viking Orbital Maneuvering System engines once more and performed its de-orbit burn. The vehicle then spun around prograde and discarded its modified external tank and mass simulator payload. A short correction burn later, the propulsion module slammed into the atmosphere, trading speed for heat and drag. When it hit the thicker parts of the atmosphere, the module ran out of electric charge- its fuel cell had failed after the deorbit burn- and it began to sideslip as aero-forces gripped it. Despite the difficulties, the propulsion module’s chutes deployed successfully, and the reusable module landed safely- albeit 54 km short of KSC…

Prologue “To the Mun” had been the mantra of the Kerbal Space Program for nearly a decade. It was a way to break the Kerman States out of a wave of wars, recessions, apathy, and a string of bad leaders. The nation rallied around the goal of reaching Kerbin’s natural satellites. When the vonKermans expressed an interest in reaching Kerbin’s mϋns as well, the Kerman States saw it as a challenge, a race to see who could get there first. They “won,” but in so doing they also completely missed the point that the vonKermans were creating a sustainable approach to exploration. Consequently, after the Kermans landed on the Mϋn and Minmus, public interest in the space program faded. KSC tried to renew interest by creating the next-generation Shuttle Launch System to replace their K-20, used it to build the Starlab Kerbin Orbital Station, and then built the Magellan Mϋnar Shuttle. For a time, their efforts recaptured the public’s attention. But going to KOS and occasionally back to the Mϋn failed to sustain the interest that KSP had hoped for. So, with Kongress’ approval, KSP began planning a kermanned mission to the Rusty Planet. But to get there on their limited budget, they had to retire their aging Shuttle Launch System and once again make changes to how they did business. Fortunately, they had a plan. KSP created the Kerbin Orbital Transportation Services (KOTS) program to help private companies develop the capability to deliver crew and cargo to Starlab and, hopefully, beyond. To help jumpstart the commercial space industry, KSC would provide technical consultation, lease its facilities at cost, and purchase crew and cargo flights to orbit. By seceding low Kerbin orbit and cisminmar space to commercial companies, they would free up Funds to focus on Project Duna. That is where Scott E. Kerman came in… “So,” Scott continued, “After being promoted to Major and meeting my minimum three-year time in grade, I resigned my commission in the Air Force. I wasn’t happy just being a test pilot, and since KSP rejected my astronaut application, the career path that I had had for myself was at a dead end. Then a week after I got out, I bought a lottery ticket on a whim- and won the largest jackpot in history.” Sara Kerman looked him over and examined the row of delta-winged Shuttle orbiters. Freedom, the first of the fleet to fly- and the last to fly- retired a year ago. She understood why Scott asked to have their meeting in the Boneyard. “That lottery ticket is your second chance,” she said. “I take it that you want my help to start a space company?” Scott nodded. “Not just start it,” he answered, “but run it. They taught us how to be leaders and handle pressure, but running a successful corporation is beyond my skills...“ “Actually, a lot of your skills are in demand in the corporate world,” Sara interrupted. “It’s just a matter of finding and emphasizing the core competencies instead of a particular weapons system. You might need some mentoring to translate your skills over, but I’m sure you’d do fine.” “You sound like you’ve made the transition yourself,” Scott suggested. Sara shook her head. “No, but I’ve worked with service people who have.” “I see,” Scott responded. “I’ll keep that in mind. But for now, if I provide the strategic vision, and uh, handle the public interface, would you be willing to handle the daily operations?” Sara could see that the younger Kerman had a lot of drive- and the funds- to pursue his dreams. “I’d want to have a lot of autonomy,” she said. “To be honest, I just want to provide the overall direction of the company, and not get bogged down with the details,” Scott admitted. “If you were the uh,” he glanced at his notes, “president and chief operating officer, would that give you the autonomy you want?” Sara smiled. “There’s more to it than just a title, but if you let me set up and run the company the way I think it should be run- as long as I stick to the corporate vision- then I think we can work something out to our mutual benefit. Deal?” “I’m still majority shareholder,” Scott prompted. “Of course.” Scott nodded and smiled. “Then it’s a deal,” he practically yelled. “So, do you have a name for this venture of yours,” Sara asked. “Yes! I’ve given it a lot of thought: Orbital Dynamics. It’s derived from orbital mechanics- the art of applying ballistics calculations to determine trajectory- and the ability to be agile and maneuver quickly.” “Orbital Dynamics,” Sara repeated, “I like it...” She looked around again. “So, where do we get a shuttle of our own?” Scott grinned. “That’s part of my strategic vision…”

A continuation of JNSQ: To The Mun and JNSQ: Shuttle Launch System, this mission report is a continuation of my existing JNSQ career game. Chapters Prologue Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6 Chapter 7 Chapter8 Chapter 9 Chapter 10 Chapter 11 Chapter 12 Chapter 13 Chapter 14 Chapter 15 Chapter 16 Chapter 17 Chapter 18 Chapter 19 Chapter 20 Chapter 21 Chapter 22 Chapter 23 Chapter 24 Chapter 25 Chapter 26 Chapter 27 Chapter 28 Chapter 29 Chapter 30 Chapter 31 Chapter 32 Chapter 33 Chapter 34 Chapter 35 Chapter 36 Chapter 37 Chapter 38 Chapter 39 Chapter 40 Epilogue --- Mod list A mapping of months Listed below are the names of the 12 months in my save, mapped to the Gregorian calendar months: Acama January Huitzil February Chimal March Itzcoatl April Moctez May Axaya June Jool July Tizoc August Ahuit September Cuitla October Cuahoc November Montezu December

Though busy with Blueshift, I'm actually working on the first few chapters of my next JNSQ mission report.

Hm... In the current tech tree, warp tech costs 10,000 Science to unlock, which aligns with @Nertea Community Tech Tree (Blueshift uses CTT's Unified Field Theory node if CTT is installed, or Advanced Alien Technology node if Kerbal Flying Saucers is installed). The current plan is to include all warp tech parts in the same node, while all jump tech parts need a separate 10k node called Jump Technologies. I figure that 10k Science is a lot to spend to get FTL, and it'll get worse when you use parts from both nodes in order to create large jump-capable ships. Given the science cost, I'm not sure how I feel about moving the non-ring coils to another node, but I can see making them...50% more expensive to get equivalent functionality. So 10 S-2 Warp Coils are equivalent to the S-3 Warp Engine's ring, but those 10 coils plus the S-3 Warp Core end up costing you 50% more than the single-part Warp Engine. The Jedi starfighter hyperdrive ring was indeed my inspiration for the Mk2 Warp Ring. A "hovering" part is possible, but I don't see how practical it is- what keeps it in place? That said, maybe the ring from the Warp Sustainer could be available a separate part and has a slim central core for attachments. TBH I don't use either Textures Unlimited or Tweakscale. Further, over the years I've found that various people request support for mods that I don't use, then they move on and I'm left trying to figure out how to support future releases of said mods. Hence, I won't be including mod support except for Community Tech Tree and Waterfall. But if you'd like to create a set of configs for TU and Tweakscale, and would like a shout out on the OP, then I'll be happy to do that.