Rich

While I can, and always will see some benefits of having sub-forms for particular KSP modifications, it does have the potential to cause problems, which make it unlikely to happen. This is because displaying preferential treatment for one particular modification will open up the doors for many other requests for sub-forums such as for kOS, and its derivatives; MechJeb, and its endless support threads and RT2 to name but a few. We would ultimately end up with so many sub-forums that there would, in the end, be no benefit at all. What is the solution to this? Well, if we look at some of the larger KSP modifications, then we can see that some have created sub-reddits, which I personally think is a reasonable solution.

As you are a new user your posts are moderated (this will stop when you hit approximately 5 posts). Your thread has now been approved and is here. Welcome to the forums~

Version 2 of the API is in the design phase and will: Automatically generate the API on entry to the flight scene so all KSP data will be available. Still allow the definition of non-automatically generated calls. This is a must for creating derived values from the game data, which would otherwise be too expensive. For example, returning a list of all the bodies in game would require 10+ API calls, but with an appropriate derived API call would need only a single call. Be served off /datalinkv2 so the old API will still work and can be mixed with the new API.

You can use the b.name and b.number API calls to create a local mapping between body names and their ID.

Added some additional API calls: Telemachus 1.4.21.0 Change Log * Added API calls to retrieve the state of the landing gear and brakes. * Added API calls to retrieve the total number of bodies, the radius of a body and the max atmosphere height of a body. I have been going for many small updates recently as this fits my free time pattern. Hopefully I will have a weekend to myself soon, so that I can knock some of the chunkier features/requests of the list.

*drool* I will see if I can make the API additions when I get home this evening.

Ah sweet, it is a web interface using web sockets - I was assuming it was a .NET application. I see that you are in need of a mechanism for retrieving the radius of a body. I will see if I can add this to the API.

Hurrah! I always knew that this was possible, and now there is finally a proof of concept.

Indirectly. The partial completion of the web socket server means I will be able to complete the hull cameras in a more satisfactory manner.

Thanks for reminding me about this. I have made a note of these integers in the slowly forming Telemachus Wiki.

Check out the Nexus 5. I have nothing but praise for this phone.

I propose that we use an open source GitHub clone, such as GitLab, as a starting point. I suggest this based on my experiences using GitHub itself to develop and distribute my small contributions to the KSP community. To demonstrate the partial viability of using a git backed system, I will address the OP's "Two bits" in terms of how GitHub fulfils these requirements (coupled with the vision to specialise and extend GitLab to support similar features). 1) Analytics - GitHub provides some analytics, but not nearly enough. However, I suspect these extra analytics could be added to GitLab. 2) Searching - The clone I am using as an example includes a search function. Is it any good? I have no idea, but again I am sure as a community we could improved it if needed. 3) Moderation - I feel a solution to this is independent of the platform developed. 4) Versioning - GitHub releases is amazing. Potential issues that I see: * The scalability of GitLab. * Git is not suitable for every project, but coupled with a GitHub releases style system this would not be a problem. * Everyone is not familiar with such rich project tools? Well, there would need to be some serious UI specialisation to make it suitable for a modding community.

Bug fix update: Telemachus 1.4.20.0 Implemented a fix for the above issue. The following web socket service command should now turn on lights (but not the light on a Kerbal's helmet). { "run": ["f.light[true]"] }

The argument to f.light is optional and should be formed as: { "run": ["f.light[true]"] } However, I actually think the "run" command is partially broken right now. I will try to fix it this evening. Thanks for reporting this issue!

Please read the what not to suggest list before posting. If you strongly desire to know more, then please use the forum's search function.

Thanks for the bug reports/suggestions! Bug fix update: Telemachus 1.4.19.0 Done! I knew exactly where this was as soon as you mentioned it ...; it should now be fixed.

Bug fix update: Telemachus 1.4.18.0 Hopefully this will work now. That is an issue with KSP. I am not seeing this issue at all. Hopefully this has been fixed Please let me know if there are anymore explosions.

I have managed to experience this issue myself! Fixing this is a priority, as I can forgive many bugs, but not those relating to stability.

That is referring to web sockets which come with the .NET framework. The web sockets Telemachus uses are custom built, and they do work on Windows 7 because I develop Telemachus on this OS. What application/code are you using to connect to the web sockets?

It is certainly possible, but it isn't a priority feature right now. I might have broken it with the last update; I plan to do a bug fix release this weekend so I will check it out then. Are you using a web socket framework which supports the RFC6455 protocol?

Yeah, Rob no longer works at Squad. Thanks for flagging this issue and I will raise it with the powers which be. Rich

Thanks for your report Sli, I will check out all of these issues. I better do some more intensive load testing on the web socket server

Not currently, but I have just completed the first release of a web socket server which makes this feature possible to implement in a satisfactory way. I am clueless also ..., maybe I can ask one of the devs. Development Note Telemachus 1.4.17.0 has been released. Grab the install files and the change log here. No new usable features, but the web socket server is at its first release so I though I would distribute it for feedback. Here is the web socket server documentation

It is possible, but 1.) It would take a lot of time and effort t build and 2) I lack the web development skills to do it myself.

I thought they corresponded to the time at the start and end of the current patch? For example, if at the end of your next patch you are changing into the Mun's SOI, then one of those values should give the time to SOI change. I am not familiar with MonoDevelop, but I can add in those two new API calls for you. I plan to do a release this coming Friday/Saturday. Hi Doudou, please could you clarify what you mean by "orbital order"?