Allowing axial symmetry in VAB and vice-versa.

[Fifi]

I think everyone who ever built a non-SSTO space shuttle or launched jet plane to other planet will agree with me, that doing it using stock tools is extremly hard (for example launching aerospike plane to Duna needs building lifter in SPH () or copying it from SPH to VAB (which results in symmetry madness, bugs and reverting to SPH after every "Revert flight"). Or making a multi-part ship for a payload which could be easily launched in one shoot.

I know that somebody will immediatelly jump up saying that some of it can be done with the use of mods, but:

a) It's bugged as I said - neither Subassembly Loader, Subassembly Manager or Editor Tools can't do it as they should because of the way game handles symmetry and projects.

This is basic functionality, it's really odd that clipboard and attaching space shuttles to rockets isn't in vanilla game but have to be such a hard thing, which can't be even done properly using mods.

Also the Ctrl+C and Ctrl+V (also between the projects) would be really nice (and would do subassembly without need for implementing it - which would remove the most must-have suggestion from not to suggest list without really completing it).

I think everyone who ever made a complex rocket will agree with me, that without proper handling of clipboard (which mods fail in, as I said) and symmetry & project compatibility between VAB and SPH it's a really complicated task.

Thanks in advance for taking it into consideration.

[Fifi]

*bump*

Btw. This option should be connected with Rover Symmetry suggestion: http://forum.kerbalspaceprogram.com/showthread.php/44742-Rover-Assembly-Building-Rover-Symmetry

[Ernest3.14]

Ctrl-C and Ctrl-V for anything other than text isn't that simple, it requires a buffer of sorts (which is what Blender does?). But given the nature of .craft files, it shouldn't be too difficult.

[Fifi]

It's already done, the currently detached parts are stored in some buffer. It's only the matter of making second object of this class or second collection (wherever it's stored) and modyfying VAB and SPH a bit, so it could be pasted also as first part (if the base component of selection mets it's criteria). The symmetry (VAB, SPH, rover) also shouldn't be a problem (it's just a bunch of modifications to the existing code) and will remove all bugs caused by workarounds.

Of course it would be better if projects won't be based on a magical "first part" (and center of wobbling), but that's the topic of another suggestion, because it's actually really complicated.