erendrake

I think it would be a better idea to not make heterogeneous lists in your code. I almost enforced this in the list structure with generics.

Really cool work you have been doing. I am excited when we have fewer bugs and i can spend a little time playing KSP with kOS and your editor

Alright everyone, there is a hotfix up on spaceport. It fixes some of the worst bugs that have been brought up here on the forums. This is not 12.1, just a hotfix to keep people from having a horrible time. * Fixes flight control being busted on launch * TIME now respects the new KERBIN_TIME setting introduced in 23.5 * Division and Multiplication operator precedence is less surprising * Vectors give a much clearer error if you abuse them It should be up now so everyone let us know if your life is any better with the new version. Good hunting.

This has to do with me never switching to UT in the map view before. Now its me staring at the useless time code and adding a bug to Github. Thank you @baloan.

What OS are you using? Sorry if you mentioned it before. Or maybe you are on 64-bit? Edit: I was able to reproduce it finally. Thank you Rosco and Entropius for helping isolate the issue. Now to figure out what the hell is going on.

So no RemoteTech? that is the one i am most worried about. Thank you very much for the list. if you open the game does it lock the throttle on the first launch or only after you "Revert to Launch"?

For those of you who are having this problem. Would you mind listing out the mods you have installed? I cant reproduce the problem and it is bumming me out

By UT I assume you mean UniversalTime? TIME is UT with a structure around it, really missiontime should have the same structure but i havent gotten around to it. if you want to get UT in seconds its TIME:SECONDS

That does sound like a pretty lame remainder problem, Would you mind adding a bug in the github tracker? Throttle control locking has a bug that i am actually working on as i post this. You can watch its progress Here: https://github.com/KSP-KOS/KOS/issues/69

Some have mentioned it already but we have a new release of kOS v0.12.0 This release has been a lot of work by a few dedicated members of the community. Big thanks out to those involved Thanks to all of the hard work by @marianoapp and @Dunbaratu, We have a new parser! Known Issues ====== * There's no built-in editor, the "edit" command is parsed but it doesn't do anything * Some subprogram termination can hang kOS unexpectedly * Steering control does not always release on execution end Changes ====== * the aforementioned new parser by @marianoapp with all of its speed improvements and other goodies. * There's a config SpecialValue that can be used to control how some of the mod features work, like setting the execution speed, the integration with RT2 and starting from the archive volume. * The terminal screen can be scrolled using PageUp and PageDown * Negative numbers/expressions can be written starting with a minus sign, so no more "0-..." * Added ELSE syntax! * Added ELSE syntax! * Added NOT syntax!! * Added List square brackets [] as list subelement accessor * you can use variables as arguments for PRINT AT statements This version adds a new 0.625m part. Thanks to SMA on this neat new addition. * it works as a kOS computer core * has 5000 units of code space * as a smaller part it is unlocked with "precision engineering" in career mode. * also has a light that will be controllable before the actual release Bug fixes * Cannot "set" a variable that later will become a "lock" #13 * Sanitize values sent to KSP #14 * Strange order of operations: "and" seems to evaluate before ">" #20 * moved some names back to "kOS" * Work on some structure's ToString return. * Parameters now get passed in the correct order * Ship resources no longer generate an error if they arent present * Ctrl+C now interrupts correctly once again. * ETA:TRANSITION returns the correct time. * Better handling of types. If you notice an issue we have a list of bugs for an upcoming patch on the github tracker, you can check the status https://github.com/KSP-KOS/KOS/issues?milestone=2&state=open https://github.com/KSP-KOS/KOS/issues

in your case it would be set nd to nextnode. print nd:orbit:apoapsis. [/COPY] The reason for the change is now you have access to all of the rest of the orbit info and if we add more to orbit ( we will ) it will be there for every orbit access method. I think i had listed it in breaking changes but it looks like maybe i missed it, my bad.

We have done this with KOS and other than the separation anxiety for me the biggest issue has been having to start over with issue backlog. I could not find a way to copy issues to the new account. Its a good thing in the long run.

This is a known bug that we are working on for v0.12.1 if you are using LOCK STEERING you can try UNLOCK STEERING before the end of your script. you can track the progress on this issue https://github.com/KSP-KOS/KOS/issues/69 Sorry for the inconvience

We are just now releasing a version that will allow you to run code if you are connected and it will continue to run if you lose connection. All of the features you are asking for are on the list of things to do. I think that key input should operate with the delay. Delay stuff gets complicated because I believe we should allow you to send commands even if you done have a connection because you might very well have a connection after the delay is finished. I also believe we should have antenna requirements in stock just like science does. I would love to have power drain when you are using the antenna, just like science does. We have an endless amount of work to do. Job Security i guess.

Do you have remotetech installed? I was fighting a bug right in the end with RemoteTech and i thought i had it licked. Update: Updated the release with some code i forgot to include. This is exactly why i put it up on Github first

I didnt realize you had removed it. it used to show on bootup when you power cycled. I would be happy to include a new font file if someone wants to build us a new one

It is never safe to assume that what version of kOS are you running?

Reserving action groups for use with KOS would be a support nightmare. You can already read the state of action groups to see when they have been pressed.

No current plans but it isnt a bad idea. It would enable menus and all kinds of fun stuff

Fixed, thanks.

I approve of this as a start. maybe allow midi's later

Nope. I have seen this request a few times now, what were you thinking about doing with them?

My bad i missed it, Added! Would you like me to include a link to some docs? i can push the changes you made live if you like?

I actually want to encourage more use of the antenna's long term. I would like there to be the same requirements for sending science as sending code or messages back to the terminal, esp power usage. My ideal would be to have remote tech help with networks and speed of light propagation.

New pre-release v0.12.P3 https://github.com/KSP-KOS/KOS/releases/tag/v12.0P3 new part, and bug fixes.