[[1.3] kOS Scriptable Autopilot System v1.1.3.0]

The issue is that you are steering with SAS turned on. Remote tech negates the stock SAS control, and so it fails to steer correctly. The documentation appears to only call this out for setting SASMODE (see here: http://ksp-kos.github.io/KOS_DOC/commands/flight/systems.html?highlight=sasmode#global:SAS) I will modify the documentation to identify that lock steering using SAS is also limited in remote tech. If you turn off SAS, it should start to work. If you vessel is unstable using the current kOS steering code, I'm working on pushing an update to that code as quickly as possible which is significantly more accurate.

Let me know how it goes with SAS turned off.

YOU ARE A GOD AMONG MEN... i.e. it now works. Thank you so much for your help, I can now launch my satellites properly.

[[1.3] kOS Scriptable Autopilot System v1.1.3.0]

Linux? I'm going to assume so because that's where this problem usually is found.

Unity 4 does some really silly things on its Linux port that really have nothing to do with any native problems in the OS itself and are just Unity *choosing* to introduce differences on Linux that it didn't need to.

Try this mod to fix it. Others have had success with it:

http://forum.kerbalspaceprogram.com/threads/108561-1-0-2-%28Apr27-15%29-Control-Lock-Input-text-into-text-fields-without-issuing-commands-to-your-vessel

- - - Updated - - -

What happens if you explicitly set the throttle value to 0 at the bottom of the script?

When the script ends it should drop throttle to whatever setting it had before you ran - which because of the dumb decision by squad to default the throttle to 50%, is 50% rather than zero like it should be. But at any rate I don't see it dropping to 50% in the video so I assume it still has locked throttle when the script ends.

Also, prove the script ended by printing something at the bottom of it:

PRINT "SCRIPT END".

The last lines of my script is:

print "test 2".

wait 10.

SET WARP TO 0.

print "test 3".

wait 10.

LOCK STEERING TO HEADING(90,0).

wait 10.

SET SASMODE TO "PROGRADE".

print "test 4".

wait 10.

SET throttleValue to 1.

print "test 5".

wait 10.

print "waiting for periapsis".

WAIT UNTIL SHIP : PERIAPSIS > ORBITHEIGHT.

print "periapsis is reached".

// WHEN THE PREIAPSIS IS AT ORBIT HEIGHT KILL THROTTLE

SET throttleValue to 0.

// STAGE.

PRINT "SCRIPT END".

WAIT UNTIL SHIP:ALTITUDE > 120000. // pause here until ship is high up.

It reaches "test 5" and "waiting for periapsis" but not "script end"- so the problem is not that the script stops. I really have no idea why it goes out of control...

[[1.3] kOS Scriptable Autopilot System v1.1.3.0]

I don't know if this is the correct forum to ask for help, but tried at r/kos on reddit and they could not help, so I though I would try here. I have made a script that should take a satellite to orbit. I am using remoteTech and the problem is that my satellite becomes uncontrollable when I loose connection to kerbin. This should only happen if I try to control from kerbin, but this also happens when I copy a script to my satellite and run it. The whole idea behind using KOS (for me that is) is that I can have some predefined action that my satellite should take - and independently of its connection to kerbin - it should do it. A link to the complete file, as .txt, is here as readable through a browser: https://www.dropbox.com/s/2xqjow7habxidvi/A2.txt?dl=0 . Only the last part is interesting, as the initial part with ascend goes well i.e. it is circularizing the orbit that is problematic so I have just copied last last part of the code here:

WAIT UNTIL SHIP:ALTITUDE > ORBITHEIGHT. // pause here until ship is high up.

print "test 2".

wait 10.

SET WARP TO 0.

print "test 3".

wait 10.

LOCK STEERING TO HEADING(90,0).

print "test 4".

wait 10.

SET throttleValue to 1. // full throttle

print "test 5".

wait 10.

A video of the whole ascend and circularizing is at https://youtu.be/Kru6-9Z88H0?t=366 set at 6:15 for the problem.

I have activated RT in kos menu and I don't run the script from 0, but I copy it over to the satellite and run it from 1.

Can anybody tell me what I am doing wrong ? Thanks in advance for any help you can give.

[[1.2.1] Outer Planets Mod (2.1) - Active development has moved, see first post for new thread]

Thanks - it works now I thought that the lines after "It incorporates the following mods:" meant that they were already in the zip files with OPM... my mistake. Thanks for the help guys

[[1.2.1] Outer Planets Mod (2.1) - Active development has moved, see first post for new thread]

I have some problems installing OPM, I believe I have copied the files in the correct folder, but I cant see any of the planets when I start KSP and go to the tracking station. I have taken a screenshot of the gamedata folder: http://imgur.com/4rlaPUc The files should be in the correct directory, can anybody tell me what I have done wrong/need to do in order to get OPM working?