linuxgurugamer

I've confirmed the issue, and it has nothing to do with your craft, thanks for uploading it. No idea how long to fix yet.

If you could make the craft file available, along with a list of all mods installed, that would be helpful Then look at EVE and RT. KW is only parts, no code.

This helps, thanks

Is anybody doing Tanklock? If not, I'll have a look. Linuxgurugamer

That I got, will look at it. What about the other issue, where in flight it used too much money?

And I assume you are running the 1.1 version of KRASH? I will look at it over the weekend. Can you narrow down any more details?

Glad to help. All I ask is a mention in the OP when you are done. And let me know if there is anything else I can do for you. LGG

I've emailed him to see if he is going to continue this. If not, then I may take it over with his permission.

I just did the pull. I added the following functionality to it: A new window was added to show all the struts & fuel lines Struts/fuel lines are listed as buttons Initially good parts are shown first, there is a button to reverse the order Clicking on a single button will highlight it, and then you can click the button to delete selected part Button at bottom to delete all bad parts at once. Only usable buttons are shown, ie: if no bad struts, then you won't be able to delete all bad struts. This was a quick n dirty job, but I tried to keep the code clean. The UI could definitely use some work, but it does work Hope this helps, looking forward to future updates LGG

I'll do the pull in a few minutes, I just got the ability to delete parts working

Does this happen when only KW is Installed? If other mods installed, first make sure they ate all updated, then post a list of installed mods

What version of ksp?

I had some time, and really wanted to be able to have this delete struts. So I forked it and added a window to list all the struts, and by clicking a button, to select a single strut. The link is here, I'd be very happy to push it back to Kujuman. Even though there is a "Delete" button in the window, it isn't working yet. @kujumanI hope you don't mind. There wasn't a license in the github repo. I haven't yet done a pull request, let me know if you want me to. This repo also includes files used by Xamarin (including the csproj file). If you ask, I will take it down. LGG My addition will do that.

Please post in the following forum to get this listed in the available mods: Please add, it would be extremely helpful. Possibly a "Delete All Bad Struts" button, and a button on each line to delete an individual strut (good or bad) Another thing to consider, may be a bit harder: In flight, show unconnected (bad?) struts, and add ability to delete them in flight to help save on partcount. Love the mod, please keep up the good work. Edit: Just realized that the only display you have is the debug log. So please add a window to show good/bad struts, if possible. Let me know if you'd like help (although I would doubt that, your skills appear to be pretty good)

I know, and have asked Sarbian about it, waiting for a reply

Sarbian, Are you going to add the ability to move the navball left or right, like EnhancedNavball used to do?

Look at this mod: Seems to do what this does, so I probably won't do anything

I may take this over, I'll take a look at the license and code

I've put my recompile of KerbPaint on Github here: https://github.com/linuxgurugamer/kerbpaint There is a prerelease containing the recompiled dll only

There is nothing preventing you from creating your own version of the functionality of the original mod. That comes under "idea", which is not protected. What IS protected by licenses, are the original code, models, and in some (or all???) cases, even the visual appearance. You could certainly come up with your own models and visuals; for example, a rocket is (usually) long and relatively thin. That idea cannot be copyrighted, protected, etc. However, the model of a particular rocket (the .mu file, dds, png, etc) is and you wouldn't be able to copy it. Now, you could create a model of a new rocket which would have the same general height, width, dimensions, etc of the original. So far, so good. You can even create your own graphics. But if those graphics are too similar to the original, you might have a problem. Again, regarding the graphics, it will depend on many factors, starting with the license (does the license forbid any recreations?), how similar, etc. I recall that the percentage of similarity has to be something less than 90% (don't hold me to that) in order to be allowable without any problems, but then you get into the realm of how to measure the similarity, etc Method is ok, as long as you don't copy code and it isn't patented. Regarding the ethics, I'm not sure that a modder not wanting their work to be duplicated is a valid concern. You can't protect ideas, and that is what you are implying the original modder wants to protect. I would be sure to have a very different name to avoid confusion between the different mods. I actually ran into this situation a year ago, and asked for advice from the forum moderators. The license was vague in one respect, and I didn't want to do the wrong thing. It was resolved by several long discussions and I was able to release my update to it while keeping in the spirit and text of the original license

But not necessarily MY community. Other than KSP, you and I have nothing in common, so no custom of yours would have any bearing on me.

What are you smoking? I don't mean to be insulting, but let's take a look at my most recent mod, KRASH. First off, KRASH was developed from HoloDeck, with the author's permission. While it wasn't necessary, I asked for permission first, and he requested that I change the name, ergo, KRASH. Now, I spent a lot of time debugging it. Probably more than I should have (estimate of >40 hours), but I wanted to release a quality mod and had a very obscure bug to trace down. Apparently I did, people seem to like it. Now, let's say that KSP is insanely successful, and also say that KRASH is very popular. Very good for Squad, and Squad will continue to support it because they are earning money from it, so it pays for them to support it. But what about me? You are saying that I have promised to support it forever, or at least a very long time. It takes time to support. Are you willing to pay me for my time? If so, I'd be happy to support you (be careful, my time is very expensive). But if you are not going to pay me, then why should I support it 5, 10, 15 years from now when people are trying to run KSP on Windows 15 and there is a problem with KRASH. For that matter, am I supposed to support it from beyond the grave? Because, I'm not a youngster anymore, and while my family is fairly long-lived, I just had an encounter with cancer, and there is always the chance that I won't be around. So the license will allow someone else to continue it. There is no promise to do anything. There is only the support for as long as I care to give it. If I stop, then my reputation suffers (maybe). Personally, I will support it for as long as I have interest in the game, and then some. But one day, I'll move on, and at that time I really won't care about any implied promise made years earlier for something I did for free. I care a lot about licenses, to the point that there was a part mod I wanted to update, but the license didn't allow any changes, so I contacted the site administrators to see if a proposed action I wanted to do was allowed. It actually started a big discussion amongst all the moderators, and their decision was initially against me, but after consideration, they approved my action.

Based on what you described, it really did have 18 parts there.

Again, a fisheye lens will do that. The rocket was very close to the lens, the little mast was further away. fisheye lenses will do that sort of distortion.

Oh. sorry about that, wasn't thinking. I was having some problems with the struts and that solved it, but didn't think about the part issue.. But you put it on the wrong docking port. I avoided the asteroid because it was too wobbly. thanks for fixing it, I would have been willing to redo the mission if needed.