erendrake

Sorry about that, I am back from vacation and i am ready to get a real release of kOS out. Thank you everyone for your testing and I would really love to see all of the bugs you find in the tracker so we can get them fixed!

Alright lets! I was thinking to start that I would just want a list of the available dishes and their: * range * power status * power consumption * their target craft/body No need to bite it all off at once. Once we get that going I would like to move on to pointing and toggling.

That is the plan. We have been a bit slow lately because we rewrote the parser but the plan is to let you enable/disable and point dishes.

Its a bit of an oversight, The Body and Vessel structures mention how to get their orbits but Orbit doesn't reciprocate Documenting this project is harder than others methinks

Do you have a block of code i can execute that triggers this? I have seen the same thing before in a stock save so i hope we can track this down and fix it. You might try looking at the map view, it might show something interesting

Just FYI there is a new Pre-release up. https://github.com/KSP-KOS/KOS/releases/tag/v12.0P2

Done! https://github.com/KSP-KOS/KOS/releases/tag/v12.0P2

once you have saved a file locally, you can COPY FOO TO ARCHIVE. where FOO is your new file. Edit: I didnt notice this was in the old thread, boo for thread necromancy!

if The normal steering assist doesnt behave like you want. you have direct access to the steering and you can turn it exactly like you would by hand. EDIT: By this i mean there is a flight control API for you to set the yaw/pitch/roll directly

Sorry im slow right now, All development is moving to the new Github organization, this weekend i have a big job of moving all of the links and such to the new one ill take a look at the SolidFuel problem, if you want to add it to the new tracker that would help.

Alright everyone, Buckle up. We have a pre-release of the new parser! https://github.com/KSP-KOS/KOS/releases/tag/v12.0P1 Please let us know if there are any troubles, as with any major rewrite there are bound to be some old bugs that are resolved and some new fun ones to discover, if you find a bug please speak up either here or in the new github tracker for the KOS organization https://github.com/KSP-KOS/KOS/issues A BIG shoutout to marianoapp on all of his excellent work over the last few weeks, he deserves all of your cookies. I have been incognito the last week with a bunch of life stuff but i have been reading everything and i know about the challenges people have been having with v11.1 and I hope we can get all of that ironed out soon

We could easily hook something like this up as a tweakable. so we could give each mission its own clock speed.

I think for now my inclination would be to spend more time adding features to make impossible tasks available (docking, science, integration with other mods). rather than spend a lot of time on more complicated scope/grammar. I like this discussion and I am hoping we can find the right solution.

Lets get this code out for a spin and see if speed is still an issue we need to worry about.

There is no argument about which codebase we will use, all of the performance gains of the new parser with all of the features of v0.11.1 is a no brainer It just comes down to who will be charged as "maintainer" and which name the project will use. I would release these bits as kOS v0.12 today and deal with whatever bugs we find but i would like to talk to marianoapp first to be sure that is ok. there is a ton of good work in here and i want to be respectful.

I am not interested in parallel projects when we can combine our efforts on one great mod. marianoapp and i need to have a meeting of the minds on which one (kOS or kRISC) will continue active development. I would be happy to continue as maintainer and i setup a Github Organization if we wanted to share admin on the project. @marianoapp would you like to have a skype/hangout discussion on this?

I would agree with you on pods like the Command Pod Mk1 where they are designed to be replicas of a part that never had a serious computer (mercury capsule). Once you make it to the Mk2 Lander Can Or the Mk 1-2 Command Pod I think they clearly have some kind of computer in them so i wouldnt mind giving them a KOS module. I do think that For very primitive pods I would like to see limits such as smaller memory, read-only memory and limited available sensors added. All of that is just a wish so far

I have a branch that displays the biome you are currently in and the biome you would be in if you were landed. I am trying to figure out a good Science API (gathering, reporting, storing, biomes) otherwise it would have been in 0.11.

Im really glad i didnt push 11.1 to the spaceport now I have my dad visiting from out of town so i have been mostly incognito the last few days and for the next few days as well. Ill have to see if i can figure out these problems and get a new version out soon. Thanks for your patience.

Cool! It makes a lot of sense to include it in the pods.

I underestimated how many mods you had you overflowed gist. would you just email that file to erendrake@gmail.com ?

That is what i was afraid of. I am actually just waiting for one of you to tell me that it is a huge pain and show me all of the crazy code it takes first if it turns out to be not a big deal i might just leave it as is.

in the root KSP folder there will be a KSP.log file. if you upload it to someplace like gist https://gist.github.com/ and link it in here. ill see if i can find the trouble.

Do you have a KSP log for me to look at? I cannot make this happen on my machine but we should try and fix it. do you have any other mods installed?

You can get the relative rotation now, the distance, and direction to the target. Im pretty sure you are talking about having the x/y/z meters to the docking port and im sure i will add them soon but for now you get to do a bit of trig to get them. Also i promised marianoapp i would stop adding features until we were able to bring in his amazing new parser.