EndlessWaves

Only if you leave the fuel in the interplanetary craft completely untouched. If you launch with full fuel tanks and string a fuel line so the fuel is burned by the ascent stage then you'll end up with a much lighter, smaller craft overall than using empty tanks.

No, just re-export the model with the correct rotation.

This is technically the plugin development thread so config file questions are rather off topic (at least, those not concerning plugins). General or add-on development would be a better place. But to answer the question. ModuleEngines specifies fuel consumption in ISP. This is essentially mass flow per unit of thrust. So as fuel consumption is specified as this the litres of fuel consumed per second depend on the mass of the fuel and the thrust of the engine. Increasing engine thrust does increase fuel consumption, and trying to run on a fuel without any mass (e.g. electricity) doesn't work because the module in question doesn't know how to calculate fuel use for a massless fuel. atmosphereCurve specified the ISP values for the engine at different atmosphere densities (or possibly pressures, the difference isn't big). If you want an engine that goes further then you need to increase the second column of values.

KSP_Data/output_log.txt tends to be more comprehensive.

The node_attach line only applies to attaching your part to other parts. If the problem is with attaching other parts to your part then it's likely a problem with your collider - if they're going inside then it sounds like it's too small.

Nobody's really messed about with modifying the asset files yet, squad hasn't released tools to open them and they're supposedly specific to the version of unity of the current build of the game (although how specific I don't know). As a workaround, you should be able to write a plugin that changes the sound files you're interested in though.

Is it the centre of mass or is it the scene origin? If it's the scene origin then you can put it where you want and move the center of mass using the CoMOffset parameter.

Define good. Blender has a rubbish interface but I don't think there are any other entirely free programs that has the full range of capabilities that KSP supports.

It toggles the motor, I thought setting that up to the landing gear key by default would be fairly intuitive but I've heard a couple of comments on it so I might remove the default assignment for the next version. All that sort of thing is still wide open, so if you think they should be stiffer/slower they can quite easily be changed for the main release. I carefully set them up to get the maximum suspension travel out of the model, any further and the suspension pistons would come out of their sockets or the wheels collide with parts of the frame. There's no point providing adjustable suspension travel in the config files, although most of the stuff is in place for in-game suspension height adjustment to make docking and similar easier. Short of a clunky custom GUI there's no obvious place to put such indicators now stuff generally has been moved off the staging bar so I'll probably wait until squad re-add the functionality. All of the action groups have on/off status anyway, they just lack indicators at the moment, so if anyone makes a general mod to show action group status it should work fine with this.

No, attachment joints are attached to the top level part GameObject rather than the model (which is a child of the part gameobject) so there's no way the model can affect them.

Unity doesn't give any error message when importing them? I take it you've opened the textures in another program to make sure they are being exported properly?

Most of Europe, South and Central America and half of Africa. The blue countries on this wikipedia map in fact: EDIT: Two of of the three biggest english speaking populations don't use it at all, but use lakhs and crore instead.

0.18 did transfer a lot of the stock parts over to new stock modules, and all of the forum information about that was lost in the forum crash in April so that's most of the cause of your difficulties. As you're not familiar with the PartModule system it sounds like you're troubleshooting GameObjects and config files (as it was common in plugins long before November) so answers will tend to be fairly simple if you go ahead and ask the questions here. I don't know the difference between Decoupler and DecouplerGUI, both are legacy part-derived classes. ModuleJettison is used for the stock fairings.

I do seem to remember the devs mentioning a stub vessel type class that retained original vessel information (name etc.) when docked. Unfortunately I don't remember where it was stored. If you've looked through the vessel and part classes for references then you could try grabbing the components on the docking nodes or current root part and see if there is anything there that looks likely: foreach(Component aComponent in aPart.gameObject.GetComponents<Component>()) { if(aComponent.GetType().ToString() != "UnityEngine.Transform") print(aComponent.GetType()); }

As far as I know there's no mechanism for the stock modules to interact with each other like that, you'll need a custom plugin.

CelestialBody.bodyType may eventually do this, right now the only entry in it's enum is generic though.

It's traditionally engineering notation, as opposed to mathematical notation of 1 x 109. Personally I'd say computer programmers tend towards using the mathematical notation generally (or 1x10^9). Only in languages/countries that define billion as 1000 million, and not a million million.

FlightGlobals.Bodies

As for #1, are you trying to change the orientation by rotating the object that has the part tools attached in unity? If that is the case then it won't work as that rotation doesn't seem to be exported by the part tools, you either need to rotate a child object (e.g. the RATO18 object in this example) or re-export the model from your modelling program (make sure to freeze/reset transforms if applicable).

A) thrustTransform is just the name the stock ModuleEngine using parts use, the actual name doesn't matter. All that matters is that it's identical to what you have in the thrustVectorTransformName field in the config. thrustTransform is the stock term used for for ModuleEngines, which uses the negative Z axis for the direction of thrust, the Y axis is used by ModuleRCS, where the corresponding name used on the stock parts is 'RCSthruster' (although of course, you can name if thrustTransform if you like as long as you specify that in the config file as well).

No. Part rendering cuts off at 5km or something. I don't quite see what advantage you'd have from attaching part components over just spawning the model.

http://forum.kerbalspaceprogram.com/showthread.php/7529-Plugin-Posting-Rules-And-Official-Documentation?p=156430&viewfull=1#post156430

The sticky explains it in detail, but basically the lines with buttons are methods tagged with the [KSPEvent] attribute and the lines without buttons are fields tagged with the KSPField attribute with the guiActive property set to true.

Use the [KSPAddon] attribute on a monobehaviour subclass, it does have arguments as to which scene it will run in - you probably want the flight scene.

ditto, that's all done. The difficulty is that tracks don't rotate so turning generally involves much higher forces as you're dragging stuff sideways. I haven't really thought about what the exact problem is, but there does seem to be an issue where better results would sometimes be achieved if some tracks modified their output depending on other tracks.