Ziw

Guys, I really find the 10000 bytes storage on cores insufficient. I am not a fan of creating unreadable code with short named variables and such, I propose to set this number as a config option. I really like KOS and it is challenging enough to have RemoteTech and KOS at the same time but this limitation of 10k code is quite silly IMO. //rant off - - - Updated - - - BTW it seems that version 1.6 of RemoteTech broke the RT2 integration in KOS. At least none of my scripts loaded into probe's memory work properly now when it comes to steering/throttle.

Kronal Vessel Viewer http://www.curse.com/ksp-mods/kerbal/224287-kronal-vessel-viewer-kvv-exploded-ship-view Does it look like what you're looking for?

Hooray! After a couple of very long evenings, a lot of Wikipedia browsing along some peeking into MechJeb sources for ideas (as I'm not an astronomer and had zero knowledge about orbital mechanics and maneuvers) I've finished my automated rendezvous script. It has some limitations, like the chaser must be in a lower orbit, which in turn must be quite close to a circular orbit, but it works! I found out the hard way that programming and testing KOS scripts may be even more addictive that playing KSP - time flies past really fast. BTW it all started when I decided to try RemoteTech for my second playthrough and stumbled upon Rescue Kerbal from orbit mission. I could've saved the poor sod from the orbit in 1/100th of the time i spent on writing the script but I call WORTH. I learned/remembered more about orbits, vectors and orbital maneuvers in 2 days more than in last 10 years (and I have master's degree in applied math and computer science, this helps a little bit). I will not share the script itself as I believe the learning experience of writing it yourself is priceless and I don't think my script is good enough to be shared (pretty sure there are some noob things there). If you need some pointers you can look into MechJeb sources for orbital maneuvers, though some things cold be done more elegantly through built-in KOS functions. On a side-note I found a strange behavior/bug - when KSP is on pause (via ESC button) with KOS Terminal open on probe, for some reason probe's electric charge is still consumed (very slowly). I noticed it while alt-tabbed to notepad++ for prolonged periods - when I return to KSP and unpause the game the probe's EC can even go to 0 and I had to wait until solar panels replenish the charge. I remedied it by putting bigger batteries on my probes in sandbox mode, but I still find this behavior as strange.

Hi everybody. I have a question on KOS interaction with RemoteTech as I started a new playthrough with a lot of new mods. I wrote a program that automates launch of a probe to an LKO (80km) and then creates and executes 2 nodes at next peri and then apo to bring an orbit to desired altitude. It worked perfectly without RemoteTech installed, but now, when I need the KOS autopiloting features the most it refuses to work (at least as I expected it to). The launch script works nicely because there is still connection to KSP and I get the probe to LKO, but problem is that as soon as I loose connection to KSP I cannot execute any nodes that are in the darkside due to being unable to steer in the right direction via lock sttering to xxx. Basically this code from my exenode.ks script just hangs until I get the connection to KSC back, because the ship is unable to steer. ... set np to nextnode:deltav:direction. lock steering to np. wait until abs(np:pitch - facing:pitch) < 0.15 and abs(np:yaw - facing:yaw) < 0.15. ... Am I missing something? Is this behavior normal? EDIT: Seems like known thing, need to modify KOS config, should have googled better before posting.