Corax

Very much agreed. Plus, if the unscaled launchpad actually turns out to be too small, how much of a hassle do you think it would be to adjust that in a quick bugfix, or (heavens forbid) in the next major patch...

The telemetry plugin's IP address should be set to 'localhost' out of the box (which is the same as 127.0.0.1 for all practical concerns).

Press F4 in-game. No config changes needed.

That was the first thing I tried, and it didn\'t work. I\'ll try it again just to be 100% sure, as that would be a lot easier than running it through my landing gear like I currently am doing lol. Thx for responses. It does. See attached craft.

My pleasure. You are of course free to include them in your next release if you like. All credit is due r4m0n If you do, you might want to change the cameraNames to two unique names, like Pilot and Commander, that was an oversight when I quickly copy-pasted them in. Anyway, thanks for the great model, I\'m having an awful lot of fun with it

Wow, just wow. It is quite clever, you may say so with all justification. I was trying to head in the direction of modularity, but obviously you put a lot more thought into it... Many thanks for sharing the code, there\'s a lesson or five in it for me

For those using r4m0n\'s excellent camera module (or MechJeb, I guess), here\'s a code snippet that gives you two cockpit views (commander and pilot) MODULE { name = MuMechModuleHullCamera cameraName = Cockpit cameraForward = 0, 1, 0 cameraUp = 0, 0, -1 cameraPosition = 0.4, -0.2, -0.23 } MODULE { name = MuMechModuleHullCamera cameraName = Cockpit cameraForward = 0, 1, 0 cameraUp = 0, 0, -1 cameraPosition = -0.4, -0.2, -0.23 } Paste into KSP/Parts/RedSpar_Eagle_Pod/part.cfg and enjoy

The trick is not to \'burn through\' 5000 Kerbals - you have to keep them alive to have new ones generate. Also you will have names come up double and triple long before you have seen all possible combinations. Prepare for a long ride.

I find that most of the time I want each individual ship/module to send individual data fields, but usually at the same data rate and formatting/comment options as the others. I usually use the same IP/Port for all, too, but I figured it might be handy to have different modules send to different receivers... so once I had the persistence part worked out, I decided to leave formatting options etc. global to quickly change those in one go. 'What' as in 'what\'s in the sound', or as in 'I haven\'t noticed any sound'? The SFX are just simple audio indicators for module de-/activation and data transmission. There\'s no meaningful data in there to be decoded. If you can\'t hear them (rising/falling sound on activation/deactivation, and a warbling sound during data transmission), make sure you have sounds activated in KSP (duh! ), and you are actually transmitting data, i.e. the telemetry module icon is green.

After an hour, I worked out that these columns are built into the ship, presumably upon launch. A quick search/replace of the persistence file and I\'m good to go. 8) Thanks for that hunt and seek - you\'re a sly one ... Sorry for the hunt, maybe I should have made it more clear exactly where the persistent data (hint, hint ) is being stored... going to try and fix that. I say in the OP that but I admit that isn\'t very precise. As you found out, editing the part.cfg only affects new modules pre-launchpad, once you have a flight scene, your 'flight' along with the current module configuration is stored to the persistence.sfs and quicksave.sfs thereafter. I\'ve tried to strike a balance between which options are saved with the module, and which are global for all modules; I\'ll also try and differentiate more clearly between the two in the next update. In the long run, I envision a graphical user interface in-game where you can configure each module individually.

I\'m using gnuplot to generate simple rectangular projection maps, and although it takes a while, it handles even larger files with ease. The raw data file is some 14GB, but contains a lot of information that\'s useless for mapping (pressure, temperature, time etc). I\'m really curious to see what you can make of it

Kind regards, Innsewerants Good to see you\'re back! I was wondering whether your MapGen can use input files with higher precision, i.e. more decimals? If so, people could use the crxTelemetry plugin for the time being, until you release an update. It can be configured to output its data in (almost) the same format as ISA_RAM. It lacks ISA\'s wide-range beam as well as the beautiful antenna part, but for the time being it might just work; I can\'t properly test it because isa_RAM_MapGen.exe doesn\'t like my Linux system: $ mono isa_RAM_MapGen.exe Unhandled Exception: System.ArgumentException: Culture ID 0 (0x0000) is not a supported culture. Parameter name: culture at System.Globalization.CultureInfo..ctor (Int32 culture, Boolean useUserOverride, Boolean read_only) [0x00000] in <filename unknown>:0 at System.Globalization.CultureInfo.GetCultureInfo (Int32 culture) [0x00000] in <filename unknown>:0 at System.Globalization.CultureInfo.get_InstalledUICulture () [0x00000] in <filename unknown>:0 at isa_RAM_MapGen.MainClass.Main (System.String[] args) [0x00000] in <filename unknown>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.ArgumentException: Culture ID 0 (0x0000) is not a supported culture. Parameter name: culture at System.Globalization.CultureInfo..ctor (Int32 culture, Boolean useUserOverride, Boolean read_only) [0x00000] in <filename unknown>:0 at System.Globalization.CultureInfo.GetCultureInfo (Int32 culture) [0x00000] in <filename unknown>:0 at System.Globalization.CultureInfo.get_InstalledUICulture () [0x00000] in <filename unknown>:0 at isa_RAM_MapGen.MainClass.Main (System.String[] args) [0x00000] in <filename unknown>:0 I say almost the same format because AFAIK ISA_RAM rounds to one decimal, while crxTelemetry uses KSP\'s internal values.

Finally, here it is. 97M data points, cleaned up, sorted, rounded to five decimals, 2.7GB of Kerbin CSV data packed into an archive just shy of one gigabyte (note: comma separated values, not semicolon as in ISA RAM). I reply here because it\'s neither ISA_RAM format, nor was it collected using ISA_RAM. I\'ll leave it up for a while, but will ultimately remove it again simply because of its size

Fun history fact: The mile is actually called a mile because of the Romans, who used 'milia passus' ('a thousand steps'), but in Ancient Rome, a 'passus' was what we\'d call a double-step. That\'s because the second is an SI unit, but the 'hour' is not (it\'s an 'accepted' unit), so using km/h is not so much different from using miles/h. There\'s a factor of 3.6 (60 minutes of 60 seconds to the hour divided by one thousand); for a very rough estimate simply multiply m/s by 4. I don\'t see why the 'metrification' should stop there, but all attempts at a decimal time base have failed so far, the last serious attempt during the French Revolution.

True, but keep in mind that 37km on Earth is not the same as 37km on Kerbin; on Earth, LEO is around 200-700km, on Kerbin that would be more like 50-70km.

Here\'s a part.cfg for the Mk.1 Pod for those who wonder why they can\'t switch cameras on a rocket... Put it in KSP_win/Parts/mk1pod/ , backup and delete the old part.cfg, and rename mk1pod_part cfg to part.cfg

...and merged with the other Mars One thread.

There is no 'light side' of the Mun. From Kerbin, there\'s a near side and a far side. Same goes for Earth and Moon.

For those poor Linux users who don\'t have access to VisualBasic: $ grep part.= Ships/VAB/my.craft | sed \'s/_/ /\' | awk \'{print $3}\' | sort | uniq

It errored, (assuming it hit the 0.0.0.0 reference like before, flipped over to the next one and I have data in my mono UDPReciever.exe Hurrah! default options and on localhost lookup Glad it works, thanks for the feedback!

Thanks for explaining, I see now what you are doing there and why.

Just a quick question, so far I\'ve only glanced over the example: Why the conversion from kg to kerbogram? Shouldn\'t mass be the same everywhere, and only the weight force require adjustment? Or am I missing something obvious?

You might want to reconsider rule #1...

I have uploaded a new version of the plugin. New feature: Sound! Changes: (Hopefully) more robust address resolution, more data fields, more configuration options. Have fun

I suggest you use ncat from nmap.org (click here for Windows download), as I wrote in the original post. It is much more reliable and flexible than the very basic UDPReceiver Basically, why I included UDPReceiver at all was as an example for others to build upon. As BarryCarlyon said, the IP port is hardcoded in the UDPReceiver. If there is demand, I may make that configurable. EDIT: Depending on your scenario, you can of course capture both (or multiple) transmitters with one instance of the UDPReceiver (all transmitters using the same port and address), and filter the output by the module UUID. EDIT 2: Not out of the box, but as long as all modules are within 'physics' range from each other (on the same vessel, or up to ~2.5km apart), you can always edit the persistent.sfs to your liking. If you don\'t feel confident about editing the .sfs, you can also launch one vessel, exit KSP and edit the telemetry part.cfg, then launch another vessel; the settings are remembered individually for each ship.