Nicky89107

Excuse me, but isn't it illegal to force payment on this? It's a mod for the game.

Ahh, Thank you. That clears up a lot.

I also have a bug to report, The interface, when left open, will be invisible if you leave to the space center menu and reload the world.

What I don't understand is how you find what the "Target =" value should be. As far as I could find, there was no kind of way to figure out what the name of the part is. Aha, found where you can find them. The Names are listed inside the part.cfg. You might want to mention that in the Documentation. Edit Edit: Only some of the part.cfg's have the target name. The rest I don't know what you should put. The part name?

Razchek, You might want to include an example button Interface, because the readme is a bit confusing

I made an Iva modifying tutorial for the .20 part tools if anyone cares: http://forum.kerbalspaceprogram.com/showthread.php/35714-Tutoria-Modifying-Exporting-Internals-in-20-Part-Tools?p=449925#post449925

I don't think anyone else has tried to do anything like what you are doing. Nice job advancing the modding community Razchek.

Alright, so I figured out how to export modified Internals and figured I would make it easier for the rest of the community. I am going to assume that you already set the .20 part tools up and a basic understanding of unity. So, Onto the tutorial: Step 1: Import the Internal To import the Internal, you go up to the hot bar, hover over tools, then open the KSP part tools GUI. Inside the GUI, you go to the "Spaces" tab, find the space you want, and click Spawn next to it. This will spawn the internal into the scene. Step 2: Modifying with existing props The part tools handily imports all pre-existing props into the GUI for you. You will want to click on the internal to make sure it is selected, And open up the GUI again. Inside the gui, You will need to go to the "Props" tab. Most of the props are named what you would most likely think. Again, Find the one you want, and click Spawn. It will appear in the scene, Most likely in the center of your Internal. Step 3: Exporting the Internal If you would like to overwrite the previous internal, You can just click on the internals root folder, Go to the inspector Tab, and click "Save to Config"\ This will save the configuration of parts to the internal.cfg If you would like to save it to your own internal config, you will first want to go to the "Dir URL" option, and click Set. This will open up a window in the GameData directory. You will want to navigate into: "YourModsFolder/Spaces/yourSpaceName" and click okay. The part tools can not create an internal completely from scratch, so if you are just modifying an internal, you will want to copy everything from it's folder into your internal folder. If you are modifying an internal, you will need to open up the internal.cfg and rename "name=". When you are done, You will want to go back to unity and set the "Space Name" option to the name in your internal.cfg. For Example: "Internal{ name = mycupolaInternal}" would equal "Space Name = mycupolaInternal" And that's your lot.

well, i guess that solves that. Just have to move the cfg for a while.

So i loaded up the part tools a couple days ago, and they loaded and i played with the new interface, but today after updating unity, I go through tools-Ksp Part tools, Set the gamedata directory, then it throws this error: NullReferenceException: Object reference not set to an instance of an object UrlDir+<get_AllConfigs>d__1b.MoveNext () UrlDir+<GetConfigs>d__2a.MoveNext () System.Collections.Generic.List`1[urlDir+UrlConfig].AddEnumerable (IEnumerable`1 enumerable) (at /Applications/buildAgent/work/84669f285f6a667f/mcs/class/corlib/System.Collections.Generic/List.cs:128) System.Collections.Generic.List`1[urlDir+UrlConfig]..ctor (IEnumerable`1 collection) (at /Applications/buildAgent/work/84669f285f6a667f/mcs/class/corlib/System.Collections.Generic/List.cs:65) KSPPartTools.GameDatabase.GetConfigs (System.String typeName) KSPPartTools.PartToolsWindow.DrawSpaces () KSPPartTools.PartToolsWindow.OnGUI () System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) (at /Applications/buildAgent/work/84669f285f6a667f/mcs/class/corlib/System.Reflection/MonoMethod.cs:222) I have no clue why it wont work. Oh, and it throws the error again everytime i try to close the part tools window edit: Seems that romfarer's cfg is causing it to fail to load the gui. Strange...

Made my own thread about the issue

one quick question, is there a guide to exporting internals or anything . I am such a noob

How did you modify the stock internals to put the laptops in there? Edit: Oooh, New part tools Know what I'm Doing next

@stevefin You have to put the Mod manager inside the primary .exe folder on any game install.

What is the "gunner" module?

Woohoo! been waiting so long! but i know its worth it!

I really like what you did with the firespitter control system. I would love to see it in more places.

Yeah, this is very useful when you have like 50 mods that may or may not work.

That sounds very Useful.

I have a question, how do you tell if you have the latest mumechlib.dll, and my game gets stuck loading Simple prop 1m pushing. Help me please?