blizzy78

http://forum.kerbalspaceprogram.com/threads/78067-0-23-5-Research-Them-All-1-1-(April-30)

It may very well be, but stating it is not helpful to any discussion.

Aren't you just contradicting yourself here? Anyway, I don't think it's a good idea to "hide" security sensitive code from the public, nor is it necessary. We should be able to produce a secure system while keeping *all* code in public. Right, Ace is not a WYSIWYG editor.

Just to throw this in here real quick, you might also want to check out Ace.

Please add a license to the OP.

Glad you could work it out.

There is no way to access this information at this time. Even if there was, it doesn't record which Kerbal did what. It does record the "vessel name", which in the case of a Kerbal it would be his name, but really, you can't be sure it has been a Kerbal after the fact.

That ModuleManager config MeCripp posted looks good.

The OP does not mention a license.

One would think that KSP uses some sort of bounding box optimization, in that where the bounding boxes of those two ships do not intersect each other, there won't be any collision checks between those two ships. In the vacuum of space, at least.

My ModuleManager config for the DTM. Seems like it is repeatable to begin with, but not grabbable. // make data in KSP Interstellar's Dual Technique Magnetometer grabbable @PART[DTMagnetometer]:Final { @MODULE[ModuleScienceExperiment] { dataIsCollectable = True collectActionName = Take Data interactionRange = 1.2 } }

KSP Interstellar has the Dual Technique Magnetometer, and it modifies the Gravioli Detector to do impactor experiments. For the DTM, I've modified mine using ModuleManager so that it is repeatable, and that the data can be extracted by a Kerbal on EVA. And then there's also DMagic Orbital Science.

Voice Commander 1.2.0 is now available for download, adding new commands for maneuver nodes, time warp, vessel switching and targetting, as well as optional support for a push-to-talk key.

Yes, the voice server is necessary to use the plugin. For me it works fine the other way around: Starting VoiceServer.exe first, then KSP. If it won't work for you at all, you can try this workaround: Make a copy of VoiceServer.exe and VoiceCommander.dll somewhere else (not inside any KSP folder), then run VoiceServer.exe from there.

See this post. While not being the documentation to my calculator, I think it should clear things up.

It works like this: There are macros, and there are commands. The commands are what you speak into your microphone, for example "set throttle to 50%." Now, instead of programming every percentage value into the plugin, and instead of you typing in the same text in the settings for each percentage value, I've added macros. In this example, the "50%" comes from a macro called <percentageNumber>. You can basically use this wherever a percentage value is required (just the number itself, "50".) The command then changes from "set throttle to 50%" to "set throttle to <percentageNumber> percent". So just try it out: For the "Set Throttle" command, enter "set throttle to <percentageNumber> percent", then speak into your microphone, "set throttle to 50 percent". It should work Note that for some macros, you can customize the texts for various values. For example, the <apPe> macro evaluates to either "apoapsis" or "periapsis". If you don't like these words and would rather use "blue" for apoapsis and "yellow" for periapsis, you can customize that. In the end, you can use the "Turn Into a Flight Direction" command (configured to "turn to <apPe>") and speak "turn to blue" or "turn to yellow" into your mic.

Please post your output_log.txt file. Also, where exactly did you install Voice Commander? (well, what BigD145 said about this)

Does it come up in the list of available buttons?

Sure, I'll add that.

Of course it would be optional. And yes, it's rather useless for single-button functions, but there are quite a few commands already that can't be done by simply tapping a button. (For example, "turn prograde.") Also, did it finally work out on your system?

I'd like to point out that some plugins might have problems if body names are changed. Other than that, neat stuff.

Hmm, I think I need to add something like a push-to-talk hotkey, so that it will only ever try to recognize commands when you hold that key.

It isn't. The foreach statement iterates through all elements of your list. In your case, it contains Vessel elements, not VesselType elements.

Please be more specific. For one, does it output anything?

... *cough*