-
Posts
1,056 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Everything posted by Rich
-
This would be cool and is on my list of features to add. However it is not a priority as it does not give you any additional capability to play KSP using only Telemachus. Also my HTML and JavaScript skills are minimal so this is best left as an addition for someone else to write. Try while not running in full screen and send me the new log.
-
It is indeed a trivial issue, but your point about keeping it consistent with KSP is valid none the less, so as of the current development build it is spelt "oxidizer". I feel it is the small touches which make a project feel more complete . Now if only I could find a programatic solution to the port exhaustion problem, and the time to improve the client side of Telemachus.
-
I doubt the code I have still works with KSP 0.23. It doesn't. I had considered exporting a model of the current ship and displaying data on it, but that idea is on the back burner as I have cameras to complete first. Highcharts looks interesting, especially this demo: http://www.highcharts.com/demo/dynamic-update Even better that it is free for use with a non-profit project.
-
I have just consulted the Oxford English Dictionary and it seems to suggest that "oxidizer" is the only correct spelling. Strangely, the dictionary indicates that both "oxidise" and "oxidize" are acceptable. Wikipedia seems to say that both are OK. Given that I am no longer sure how to spell it correctly and continue my crusade of British English, I think your above suggestion makes perfect sense. I have added it to my list of tweaks to include in the next release of Telemachus.
-
Changing your profile picture changes only the picture on your profile page (you can do that here). To change your avatar (which appears alongside your posts) you need to go to this page.
-
Indeed. If anything I would have expected Chrome to work better as the graphing API was written by Google. Thanks for your post - I have reflected on your comments and have the following to say. 1. I have yet to find a good way to debug JavaScript on a mobile device. I do plan to rewrite all of the pages using a different graphing API anyway, so hopefully that will improve cross browser compatibility. 2. I will update the information page to list the required sensors next to pages which need them.
-
The accelerometer is required for the g-force information. If you are referring to the fact that I have spelt it as "Oxidiser" then this is the English spelling. If I have screwed up the spelling in some other way, I would be grateful if you could tell me the precise location of the error. I do not have regular access to an iPad so limited testing has been done on this device. However, the reports I have received concur with your conclusion - Safari seems to work better for Telemachus.
-
That would explain the access denied error as the default IP used is 127.0.0.1, which is the address of the machine the browser opened on. The secondary IP is the correct IP to use if you want to connect to the machine running KSP from a different device. If your firewall is being a pain you will need to create an exception rule. Usually when Telemachus first tries to listen your firewall will ask you if you want to allow it, but I guess in this case it has not. What operating system are you using? Telemachus has a config file (config.xml) where you can specify the port number. This file can be found in the PluginData folder which is somewhere in the Telemachus directory you will have installed.
-
Access denied you say? Well that is odd. The following are the only problems I can think of. Are you using the IP address of the machine running KSP and not that of the Kindle? Maybe the Kindle doesn't like using a port other than 80, so try telling the Telemachus server to use port 80 (you might need admin priveldges on the KSP machine to do this) It is possible the baked in browser does not support Google graphs; can you get Chrome from the app store?
-
Thanks for that cyoung_mi. I think I have found the problem - there appears to be a bug the Telemachus code in that it attempts to find all the available network interfaces irrespective of whether you specify your own IP. So if it craps out on that lookup, it breaks the entire process and ignores the user specified IP. I will attempt to release a fix shortly - you will still need to specify your IP manually, but hopefully it will actually try your suggestion.
-
This error occurs when something on the system is preventing Telemachus from listening on the specified IP address and port. Could you please send me your ksp_log.txt and config file? Maybe I can spot the problem. I certainly appreciate your persistence in trying to get this to work; hopefully we can resolve this issue and I can either improve Telemachus or the user guide. Someone was working on this - it functioned very well but was never finished. I think there is a development version you can download. Figure 1: Navball in the web browser powered by Telemachus