MoonstreamInSpace

A few other missing features to add on to this thread: Craft folders: this was one of my favorite feature additions to KSP1, and made it much easier to keep track of huge sprawling save files. (also, if it is implemented, please implement it so that it works with the filesystem like how KSP1 did) Alarm clock: This made not overshooting maneuver nodes that much less easy, and both the softer slowdown at the end compared to just clicking the "warp to node" button and the ability to set the delay before the node made trying to not miss maneuvers 30 years in the future that much easier. Forced Physwarp (alt+timewarp): makes landings a lot easier, as you don't have to stop warping every few seconds to reset orientation and adjust throttle Maneuver node planner (the thing from the room to maneuver update): First and more obviously, it lets people fine-tune your maneuvers much more carefully, making it easy to find that last 0.1 m/s change that brings them to a close encounter, and also text input made it easy to reset an unintentional direction change by setting it back to 0. It also gave the ability to edit the maneuver while it isn't on-screen, which lets people focus on looking at where they are going to go, instead of having to awkwardly adjust the camera so they can see where the maneuver started. Pinnable part menus: The ability to have the guis for multiple parts available so you can fine-tune values such as friction on landing gear, or thrust on multiple VTOL engines, is very useful. Selecting parts in the VAB when setting action groups (left-click on a part, its actions are now highlighted in the AG menu) Action groups for parts being grouped by symmetry: Much easier than setting 8 multimode engine keys seperately Global rotation/translation, especially having parts snap to a "global grid" when moving and rotating. Renaming vessels in-flight Fuel tank locking Fuel tank priority

I really miss the vehicle folders for KSP1. Is there a plan to add them back in for KSP2?

Reported Version: v0.1.2 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 (Through Parallels on Mac 13.4) | CPU: M2 CPU (Not sure how emulation works) | GPU: (Not sure how emulation works) | RAM: 12GB allocated (Using a Windows emulator, I understand this is not officially supported, but I'm curious if this might be useful info) Issue involving a black border between Kerbin and space. My findings on the problem: - It appears at the border between Kerbin's surface and space - It stays anywhere on screen that it had been in the past (leading to a kind of "smearing") - However, if between 2 frames, it moves to another section of the screen, then there is no black in between (likely because it never rendered there?) - Changing the window size (possibly forcing the game to re-render everything?) removes the "smears" leaving only the border itself. - It shows up on the KSC and in flight mode, but not in map view or the Tracking Station. - It is much thicker at alt 0 than at alt 70K - The sun shows through it - The "smears" of the border also remain even after changing the view to the map screen and back. Sorry, I get this isn't the most coherent bug report or that relevant. Note: the game is entirely playable, and runs surprisingly well! I just need to manually reset the "smears" sometimes to keep the screen visible. Included Attachments:

Thank you, Angel-125, for fixing the Pathfinder<->Sandcastle interaction! It works now, and is really useful!

Update: It didn't work. I'll have to do it manually.

I actually had KSP_PartVolume do all the work for me, by mass-replacing all instances ModuleInventoryPart to be unrecognizable, running it, taking the generated MM file, and resetting that to use ModuleStorablePart. We'll see how this spaghetti plays out.

Oh, I don't have KIS, as I always found the lagspikes on build annoying. I'll try and set it up again. Would it be possible to have a patch or something that turns all the variant parts into their own separate parts? It should (I hope) fix the main issue.

Also, randomly, when I print a part, there is a chance the workshop tries to start filling every container it can reach with them. (if it helps, the workshop efficiency was set to 100, so I could build parts fast to test things)

This mod does not work with stock EVA construction. I can't attach modules in a line (due to EVA construction collision detection), and part variants have the attach nodes of the root part (it's a bug even when the parts were placed in the VAB). Is there anything I can do to fix these problems? On that note, is there any mods that make it possible to detach parts that aren't at the very edge for EVA construction and/or place parts that would overlap? EDIT: There seems to be a (temporary) workaround to the construction problem involving offsetting parts around, and I can still build with the basic chassis parts without variants, but if there are fixes to either of these, please let me know. Also, "Mountain Goat" wheels are bugged , they shift backward and up relative to their mounts once placed, but can be fixed with by quicksaving and reloading. It's possible that most of these are caused by mod conflicts, though.

Another issue: When I print a part variant (buffalo chassis long), it prints the part like it should, but the attachment nodes appear to be taken from the base part instead of the variant (it has the buffalo chassis short nodes, but looks like a long chassis). What is going on? EDIT: OK, it appears it's a bigger bug than I thought. Even a part placed in the VAB has the wrong nodes in EVA construction.

Gotcha, thank you for clarifying that! Is there an easy way to get/estimate the volume of a part?

I actually use the Buffalo2 Workshop for printing out things.

Has anyone been able to print components using the Pathfinder inflatable parts?

I noticed that there is a config inside the Buffalo2 files that allows parts with ModuleInventoryPart to effectively also have ModuleCargoPart. How hard would it be to give this to, say, all the Pathfinder and/or stonk parts? Would it be possible to make a variant/modification of KSP_PartVolume that uses the new system instead?

Has anyone else had this problem? Did I forget some sort of dependency?