eberkain

Members
  • Content count

    659
  • Joined

  • Last visited

Community Reputation

185 Excellent

About eberkain

Profile Information

  • Location Alabama

Recent Profile Visitors

1928 profile views
  1. The stock parts were all from 1-10 EC based on the overall size of the engine, I kind of stuck with that on the balance for the other mods I've done. What i need is a small mod that adds some ullage motors early in the tech tree.
  2. [1.3] kOS v1.1.3.0 : kOS Scriptable Autopilot System

    The terminal is only active in-flight. You just have to put together something launch it, run your kos tests, revert and make changes, relaunch.
  3. I'm also getting a metric ton of log spam. I'm not sure if its coming from AGX or kOS? Is there a way to disable these messages? [LOG 06:00:39.813] AGX Call: group gtate 204 for active vessel [LOG 06:00:39.814] AGX Call: group state for 205 for vessel 2214072152 [LOG 06:00:39.815] AGX Call: group gtate 205 for active vessel [LOG 06:00:39.816] AGX Call: group state for 206 for vessel 2214072152 [LOG 06:00:39.817] AGX Call: group gtate 206 for active vessel [LOG 06:00:39.844] AGX Call: group state for 201 for vessel 2214072152 [LOG 06:00:39.845] AGX Call: group gtate 201 for active vessel [LOG 06:00:39.846] AGX Call: group state for 202 for vessel 2214072152 [LOG 06:00:39.847] AGX Call: group gtate 202 for active vessel [LOG 06:00:39.848] AGX Call: group state for 203 for vessel 2214072152 [LOG 06:00:39.849] AGX Call: group gtate 203 for active vessel [LOG 06:00:39.850] AGX Call: group state for 204 for vessel 2214072152 [LOG 06:00:39.851] AGX Call: group gtate 204 for active vessel [LOG 06:00:39.852] AGX Call: group state for 205 for vessel 2214072152 [LOG 06:00:39.853] AGX Call: group gtate 205 for active vessel [LOG 06:00:39.854] AGX Call: group state for 206 for vessel 2214072152 [LOG 06:00:39.855] AGX Call: group gtate 206 for active vessel [LOG 06:00:39.863] AGX Call: group state for 201 for vessel 2214072152
  4. Official FAR Craft Repository

    first FAR plane in a long time, forgot how much fun i had flying around.
  5. [1.3] kOS v1.1.3.0 : kOS Scriptable Autopilot System

    It does indeed work PARAMETER CPUID IS -1. IF CPUID = 1 { LOCK AG_ID1 TO AG201. } IF CPUID = 1 { LOCK AG_ID2 TO AG202. } IF CPUID = 1 { LOCK AG_ID3 TO AG203. } IF CPUID = 1 { LOCK AG_ID4 TO AG204. } IF CPUID = 1 { LOCK AG_ID5 TO AG205. } IF CPUID = 1 { LOCK AG_ID6 TO AG206. } IF CPUID = 2 { LOCK AG_ID1 TO AG207. } IF CPUID = 2 { LOCK AG_ID2 TO AG208. } IF CPUID = 2 { LOCK AG_ID3 TO AG209. } IF CPUID = 2 { LOCK AG_ID4 TO AG210. } IF CPUID = 2 { LOCK AG_ID5 TO AG211. } IF CPUID = 2 { LOCK AG_ID6 TO AG212. } ON AG_ID1 { print "MFD " + CPUID + ":1". return true. } ON AG_ID2 { print "MFD " + CPUID + ":2". return true. } ON AG_ID3 { print "MFD " + CPUID + ":3". return true. } ON AG_ID4 { print "MFD " + CPUID + ":4". return true. } ON AG_ID5 { print "MFD " + CPUID + ":5". return true. } ON AG_ID6 { print "MFD " + CPUID + ":6". return true. } In the AHK GUI I can click a button (to later be replaced with a hardware controller) AHK then activates the KSP window and sends a keypress AGX responds to the keypress and actives an empty action group (201-218) kOS script sees the Action Group activation and can react I can run the same script on different CPUs and the script will be able to tell which set of MFD buttons it should react to.
  6. [1.3] kOS v1.1.3.0 : kOS Scriptable Autopilot System

    Let me ammend my question. Assume CPUID is a static value that will never change during the life of the program. Lets say I have the same program running on multiple kOSProcessors and each instance of the scrip has a different CPUID assigned. Is there a way to reduce the number of ON statements when we know the contents of some of the ON statements will never execute. For example, will something like this work? SET CPUID = 1. IF CPUID = 1 { SET AG_ID TO AG1. } IF CPUID = 2 { SET AG_ID TO AG2. } IF CPUID = 3 { SET AG_ID TO AG3. } ON AG_ID { print "Action group clicked!". return true. }
  7. [1.3] kOS v1.1.3.0 : kOS Scriptable Autopilot System

    How about a different question, is there any way to optimize this to use a single ON trigger? SET CPUID = 1. ON AG1 { IF CPUDID = 1 { print "Action group 1 clicked!". return true. } } ON AG2 { IF CPUDID = 2 { print "Action group 2 clicked!". return true. } } ON AG3 { IF CPUDID = 3 { print "Action group 3 clicked!". return true. } }
  8. [1.3] kOS v1.1.3.0 : kOS Scriptable Autopilot System

    Yeah the docs said that preserve keyword will eventually get removed and return true or false is the preferred. I'm also trying to increase the disk size and thats not working for me either, I don't think the mod likes me very much.
  9. [1.3] kOS v1.1.3.0 : kOS Scriptable Autopilot System

    Thats what the Until 1=2 does, puts it into an endless loop., I am an certain the script is running because I have to CTRL C to break out of it.
  10. [1.3] kOS v1.1.3.0 : kOS Scriptable Autopilot System

    I know its late and all, but I can't figure out why this doesn't work. I've read through the page on flow control a couple times and im not getting it.
  11. Is there any way to assign a modifier+key to an action group. I have 18 action groups I need to assign keybinds and I was wanting to use 1-6 on the numpad modified with shift+, ctrl+, alt+
  12. [1.3.1] Kerbal Konstructs - 1.3.1 - 07.10.2017

    Do you have the Launch from Anywhere cheat enabled?
  13. I'm seeing the same thing.
  14. I just test both career and science mode on my install I'm using to setup my 3.2 rescale. I was unable to reproduce the issue you describe. Yes when you return the editor and first click the KK button it says Launch Site Selected Dull Spot, but you can simply click the KK button again and pick whatever launch site you want. I just launched a rocket from the SPH at Mount Snowey, returned and launched again from a carrier, returned and launched again from the KSC helipad. EDIT: Actually I was able to do it. Trying to select KSC Runway instead selects Dull Spot. Output log https://drive.google.com/open?id=1SvixYJDMUDoOVVWP15fJoiNoEZbBxrS4 I was able to launch from the runway again after disabling the cheat option.
  15. Check the settings menu, there is an option to do that.