I do not consider this thread to be spam because discussing flight operating procedures is pretty "geeky". So please ladies and gentlemen stop derailing the thread and targeting the OP.
While I appreciate your forward thinking, this thread will just fill up with excellent ideas which should really be placed in the Suggestions and Development Discussion forum.
Hi RoverDude, Could you do this sooner rather than later please, as providing source code is a requirement of posting a plugin on the KSP forums. Thanks, Rich
I will be using a similar setup to Telemachus. So yes, the code will be going on Github and the documentation on the associated project wiki. Now I just need to get off my bottom and tidy up what I have, so I can release what I have so far.
Mainly a bug fix release - Download and change log for v1.4.23.0 Additionally: * Tested custom resources with 0.23.5; using the "AblativeShielding" resource from Deadly Reentry v4.61 works. * Tested sensor readings with KSP 0.23.5
So, I'm going to take a guess and say that two argument API calls are broken (with websockets) because I am being a bad person and parsing my JSON with regular expressions, which is theoretically a bad idea. I'll try to fix this issue later today. Please let me know if you have any other issues
[table=width: 100%, align: center] [tr] [td=width: 25%]2/5/2014 - This might not look like much, but after some wrestling KSP and MCT are now talking. The next step is to expose the data as MCT feeds so that the data can be displayed and composed using the GUI.[/td] [td] Figure: Data flowing into the telemachus-mct plugin [/td] [/tr] [/table]
I hope so, but if not, this program is highly extensible so it should be easy to include. Small update - My development environment is now sane so now I can focus fully on programming.