Ziw

Fixed

Don't worry, we have your back! Check out the improved ServoControl window:

Oops, I just copied your code without thinking, of course it is PILOTMAINTHROTTLE - - - Updated - - - I suggest you file an issue here: https://github.com/KSP-KOS/KOS/issues

Control-C in terminal window should terminate running script - - - Updated - - - Well, it is actually possible if our script does not lock throttle or steering. You can run a script like this on the launchpad wait until alt:radar > 50000. print "Cuting throttle". set ship:control:mainthrottle to 0. The script will not interfere with your manual controls until the wait condition triggers

This looks amazing! Will use it on main save after a couple bugfix releases

I have 30+ mods alongside Ven's, including B9 and Astronomer's pack and I still have around 1gig Ram limit available. Have you tried running KSP in OpenGL mode?

That rework is actually moving forward quite nicely We're hoping to bring some improvements, both on stability/performance side and UI/usability side quite soon, if we get sirkut's blessing.

It should be in the nearest release. Or if you're github/compiler friendly, you can use my repo (https://github.com/ZiwKerman/KOS) and get a preview version.

The work is underway to provide better integration of IR and KOS, but it is in really early stage.

Nice part! I've also written MM config for KAL-9000 part, but yours look more fitting.

I can't see anything, gives error 403.

/GameData/VenStockRevamp/PartRevamp_TextureReplacer.cfg just rename it to PartRevamp_TextureReplacer.cfg.bak or try to update Texture Replacer - there were some hotfixes

Errm, is it just me or the KerbalStuff zip does not have part.cfg?

Blackscreen Kranken. Delete TR reflections config.

Well it did work for me... Have you tried reverting just the Gigantors to stock by editing MM config?

One thing IR really needs IMO is some kind of interval movements commands, like - "Rotate 1 degree" or "Translate 1mm". I know that I can do this through KOS (which I already did), but it is such an unnecessary chore, IMO better to be implemented inside IR.

Remove TR reflections from Ven's mod (rename TR reflections config to .bak) and see if it helps.

I'd say that trio of RemoteTech + IR + KOS mods make the game so much deeper. It's like a sandbox within a sandbox.

You can try to cheat a little bit and rotate the cupola in the opposite direction of the rotating part.

Before version 1.5, I had to use different tools to calculate orbital parameters, battery requirements and darkness times, now it is all in one place and really visually pleasing. Thanks for this tool!

I just realised that RequiredPower consumed by CPU depends on whether or not you are using Archive If you switch to Archive CPU consumes 0.2 EC/sec, if you switch to local volume it consumes 0.02 or 0.04 depending on CPU size. Is that an intended behaviour? Also please see issue #632 Boot file selection bug (simple fix inside).

If we are discussing the change of the name only (without changing how it works), then why not just LIST VESSELS? It makes sense as it returns a list of elements of type Vessel. Done, issue #623

I am experimenting with running multiple cores on one ship and trying to find a way, apart from obvious tagging, from within a script to locate a part of the ship that is the active core itself? I want to use this to save bootloader script name in the each core's tag to be executed on this core whenever the ship loads from rails. All I can think of requires some basic string operations, which are not yet present in KOS. Maybe something like "list cpu" command which behaves like "list parts" command, but returns the list of all cores in physics range with some indication of active cores (almost the same functionality you get on a welcome screen of a telnet terminal).

To Developer(s): As discussed in KOS thread (http://forum.kerbalspaceprogram.com/threads/68089-0-90-kOS-Scriptable-Autopilot-System-v0-16-0-2015-2-20?p=1761407&viewfull=1#post1761407). Is it possible to add KSPEvents to robotic parts mimicking "move +" and "move -" KSPActions, or even implement proper iterative movements by introducing "move +"/"move -" buttons to move for 1 unit set in Min Increment field? Reason is that due to recent changes in KOS career limits KSPActions are not accessible to KOS scripts until VAB/SPH are fully upgraded, but the only way to move robotic parts in scripts and not through GUI is via calling to KSPActions, which severely limits early and mid career automation of robotic tasks.

As I said, I understand your intentions and mostly agree. Just a little but frustrated that IR's mechanics are not accessible outside of their GUI without action groups. But the same goes for RT antenna targeting for example - you cannot target the RT antennas via KOS script (as discovered by someone earlier in the thread), best you can do is open the GUI. Only hope for early robotics would be asking sirkut to add KSPEvents to robotic parts mimicking "move +" and "move -" actions. Or even implement proper iterative movements - eg "move +" button to move for 1 unit set in Min Increment field.