TheUndeadFish

Hey everyone, Sorry about disappearing for a while. I hit a lack of interest in KSP combined with some other distractions. Coming back, I see that .22 will have a SubAssembly Loader equivalent built in. So I expect this mod to become completely obsolete. In that case, I don't plan to do any further updates to it. (Although I will at least write up some instructions on how to migrate subassembly files to wherever they need to end up in .22) However, if the official .22 subassembly feature ends up being lacking in some important or useful aspects, then I might look into revising this mod into some kind of extension of the built in functionality (if possible). So at this point I'm in "wait and see" mode until .22 comes out.

I chose that because it was easiest way for my mod to take over from the old SAL but still allow people to access any previously saved subassemblies. I didn't really want to be asking people to have to manually shuffle folders around any more than absolutely necessary. However with KSP 0.21, they're allowing mods to use proper file/directory handling features. So I'll be able to make this mod do all the file and folder management itself, which is what I've been wanting to do all along. Once I have time to work out all the programming for that, I'll be able to have it fairly seamlessly start using a new location. I've been debating either putting the new location somewhere under GameData/SubassemblyManager or under the current save-game's folder (thus making it a lot easier to backup all craft files and subassemblies at the same time). Or maybe I could provide both...

I've just updated my own game and it appears to be working normally. So far I haven't seen any new problems like that. Are you trying to load and attach a subassembly that is fundamentally unattachable (and wouldn't have worked in KSP 0.20 either)? If not, then I'll need a bit more detail as to what you're doing saving and loading parts to end up with your problem.

It's not all under GameData, although that part would at least be enough to get the mod to load and show the button. The folder/file structure is: Kerbal Space Program GameData SubassemblyManager SubassemblyManager.dll file PluginData subassemblyLoader subassemblies Landers Lifters Probes As of my latest version (v0.1.3) it now shows a disabled button (really just a dark rectangle) when there's no root part. But yes, placing a root part is a requirement for it to show a usable button. I don't have OS X so I can't test anything with that specifically. And I haven't heard anything from anyone on OS X previously, whether saying it's working or not... From what you're saying, it seems you didn't find a line starting with "AddonLoader: Instantiating addon component 'SubassemblyManager". If that's missing, then I assume it's not fully loading my mod for some reason (assuming all the same information is written to that log on OS X). So I don't have much to go on as to why it's not working. Perhaps you could try this: start the game, enter the VAB, exit out of the game, and then send me the resulting output_log file. I'm hoping there's something somewhere in there that might tell me what's going on. On a separate thought: Do you happen to be using the Part & Groups Filter mod? I've had a couple reports saying that mod causes mine to "not work", but I haven't gotten around to investigating that properly yet.

So VAB to SPH to VAB... interesting. I've taken something from the SPH to VAB, but not a full round trip like that. I'll try some experiments and see if I can get anything weird to happen.

New version released. 0.1.3 Added the ability to save over an existing subassembly without having to re-type the name. Added a warning message if the user tries to save a subassembly that probably won't be attachable (no available attachment nodes on root part). No longer allows trying to save a subassembly without a name. The save/load button appears in an inactive mode when it's not clickable, instead of being completely invisible.

I would love to enhance this. But currently KSP exposes exceedingly minimal file/directory facilities and doesn't allow me to bring in what I would need from the .NET framework. So that rather cripples my ability to do what I would want. On my to-do list. But many craft probably won't have a free attachment node on their root part and thus wouldn't be attachable as subassemblies. So it's a question of whether I can solve that problem first, or just put craft loading in before that regardless. I've taken a stab at a way to do this today... But even after flipping the necessary child-parent relationships, it's not working properly. Crawling around the minimally documented depths of KSP has not led me to a solution yet... I'm going to be working on that for my next update. Possibly tomorrow. Currently the main advantages are: - I'm allowed to distribute this one since I wrote it from scratch, whereas the old one didn't have a proper license and thus distributing any modifications to it violated the implicit copyright/intellectual-property/whatever of the original author. - I'm still here and working on it, whereas the author of the original has disappeared. - I've licensed mine so that others can continue it if I ever disappear.

You don't need the old SAL plugin. And this mod doesn't use any of those icon files. However, this does still use "Kerbal Space Program\PluginData\subassemblyLoader\subassemblies" to save and load subassemblies. (I did it that way mainly so that people can easily start using my mod while continuing to access anything they've previously saved with the old SAL.)

Currently, you can only attach a subassembly via the same part that you clicked on to detach it in the first place. This is due to the way KSP views things as a hierarchy of parts. The part you click on to detach it is the root of that subassembly and consequently the only one that can be used to reattach. If you take a whole craft and save it as a subassembly, then the root node (the command pod that you used to click and drag it) will be the root of the subassembly and consequently the only one that can be used to reattach. In that case, if you've covered up all the attachment nodes on that root, then you probably won't have any way to reattach the subassembly to another craft. These are all the same limitations that the old Subassembly Loader had. In fact, the old mod had a check that would prevent you from even trying to save a subassembly if it believed that it would not be reattachable. I haven't put in any kind of check like that, so for better or worse you can currently end up with unattachable subassemblies. I would like to find a way around these limitations eventually. But I suspect it will involve rearranging some of the part hierarchy of the subassembly on the fly, if it's possible. So that is going to take some time and experimentation.

I've just put up version 0.1.2 which should fix both of these issues.

Hmmm, I was unaware of that... Sounds like that's the cause of people's inability to load. I'll get to work on a fix. In the mean time... is there a list of portability issues and stuff like this somewhere? I would rather not be bumping into it by trial and error.

I only have a Windows computer, so that makes it harder for me to ensure it works on Linux. What exactly is going wrong for you? When you try to load one, does it not even show up in the list or does it not load once you've selected it? Could you try checking either the Alt+F2 debug log or KSP_Data/output_log.txt for errors and let me know what you find?

Ah, I think I see what's going on. I bet you're trying to save a subassembly made up of a single part. I'll have a fix for this shortly. In the mean time, multi-part subassemblies should work for you.

Hmmm. If there's a problem happening when you click the save button, then an error should hopefully show up in the Alt+F2 debug log and/or the KSP_Data/output_log.txt file. Could you check and let me know what it says?

Did you end up with those category folders under "Kerbal Space Program\PluginData\subassemblyLoader\subassemblies" or did you put them somewhere else (like under GameData)?