Jump to content

[1.8.0-1.12.X] Baker Operating System v2.2.0 a KOS RPM IVA GUI autopilot script


SelfAwareMatter

Recommended Posts

Yeah, this code definitely does not work "out of the box".  Instead of toggling the CLOBBERBUILTINS option, I went into the code and made a few edits to my local copy, such as:

  • Changing "set throttle" to "lock throttle", and making sure there was a corresponding "unlock throttle"
  • Changing one instance of "set steering" to "lock steering", and making sure there was a corresponding "unlock steering"
  • Setting "sas on" after "unlock steering" in maneuver functions
  • Commenting out one instance of "ag3 off"

Now I no longer get the CLOBBERBUILTINS error, but I get the following:

Uq1hVv5.png

This looks very similar to the error in Frostiken's note from last year (4 Sep 22).  I didn't get the "SETDELEGATE not found on object BUTTONS", but perhaps that text scrolled off the top.  I first got this error for button 3.  I noticed that this was the first "buttons:setdelegate" that the code attempts to perform, so I commented it out - result, the error moved on to the very next buttons:setdelegate attempt (for button 4 instead of button 3).

I also see that 610yesnolovely said on 5 Sep 22 that I need to be using kOSProp Monitor v 1.7.2., and that the CKAN version is outdated.  I checked CKAN, and sure enough I'm using 1.5.1.

So, questions:

  • Do I need to upgrade kOSPropMonitor to 1.7.2?  Will these button delegations not work otherwise?
  • Is there an updated version of the BakerOS?  Both CKAN and SpaceDock provide what is titled as v 2.2.0, but the comment at the very top says this is v2.1.0.  Is there a more current version somewhere else?
Link to comment
Share on other sites

Update:

Yes, upgrading from the kOSPropMonitor version on CKAN (1.5.1) to the version available on SpaceDock (1.7.2) is required to get past this error, and to get buttons working.

I find the script itself kind of wonky to work with.  It's difficult to figure out how to move between screens, how to provide input to the various screens, when to use buttons and when to use keyboard, etc.  But, I've learned a lot by looking through the code.  I'll probably take some parts of this as starting points and write some scripts of my own.

Link to comment
Share on other sites

  • 4 weeks later...

Hey guys sorry for being mia for a bit. I have returned to update my mod and boy oh boy i didnt realize so many people would we using it.  I have a new version uploaded with a ton of new features and i have taken care of many problems the script had.  The buttons have been fixed! Garbage collection issues have been fixed as well. It runs smooth as butter.  Ive added a few new scripts and have updated almost every single existing one. Many of the issues you guys are having should be fixed now. Any questions shoot me a response i will try to respond quickly

Link to comment
Share on other sites

  • 2 months later...
  • 4 months later...
  • 2 weeks later...
On 5/19/2024 at 3:09 AM, J534 said:

Just tried running BakerOS and I get this error: Error.png

Anyone know what I should do? Also @Nikodga so far to get where I'm at I entered the following commands:
 

SWITCH TO 0.
RUN BAKER3.

 

I did a little research in the kOS wiki.  You have 2 options to get this to run.  the first is to open the baker2.ks file in notepad, then add this line:

@CLOBBERBUILTINS on.         on the very first line.  This is one way.

The other is to set up custom settings on a new game.  Hit new game, then click the difficulty button.  Find the kOS tab, then click the button that allows clobbers.  The difficulty will then show custom instead of normal.

 

The first option allows clobbers on that script only.  The second allows it on all scripts.

Link to comment
Share on other sites

  • 2 weeks later...

So I'm getting to grips with this, and kos in general. This script has gotten me more excited for ksp than I've been for a game in many many years. 

Is the discord still going? The link is expired and I'm guessing most of my questions have answers in there. 

I've been getting some odd initial screens popping up (they look like ports on a screen numbered 10, 20, 30 and so on). 

 

Some documentation on how scripts work would be great aswell, variables etc. Also getting some gui bugs like 'printscreen' and after a script getting kicked out of BakerOS.

Link to comment
Share on other sites

  • 2 weeks later...
This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...