Search the Community
Showing results for tags 'assembly'.
The search index is currently processing. Current results may not be complete.
Found 3 results
-
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. -
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.
-
I've been trying to offset some engines for my first space plane and it seems that after trying to "move" it using the tool, I cannot get anything to work again unless I exit and enter the assembly building again. Also the move itself doesnt work. Once I presset the part I want to move nothing else happens. I cannot offset it at all. Even the other tools like place and rotate wont work once I have attempted to move things. Any ideas? edit: So I tried removing all the mods and reinstalling the game. Still the same... After pressing "Move" nothing works right in the assembly building anymore. I cannot even place new objects. edit2: Starting KSP in 64-bit mode seemed to solve the issue Br Michael
