Lyraea

That drive virtualization trick I mentioned before is working great for me. I'm using Ubuntu's VMM tool to run a Windows 10 guest machine, with drive virtualization onto my SSD with Kerbal on it using the VirtIO Win10 Guest Drivers. Would be interested in talking to other people who've worked on this earlier like @737 and @Urbs to see if we can work out a simpler way to make it happen if we put our heads together. I couldn't find the python script Urbs and 737 were talking about in version 0.9.9 (is it GenerateSystem.py in the master?), so I had to make it work with the .exe, which happens to make WINE very unhappy: wine: Unimplemented function api-ms-win-crt-runtime-l1-1-0.dll.fetestexcept called at address 000000007B011E0E (thread 00f4) I assume the structure of this mod has changed significantly since the update you were working with? I see that the latest release on Github and the master have very different structures and file sizes.

Success! I've gotten it to open in a VM. If nothing else, there's at least one way to run it under Linux... I might even be able to get it to install onto my Linux system from inside the VM with drive virtualization, but I'd like to do this with as few "moving parts" as I can.

Hmm... That's worrying. I can't even get it to boot as expected in a Windows VM. I'll redownload and be sure I'm using a version that works before I try to get it to open on Linux.

I'm on Linux Mint 21.3 Cinnamon, Linux kernel version 6.8.0-40-generic. I'd love to get this mod working, and it seems possible, considering it's mostly a Python script and ImageMagick is already available on Linux. I'll give my best try getting it to run on my machine and post a step-by-step guide here if I can get it to work. @Sushut, I'd be happy to test any Linux compatibility attempts you might want to implement, and provided I can figure it out myself, I'd even be willing to write Linux instructions for your GitHub readme or the like to help other Linux users. Hopefully the smart people of this topic can put our heads together on this and get it running smoothly without too much effort on your end! Unfortunately, GenerateSystem.exe isn't running under WINE out of the box. I'll have to get creative... Gonna look at what else was said about Linux in this thread before I got here, in case someone else has already worked this part out.

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: AMD Ryzen 9 5900X 12 Core | GPU: AMD Radeon RX 6700 XT 12GB | RAM: 80GB In the debrief for the Going Green mission, there is a typo: Where Keri Kerman is meant to say: The line is written as: Included Attachments:

Installed, visited, and followed. Fantastic work! Can't wait to come back to Nem on future missions.

First?! Goodness, I might be late to the game, but this is an awfully impressive first pack! New must-have added to my saves.

I've encountered a recurring error between CryoTanks+NFSuite(+B9PS) in several installs including the Near Future suite, and not finding any exact reports of my error, figured I'd come here for help in case any of you have encountered it before or @Nertea is familiar with a fix. This might be better suited for one of the threads of the NF suite, but having encountered this with multiple Near Future mods, I'm leaving it here. Modlist and error attached. Can provide more information if requested. By my limited understanding from logs, the error goes something like this: Near Future parts have a CryoTanks config in B9PS, requiring cryo tank types. Specifically in my case, the LH2OCryo tank type. B9PS cannot find cryogenic tank types, despite CryoFuels being installed. (Exact error text below from the first time it appears in my logs.) B9PS throws a fatal error, forcing KSP to close. Here it is: I figure it's probably a conflict that isn't immediately apparent to me (as my modlist is a hefty one,) so here's my list and GameData contents in full as stated directly in the logs:

Night launch of the satellite, unfortunately. However, here's a photo during the circularization burn!

It took a while to refine the design (and real life got in the way,) but I've finally been able to design a working prototype for the JB-3! More in-depth post coming soon.

Ah! The VAB is done upgrading to level 4, and it looks... different. The engineers tell me they ran out of space on which to paint racing stripes, so they built it bigger to fit more racing stripes on. This seems to have worked, since the engineers have stopped complaining about the "cramped working conditions" and "almost getting hit by work trucks and rolling rocket parts all the time." Now it's only some of the time! A significant improvement, I say. Maybe we should look into this "actually build a bigger building" business, and implement it elsewhere.

I've designed the JB-3, but there's one problem: it's too complicated to fit under the 30-part limit! I'll be having to upgrade the VAB yet again to Level 4 to be able to build it, and that means I won't be able to launch rockets for a while until then. Oh, well... This is a great time to meet our trusty Kerbonauts!... ...what? Who are you? I have a feeling something's very wrong here, but I can't put my finger on it. Ah, well, no need to dwell on it. These are some of the greatest pilots and most belligerent coworkers known to Kerbalkind! It just won't do to just stand here gawking at them, they deserve a proper introduction! Everybody knows Jebediah Kerm- ahem, von Kerman. The son of a genius scientist who kindly provided the initial Funds for me to start this space program, Jebby is also an ace pilot and a bit of a national hero for his exceptional achievements in Komplete Konflict II about... 7 years ago?! My, how time flies. That can't be said about these two, however. Bill Kerbrown is the engineer that had the gall to try and tell me he'd need a month to build Jumping Bean (poor, sweet Jumping Bean...) and didn't even get it to fly into space when he was done. Meanwhile, Bob King is a scientist that did I don't know what exactly, but I put him in the program for symmetry. Finally, there's Valentina Kilroy. A rising star in aviation, her recent achievements as an ace pilot have granted her the spotlight, and are even threatening to eclipse Jebby's own. They've got a bit of a friendly rivalry going, trying to see who can break more records. Kilroy would like me to make a correction, her records have, in fact, eclipsed Jebby's own. Jebby objects.

JB-2B launched with flying colors, bringing back a yield of about 30 science and collecting the first science above the Karman line (100 kilometers instead of 70, thanks to the atmosphere rescale.) It had an apokee of about 133 km, but I wasn't able to capture any screenshots during this record-breaking spaceflight due to a communications antenna error (which I had to frantically troubleshoot in that 1m 30s time period, so I was able to transmit my science back before the probe was destroyed on reentry!) To my surprise, though, the ever-faithful JB-2B naturally oriented itself engine down during reentry and survived the heating basically untouched, only to be destroyed on splashdown. This means I may be able to use the second stage "Pug" engine from the JB-2B as a makeshift heat shield on later versions of the JB-series. Here's to the JB-3, a future attempt at orbit! We also used the science from this flight to unlock these tech nodes:

After rolling out another JB-2 to the Launchpad to run tests and verify that the bug was fixed (and then rolling it back and promptly scrapping it,) we built and rolled out the JB-2B - now with aerodynamic fins. This was totally because of a normal step in the development process to ensure the utmost confidence in the second launch, and not because I realized I needed fins right before launching the second JB-2. Just trust me on this one, I swear. Okay, I also forgot reaction wheels. I'm not even going to pretend on this one, I considered adding them and deliberately decided against it. Turns out they're the only way such a long burning SRB stage can stay oriented...

Despite the software bug, we had 5 good lights on the JB-2 first stage. Maybe this mission won't go so poorly, after all... NEVER MIND Well, JB-2's Karman line attempt is a write-off. We'll try with the liquid second stage, but we can't guarantee anything impressive (or much of anything at all) due to its abysmal low altitude thrust. Time for us to build an identical third mission, hopefully without the software bugs this time... Not aerodynamically stable, and it flipped and crashed into the ground. Nothing left but shrapnel around the space center and a probe core rolling across the ground... Truly a tragedy for the ages.