[0.20.x] Subassembly Manager

[Carlonord]

Reread the documentation very carefully, there is a folder that MUST go in the Plugins Data folder.

I installed it correctly, I watched what happened to see if I missed anything. For some reason the categories deleted themselves so all that was needed was a quick click-and-drag.

[phrenq]

Well it definitely was a long path, but getting it out from under the Users directory is a good start, as everything under there is protected anyway. Now that you've gotten it out from there, are you sure the folder isn't set to read-only, or that the game/mod isn't being prevented from writing files to it somehow?

Yeah, I made all the directories world writable, although that shouldn't be an issue since the KSP process runs as my user.

I wonder, has anyone else ever successfully used Subassembly Manager on OSX, and on OSX with Steam?

[jrandom]

I'm running OS X, Steam, Subassembly Manager, and SelectRoot with no problems. I did nothing other than simply install the mods. No directly permissions or any other alterations.

[phrenq]

Thanks guys -- I figured it out. While poking around in the plugin source code, I noticed it references the PluginData directory relative to the "saves/<game>/Ships/VAB" directory (i.e., "../../../../PluginData/subassemblyLoader/subassemblies/"). My saves directory is actually a symbolic link to a directory in Google Drive, which I use to sync saves across computers, and this was tripping it up.

Even though the error message said it was failing to save the file in the "/Steam/SteamApps/common/KSP/PluginData" directory, it was really trying to save in a PluginData directory that was a sibling of the symbolic link target, in my Google Drive directory. So I made PluginData another symlink in the same location, and problem solved! Appreciate the help.

[shand]

I installed it correctly, I watched what happened to see if I missed anything. For some reason the categories deleted themselves so all that was needed was a quick click-and-drag.

same thing here, click and drag and its fixed.

[Ali_J_101]

Awesome mod! Saves so much effort in launching stuff. Thanks!

[DerekL1963]

Nice work! (Still eats fuel lines though.)

[Fox62]

Nice work! (Still eats fuel lines though.)

The trick is that sub assemblies are the same as .20.x craft files. So if you have a .craft file that has the decouplers the root part, you can use that for the subassembly I think.

[Ricardo.b]

very useful mod, is possible to create new categories? ships, satellites and misc would be nice

[Deadweasel]

very useful mod, is possible to create new categories? ships, satellites and misc would be nice

All you have to do is create the directories; the plugin will roll from there

Go to %KSP_ROOT%\PluginData\subassemblyLoader\subassemblies

Folders you create in there will become available as "categories", using the folder names.

[DocLangy]

So this is added correctly. The plugin folder has subassemblyLoader/subassemblies/ then lander lifer and probe folders, when I try and save I can get it to say "save part" but there are no categories to save it to. Any advice?

[HeadHunter67]

You didn't install it correctly after all. That part of the mod doesn't go in the Plugins folder, it goes in the PluginData folder.

[Sharkey]

Really hate to bump a dead thread here, but I was wondering if this mod was compatible with 0.21 or if there is another mod that is.

[jrandom]

Really hate to bump a dead thread here, but I was wondering if this mod was compatible with 0.21 or if there is another mod that is.

I've been using it with .21 and it seems fine. Same with SelectRoot.

[AncientGammoner]

Subassemblies are coming to stock in 0.22 as well.

[Henno]

Below is the mess I have made of my KSP folder. I have somehow managed to get mechjeb going but can't remember how.

My problem seems to be what to click on after I have cut and paste the .rar files from my /downloads folder into this folder. I have 3 options that are .rar related; Extract files..., Extract Here, Extract to uploads-2013-07-SubassemblyManager

The instructions on spaceport say to 'Extract the GameData and PluginData folders into the main folder....' Can I copy and paste the GameData folder I can see in what I have extracted here under my 'sounds' folder or the GameData/SubassemblyManager folder into my GameData folder?

I don't know how to extract some files to some folders and some folders to others if that's what the above instructions mean. AAAAaaargh, it's doing my head in!

[Henno]

This on startup

This when I try and load anything even a stock craft.

[GhostChaser]

Sent ya a PM Henno so we don't bog down this thread.

[Apollo13]

KSP vers. 0.22 includes a built-in subassembly manager, making this mod redundant. I assume it will no longer be maintained as players transition their subassemblies to the built-in manager.

[Absolute Human]

Is TheUndeadFish still here?

Could you please do a favour- compile a version that saves subassemblies in the mod directory, rather than in the old Subassembly Loader directory?

Yes, I am warned that this feature is becoming stock, but before it is actually here (and whatever at all).

It just would be nice to see the mod fully completed and perfect for use in the current version, hence the problems of updating various mods for the new version, if some become brocken.

[Gaius]

Could you please do a favour- compile a version that saves subassemblies in the mod directory, rather than in the old Subassembly Loader directory?

Yes, I am warned that this feature is becoming stock, but before it is actually here (and whatever at all).

It just would be nice to see the mod fully completed and perfect for use in the current version, hence the problems of updating various mods for the new version, if some become brocken.

It's fully completed and perfect for use in the current version. Squad relaxed the requirements for where mods can read/write data a version or two ago, so the problems you're talking about are nonexistent. The current scheme for where subassemblies are stored will probably continue to work even after the game is out of beta -- not that it will matter, since this is becoming a stock feature on the next beta release, so there simply isn't a question of potential future bugs. If a bug doesn't already exist in this mod, it effectively never will. We're already playing the very last version of KSP this mod will be used with.

[Absolute Human]

It's fully completed and perfect for use in the current version. Squad relaxed the requirements for where mods can read/write data a version or two ago, so the problems you're talking about are nonexistent. The current scheme for where subassemblies are stored will probably continue to work even after the game is out of beta -- not that it will matter, since this is becoming a stock feature on the next beta release, so there simply isn't a question of potential future bugs. If a bug doesn't already exist in this mod, it effectively never will. We're already playing the very last version of KSP this mod will be used with.

It is not really a "problem". Just a matter of changing the path in one or two lines of the code and compiling a new ".dll".

For the sake of simple convinience knowing that all mod files are stored in "gamedata"...

[blazing angel]

not working on macs you have no categories unless there is a way to trouble shoot this

[Technothederp]

So can this work with 0.21?

[Kerbal01]

Yes,it does.