Search the Community

I found an interview with Nate Simpson explaining how this works. https://youtu.be/d6db1-dILgM?si=Q_GthA6T536iIJ5h The "workspace file name" is the name of the file on your computer. The "vehicle name" is the name of your rocket in game. Original post --- Each workspace has a name. Each vehicle has a name. A workspace can only contain one vehicle. When you load a file it gives you the workspace name. When you save a file it gives you the vehicle name to overwrite. When you merge files, you merge workspaces. My first impression was, a workspace allows you to build variations of a vehicle. Like a rocket family. However you can only have one vehicle in a workspace. Is the intent that you're suppose to merge payload workspaces into a vehicles workspace and then combine them? Why then can you swap assembly anchor? It feels like "assembly anchor" should be called "vehicle", and you should be able give each one a unique name. A workspace now contains multiple vehicles. You then merge other vehicles from other workspaces into your active workspace to add to the list of vehicles. For example. "Apollo workspace" (contains vehicles) Saturn V Command/service module LEM Apollo–Soyuz Merge skylab from "space station workspace" into "apollo workspace". But this is not possible. I'm not sure what the intent here is... Does anyone know?

I think we really need this ASAP because backward compatibility will become an issue later. It's a very important change and relatively easy to implement: In the Save / Load windows, replace the term "Vehicle" with "Project" (because some people build entire families / fleets of boosters as assemblies and these are not vehicles) Also, replace the term "Workspace file" with "Project workspace snapshot" In the Load window, replace "Load vehicle" with "Load project" AND put all "Project workspace snapshots" in a drop-down list specific for each Project save. This way we can have Projects be vehicles and then we can merge / import that vehicle Project Workspace Snapshot into another Project which is a fleet of vehicles (but we should be able to name these vehicles individually). Also, as stated above, it would be incredibly useful to be able to label (sub)assemblies and have them be a single group of parts which can be stacked and destacked. More details below: A Project should be a collection of vessels and assemblies (like a folder which holds crafts and (sub)assemblies). We should be able to label vessels and (sub)assemblies (groups of parts) inside the Project. Labeled craft / (sub)assemblies (groups of parts) should also save their own action groups and staging sequences. The assemblies should stay grouped together even if stacked on top of each other, so it's easy to destack them (stage, lander, return pod etc.). Working on parts of an assembly would require selecting that group.

I tried to build a new rocket to go to the Mun northpole this morning. I got big problems. With the ship, it was a lousy build, but mainly with the save ships and save game commands. The saved ships that I had made were first not available ingame. (Which meant that the saves got corrupted and at one point i could not even save the game) That was the first thing that happened. When i looked in workspaces folder they were still there. The last save had the message that the rockets were unavailable. I could not save the Luna1 ship i was working on in the assembly hall. After restarting the game the ships came back and i managed to make a lift off. After going back to the vehicle assebly hall I loooked at the saved ships and they were all there. I decided to erase one of the ships and now I got back to the problem i had earlier. All ships disappered ingame and all saves had the wording that the ships were unavailable. I could not save the ship that I was working on either. I could make new saves but with the message that the vehicle was unavailable. I looked in the workspaces folder and all Luna and Mun ships had disappered. Only my crappy first ship was still there. And i could not save the ship that was in the Vehicle assembly hall. This is how it looked like. Now I am reinstalling the game from scratch. I will write here again later today if the problem remains. For my specs: https://pasteboard.co/8LMZ0j6nm6vE.png I have GTX 3070

1. Craft / (sub)assemblies should be saved globally, individually, stand-alone, separate from workspaces. 2. Workspaces should be collections of craft/ (sub)assembly objects. This way you can edit a craft or assembly and when you save it all changes / improvements cascade in workspaces that contain said object. So you don't have to constantly switch workspaces to find the latest iteration of an object. 3. Also craft should be collections of stand-alone, labeled (sub) assemblies, each containing their own action groups and staging sequences. Any craft should be easy to separate into the (sub) assemblies it's made of. 4. And we should be able to launch / test any sub(assembly) or craft from a workspace very easily, with the click of a button.