0

Loads of new stuff in KSA since my previous post. I'll defer to ShadowZone to show you how the game looks like right now

play · youtube.com
YouTube KSA's New Boosters Are Unlike Anything in Kerbal Space Program youtu.be
preview

I haven’t had much time to update myself on the state of ksaffairs, but the linked video should give you an idea.

Features implemented since my last post, off the top of my head, includes (but aren’t limited to):

  • Craft building
  • Collisions
  • Docking
  • modular BOOSTERS!
  • Official linux builds
  • Improved smoke/exhaust plumes

As before, the game is available for free at the official site. It is funded partially by donations, including from yours truly, in an effort towards making the game available to everyone and anyone. Any cent contributed to help this business model succeed is greatly appreciated by anyone involved.

Disclaimer: I am not affiliated with Rocketwerkz or KSA, but i can forward any feedback or issues people may have.

I haven’t had much time to update myself on the state of ksaffairs, but the linked video should give you an idea.

Features implemented since my last post, off the top of my head, includes (but aren’t limited to):

  • Craft building
  • Collisions
  • Docking
  • modular BOOSTERS!
  • Official linux builds
  • Improved smoke/exhaust plumes

As before, the game is available for free at the official site. It is funded partially by donations, including from yours truly, in an effort towards making the game available to everyone and anyone. Any cent contributed to help this business model succeed is greatly appreciated by anyone involved.

Disclaimer: I am not affiliated with Rocketwerkz or KSA, but i can forward any feedback or issues people may have.

0

Artemis II hype sees Kerbal Space Program beat all-time Steam player record 11 years after launch

GamesRadar+ Artemis II hype sees Kerbal Space Program beat all-time Steam player record 11 years after launch www.gamesradar.com
preview

The same definitely cannot be said for the sequel

The same definitely cannot be said for the sequel

0

KSA trialing Linux Builds

preview

From Dean Hall on Discord:

Apologies it has taken this long, but we are now trialing linux build deployments. These builds are deployed untested. I have changed <#1406840455093682258> to now split out preparing the builds and deploying them. The windows build will now refuse to deploy a build that fails digital signature. Both builds will now indicate if they have successfully be deployed or not. The master server MAY indicate an incorrect build for linux, if linux fails to deploy. This will be changed soon when I can update that side of the deployment process.

You can download the trial builds for linux directly at:
ksa-linux.ahwoo.com/[](https://…/)

Please consider contributing
It will increase our costs significantly to host this separate linux deployment. We are already spending x10 as much as we get in contributions - so it would make a great deal of help if folks who find the linux deployment useful consider contributing. If you do contribute - please do note in the contribution message if you can that it is FOR the linux deployments. I will use this data to help push that we should continue to integrate this going forward.

Report Linux issues
Discuss on the forums and in <#1438972207433912474>. We will try and be more active on the forums as, due to ‘recent stuff’ on discord, we understand this is not a perfect place for everyone. So feel free to post on the forums as well.

From Dean Hall on Discord:

Apologies it has taken this long, but we are now trialing linux build deployments. These builds are deployed untested. I have changed <#1406840455093682258> to now split out preparing the builds and deploying them. The windows build will now refuse to deploy a build that fails digital signature. Both builds will now indicate if they have successfully be deployed or not. The master server MAY indicate an incorrect build for linux, if linux fails to deploy. This will be changed soon when I can update that side of the deployment process.

You can download the trial builds for linux directly at:
ksa-linux.ahwoo.com/[](https://…/)

Please consider contributing
It will increase our costs significantly to host this separate linux deployment. We are already spending x10 as much as we get in contributions - so it would make a great deal of help if folks who find the linux deployment useful consider contributing. If you do contribute - please do note in the contribution message if you can that it is FOR the linux deployments. I will use this data to help push that we should continue to integrate this going forward.

Report Linux issues
Discuss on the forums and in <#1438972207433912474>. We will try and be more active on the forums as, due to ‘recent stuff’ on discord, we understand this is not a perfect place for everyone. So feel free to post on the forums as well.

0

First public build is out!

preview

Official announcement:

Pre-Alpha Public Release We have now moved from a closed pre-alpha to a public one. The build is now available for download from ksa.ahwoo.com. It is important to manage expectations, with the current build being certainly much more than a tech demo, but less than a game. This is expected as we have focused on establishing solid core fundamentals that will provide a safe scaffold to build all that we want to on top of this. It is this that you should see in the build.

ahwoo.com/…/019a8091-b519-7fd6-b0e8-cda461864d8b

Official download link: ksa.ahwoo.com (This is also where contributions can be made for those who wish to do so)

Mirror (HTTP)
Mirror (Torrent)

I won’t have time to test it myself for a while, so I’m happy to hear what you think and whether you manage to make it run on linux.

Official announcement:

Pre-Alpha Public Release We have now moved from a closed pre-alpha to a public one. The build is now available for download from ksa.ahwoo.com. It is important to manage expectations, with the current build being certainly much more than a tech demo, but less than a game. This is expected as we have focused on establishing solid core fundamentals that will provide a safe scaffold to build all that we want to on top of this. It is this that you should see in the build.

ahwoo.com/…/019a8091-b519-7fd6-b0e8-cda461864d8b

Official download link: ksa.ahwoo.com (This is also where contributions can be made for those who wish to do so)

Mirror (HTTP)
Mirror (Torrent)

I won’t have time to test it myself for a while, so I’m happy to hear what you think and whether you manage to make it run on linux.

0

Update on Public Build Timeline

preview

From Dean Hall on Discord:

tldr: No blockers identified, launch to proceed estimated in 19 hours

(Neidu’s comments: timezones and sleep schedule means that this means roughly… uh… I have NFI when. Discord timestamps are weird. Very soon, that’s for sure)

Sorry for the delay it has been a very busy time here at the studio. Our steering group went really well and while issues were identified, none are so far considered blockers to public availability of the launch. Some remaining work was identified but engineering was confident, so we gave them today to be sure. If this continues, that means at the end of this week. It is vital to note that it is ultimately our engineers who guide the decision on whether to release, there remains the chance that a significant blocker comes up and the public availability is delayed.

About the build
It is important now to discuss what the build is and set expectations. What you have been seeing in ⁠dev-updates updates and videos from content creators, is what you will be getting. We aren’t hiding things, or holding back stuff for marketing purposes. The current build is more than a tech demo but less than a game, deliberate as we have focused on the foundational technology to deliver the game to the future. What you can do is play around with this foundation, primarily controlling the loaded rockets and seeing how the orbital physics and basic collisions work. Only Sol is simulated currently, and you can never leave its SOI - this means if you do get further out than Sol’s SOI, you will see precision issues. A sample kitten in EVA is included. While basic modding is supported (and mods already exist!) the data structures are heavily in development so will change a lot, especially things like vehicles. All our internal debug tools are generally embedded in the game and are there for you to use (at your own risk) as well, such as part editing and such. The current system, Sol, is only for testing and will begin to be replaced with a custom designed one in the coming months.

We need you
The studio has found that our old ways of making and selling games just simply wasn’t working, and that if we didn’t try new ways we would end up as many other studios have. This project is the culmination of probably a decades worth of work building the studio. If you’re here, then you’re part of that journey now. We’ll provide some more details of how all this will shake out later - in the meantime a ‘save the date’ for in 19 hours. When it does go loud, we need you as a spokesperson not a sales person. You know the project, you’ll have the build - so you can make your own assessments about what the project has done, and where it is heading. Use that voice out there in the community with the project. If you can, and you feel the build meets expectations - contribute. Support content creators as much as you can as well. Developers, modders, content creators, and players will form what we hope is a “rebirth” of the spirit that Felipe bought with KSP. But in times like we are now it is so much harder, so we have nurture all parts of that.

A huge milestone
I am immensely proud and somewhat awed by what the team has pulled together. We have not only met, but exceeded even our stretch goals for what we wanted to have for the foundation of the project. This puts us in a very strong technical position to build up from here. More of this will be outlined when the public build goes live.

Known issues
We are tracking issues with older cards, especially AMD 5000 and 6000 series. Expect other weird edge case issues around GPUs and such. The technology we are using (BRUTAL) is brand new; and this is a huge ask for any engineering team to work through. Much of the work you would get for “free” with an engine is oriented to try solve a lot of these issues, and so we have to work through the various different platform and GPU idiosyncrasies. We also have not optimized our GPU handling, so cards that don’t have a lot of VRAM may run into issues. The settings default to the highest level, when you boot the game.

A note from me, some random dude on the internet who is not affiliated with the project:

  • Once the build becomes available to the public, I will of course provide the official download link. I also intend to mirror the download myself.
  • While Linux isn’t officially supported, various bits of pieces along the way has indicated that it is at least somewhat linux-friendly. I will make an effort into providing instructions for running the build on linux in case some hacking is required.
  • This is not a game. The devs are even hesitant when it comes to calling it a “playtest”. If you’re expecting a game and are afraid of disappointed, I suggest you sit this one out. Earlier comms have indicated that this is more akin to a tech demo with the intent of gathering as much bug reports and constructive feedback as possible on the overall engine and architecture. If you’re able to set aside any expectation of a fully fledget Kerbal Space Program replacement, and evaluate it for what it is, then go ahead and play around with it.

From Dean Hall on Discord:

tldr: No blockers identified, launch to proceed estimated in 19 hours

(Neidu’s comments: timezones and sleep schedule means that this means roughly… uh… I have NFI when. Discord timestamps are weird. Very soon, that’s for sure)

Sorry for the delay it has been a very busy time here at the studio. Our steering group went really well and while issues were identified, none are so far considered blockers to public availability of the launch. Some remaining work was identified but engineering was confident, so we gave them today to be sure. If this continues, that means at the end of this week. It is vital to note that it is ultimately our engineers who guide the decision on whether to release, there remains the chance that a significant blocker comes up and the public availability is delayed.

About the build
It is important now to discuss what the build is and set expectations. What you have been seeing in ⁠dev-updates updates and videos from content creators, is what you will be getting. We aren’t hiding things, or holding back stuff for marketing purposes. The current build is more than a tech demo but less than a game, deliberate as we have focused on the foundational technology to deliver the game to the future. What you can do is play around with this foundation, primarily controlling the loaded rockets and seeing how the orbital physics and basic collisions work. Only Sol is simulated currently, and you can never leave its SOI - this means if you do get further out than Sol’s SOI, you will see precision issues. A sample kitten in EVA is included. While basic modding is supported (and mods already exist!) the data structures are heavily in development so will change a lot, especially things like vehicles. All our internal debug tools are generally embedded in the game and are there for you to use (at your own risk) as well, such as part editing and such. The current system, Sol, is only for testing and will begin to be replaced with a custom designed one in the coming months.

We need you
The studio has found that our old ways of making and selling games just simply wasn’t working, and that if we didn’t try new ways we would end up as many other studios have. This project is the culmination of probably a decades worth of work building the studio. If you’re here, then you’re part of that journey now. We’ll provide some more details of how all this will shake out later - in the meantime a ‘save the date’ for in 19 hours. When it does go loud, we need you as a spokesperson not a sales person. You know the project, you’ll have the build - so you can make your own assessments about what the project has done, and where it is heading. Use that voice out there in the community with the project. If you can, and you feel the build meets expectations - contribute. Support content creators as much as you can as well. Developers, modders, content creators, and players will form what we hope is a “rebirth” of the spirit that Felipe bought with KSP. But in times like we are now it is so much harder, so we have nurture all parts of that.

A huge milestone
I am immensely proud and somewhat awed by what the team has pulled together. We have not only met, but exceeded even our stretch goals for what we wanted to have for the foundation of the project. This puts us in a very strong technical position to build up from here. More of this will be outlined when the public build goes live.

Known issues
We are tracking issues with older cards, especially AMD 5000 and 6000 series. Expect other weird edge case issues around GPUs and such. The technology we are using (BRUTAL) is brand new; and this is a huge ask for any engineering team to work through. Much of the work you would get for “free” with an engine is oriented to try solve a lot of these issues, and so we have to work through the various different platform and GPU idiosyncrasies. We also have not optimized our GPU handling, so cards that don’t have a lot of VRAM may run into issues. The settings default to the highest level, when you boot the game.

A note from me, some random dude on the internet who is not affiliated with the project:

  • Once the build becomes available to the public, I will of course provide the official download link. I also intend to mirror the download myself.
  • While Linux isn’t officially supported, various bits of pieces along the way has indicated that it is at least somewhat linux-friendly. I will make an effort into providing instructions for running the build on linux in case some hacking is required.
  • This is not a game. The devs are even hesitant when it comes to calling it a “playtest”. If you’re expecting a game and are afraid of disappointed, I suggest you sit this one out. Earlier comms have indicated that this is more akin to a tech demo with the intent of gathering as much bug reports and constructive feedback as possible on the overall engine and architecture. If you’re able to set aside any expectation of a fully fledget Kerbal Space Program replacement, and evaluate it for what it is, then go ahead and play around with it.
0

Statement regarding imminent public build (TLDR: Maybe in a week)

preview

It was supposed to happen this week, but they decided to delay, maybe in one more week. Statement by Dean Hall:

Public Build and Contributions delayed again, review next week

The disappointment, especially for the Ahwoo team, is palpable. But its essentially the best reason for a delay: opportunity. We really want to get the Kitten pipeline into the first build and allow more time hardening startup crashes and input issues. We feel that the startup crashes and input issues can present some issues with achieving what we want in those first builds. Additionally, having the Kitten actually controllable in game in EVA, allows us to directly tackle one of the more challenging aspects of the project for people to wrap their heads around. The overall discussion from the team agrees the build is “fine” for an initial pre-alpha, but another week might well allow us to progress so much further.

I mentioned last week the project is somewhat a victim of its own success, and this is more evidence of that. We have the opportunity to push updated rendering and animation pipelines into the first build. In my opinion, the end result of this will do more than anything to convince people that we are making the right decisions with character compromises. I should stress this is not about getting the build perfect and there will be, obviously, a lot that is missing. It’s going to be very much a pre-alpha, and short of flying around missing all that we want such as vehicle building. But we are going to give the build another week. That does not mean, for certain, the build comes out next week. We will, again, review for “go or no-go” on Tuesday our time. If the answer is “go”, then it won’t come out immediately, it would be later that week.

The currently remaining priority work includes:

  • Kitten EVA in game
  • Investigation of crash-on-boot (especially certain AMD cards)
  • Fixing of input issues (selection of non-controlled vehicle orbits making burn node creation difficult/impossible for some vessels)
  • Default vessel will be old “Rocket”, with lunar aligned orbits

Secondary work may include:

  • DearIMGUI upgrade (might fix a variety of viewport issues, or enable future fixes)
  • Maybe some Jupiter cloud work (to be confirmed, unknown status)
  • Situation selection on boot menu
  • Additional optimization and bugfixing

It was supposed to happen this week, but they decided to delay, maybe in one more week. Statement by Dean Hall:

Public Build and Contributions delayed again, review next week

The disappointment, especially for the Ahwoo team, is palpable. But its essentially the best reason for a delay: opportunity. We really want to get the Kitten pipeline into the first build and allow more time hardening startup crashes and input issues. We feel that the startup crashes and input issues can present some issues with achieving what we want in those first builds. Additionally, having the Kitten actually controllable in game in EVA, allows us to directly tackle one of the more challenging aspects of the project for people to wrap their heads around. The overall discussion from the team agrees the build is “fine” for an initial pre-alpha, but another week might well allow us to progress so much further.

I mentioned last week the project is somewhat a victim of its own success, and this is more evidence of that. We have the opportunity to push updated rendering and animation pipelines into the first build. In my opinion, the end result of this will do more than anything to convince people that we are making the right decisions with character compromises. I should stress this is not about getting the build perfect and there will be, obviously, a lot that is missing. It’s going to be very much a pre-alpha, and short of flying around missing all that we want such as vehicle building. But we are going to give the build another week. That does not mean, for certain, the build comes out next week. We will, again, review for “go or no-go” on Tuesday our time. If the answer is “go”, then it won’t come out immediately, it would be later that week.

The currently remaining priority work includes:

  • Kitten EVA in game
  • Investigation of crash-on-boot (especially certain AMD cards)
  • Fixing of input issues (selection of non-controlled vehicle orbits making burn node creation difficult/impossible for some vessels)
  • Default vessel will be old “Rocket”, with lunar aligned orbits

Secondary work may include:

  • DearIMGUI upgrade (might fix a variety of viewport issues, or enable future fixes)
  • Maybe some Jupiter cloud work (to be confirmed, unknown status)
  • Situation selection on boot menu
  • Additional optimization and bugfixing
0

Matt Lowne playing the first semi-public build

play · youtube.com
YouTube PLAYING KITTEN SPACE AGENCY! - My Thoughts youtu.be
preview

Content creators got an early business ld for testing. While not confirmed, it is my expectation that the next test release will be public.

Content creators got an early business ld for testing. While not confirmed, it is my expectation that the next test release will be public.

0

Heightmap decal preview

preview

From Linx on Discord:

WIP preview of a ‘heightmap decal’ terrain modifier. This will give us the ability to create points of interest using hand-placed terrain detail in a desired location at a higher quality than the planet’s base height texture. It’s not ‘painting’ detail in (it’s more like slapping on a sticker!) but it could be used to create some interesting locations - the example here shows off the dynamics of the modifier

From Linx on Discord:

WIP preview of a ‘heightmap decal’ terrain modifier. This will give us the ability to create points of interest using hand-placed terrain detail in a desired location at a higher quality than the planet’s base height texture. It’s not ‘painting’ detail in (it’s more like slapping on a sticker!) but it could be used to create some interesting locations - the example here shows off the dynamics of the modifier

0

Water!

preview

From Blackrack on Discord:

Early water surface previews. We’re currently putting in place the foundation for the ocean system, these shots are using placeholder gerstner waves which can be used to test the shading/geometry and integration with the other systems. Later on the waves will be replaced with a more realistic system.

From Blackrack on Discord:

Early water surface previews. We’re currently putting in place the foundation for the ocean system, these shots are using placeholder gerstner waves which can be used to test the shading/geometry and integration with the other systems. Later on the waves will be replaced with a more realistic system.

0

Martian dust storm showcase

preview

Posted by Blackrack on Discord.

1

2

Another showcase of the dust storm’s front, these are currently exaggerated in scale but can be toned down as needed:
3

Posted by Blackrack on Discord.

1

2

Another showcase of the dust storm’s front, these are currently exaggerated in scale but can be toned down as needed:
3

0

Full orbit/ground tracking overview with sun/daylight indicator

preview

…which allows for some nice plots when you’re at semi-synchronous orbits. Can’t wait to position site survey (spy) satellites this way:

Bright green is current orbit. Darker and more faded greens for subsequent orbits.

…which allows for some nice plots when you’re at semi-synchronous orbits. Can’t wait to position site survey (spy) satellites this way:

Bright green is current orbit. Darker and more faded greens for subsequent orbits.

0

An early look at the autopilot control panel

preview

From Gravhoek on Discord:

Here’s a quick look at my most recent pass on the autopilot control panel. I’m already planning on making a few more changes in the next few days (specifically around burn execution), but you can see what’s been done so far. This will also get a pass from Dean and his fancy new UI.

From Gravhoek on Discord:

Here’s a quick look at my most recent pass on the autopilot control panel. I’m already planning on making a few more changes in the next few days (specifically around burn execution), but you can see what’s been done so far. This will also get a pass from Dean and his fancy new UI.

0

Playing around with heigtmaps

preview

From Linx on Discord:

A quick look at the detail heightmaps in action and how fast it is to make edits to the terrain. It’s pretty satisfying to see the textures update to reflect the new context of the terrain. I spent longer than I should have playing around with this!

Detail heightmaps are per-biome so planets won’t have the same one everywhere. Due to their tiling/repeating nature they won’t be used in places where that becomes obvious; I’m thinking they’ll be applied to slopes or cliffs to add some extra detail to stop them from looking lumpy. I’m also going to be looking into procedural elements! Procedural noise is great for adding non-repeating detail that also isn’t limited by the resolution of a texture, but requires a lot of care so that different locations don’t look “samey”. The planets will still be mostly driven by heightmaps, but closer to the surface where the heightmap resolution becomes too low is where procedural elements shine - KSP uses this. Not sure how far down that rabbit hole we’ll go as I’ve only recently started looking into it, but it’s something I’m interested in.

I leave you with a fun fact: Minmus in KSP is entirely procedural. If you change the seed using a mod you get an entirely new version of the minty moon 😉

From Linx on Discord:

A quick look at the detail heightmaps in action and how fast it is to make edits to the terrain. It’s pretty satisfying to see the textures update to reflect the new context of the terrain. I spent longer than I should have playing around with this!

Detail heightmaps are per-biome so planets won’t have the same one everywhere. Due to their tiling/repeating nature they won’t be used in places where that becomes obvious; I’m thinking they’ll be applied to slopes or cliffs to add some extra detail to stop them from looking lumpy. I’m also going to be looking into procedural elements! Procedural noise is great for adding non-repeating detail that also isn’t limited by the resolution of a texture, but requires a lot of care so that different locations don’t look “samey”. The planets will still be mostly driven by heightmaps, but closer to the surface where the heightmap resolution becomes too low is where procedural elements shine - KSP uses this. Not sure how far down that rabbit hole we’ll go as I’ve only recently started looking into it, but it’s something I’m interested in.

I leave you with a fun fact: Minmus in KSP is entirely procedural. If you change the seed using a mod you get an entirely new version of the minty moon 😉

0

Gravhoek explains how the RCS works from a technical perspective

preview

From Gravhoek on Discord:

For anyone interested in how RCS control works internally, I thought I would post a couple shots of its “brain” during a maneuver.

If you have some familiarity with how automatic controls work you’ve probably heard of PID - that’s not how this controller works. The problem with PID is that it doesn’t handle actuators (RCS jets, in our case) that have a “minimum impulse” very well. That is, you can’t fire an RCS thruster for an infinitely small amount of time. In practice, this means every correction you make is always at least a slight overcorrection, which means you’re going to have to accept a bit of “wobble” around your target.

To handle this without constantly firing back and forth and wasting fuel, you need what’s called a “dead band” where you just coast and allow your pointing angle to drift away from your target angle a little bit. Then, when you get too far away, you make a small correction and drift back the other way. When you end up in this pulse-drift-pulse cycle around your target and the pulses are minimum pulses (meaning the smallest possible RCS firing time), this is called a “limit cycle”, which we will see in this graph.

The graphs here display something called “phase space”, which is a general term in control theory. For our purposes, it is a graph of two errors - error being the distance from your target state to your current state. The two errors we care about for each axis are angular error (the X axis) and angular rate error (the Y axis). Basically, how far you are from the target and how fast you are going relative to the target.

The big red dot on the graph is your current location in phase space. The lines on the graph are called switching lines - hence why this is called a “switching line controller”. If you are below the lines, it means you need to increase your angular rate. If you are above the lines, it means you need to decrease your angular rate. Between the lines is the “dead band”, where all thrusters are off. You can see the lines converge towards zero rate and zero angle at the center, which is why this controller guides the spacecraft to its pointing target.

The three images here show a complete maneuver.

  1. The initial angle offset where the red dots are far outside the lines.
  2. Mid maneuver where the red dots are inside the lines but we are rotating around towards the target. This is the coast phase where we are spinning but there are no thrusters firing.
  3. The “on target” phase where errors are close to zero.

Once you get close to the origin (zero rate, zero angle), the shape of the lines change into the squarish structure you can see on the zoomed picture. Here you can see several things more clearly:

  1. The yellow lines are the switching lines described before.
  2. The green line is the target line - when you are outside the switching line, you try and fire thrusters to hit this target line.
  3. The gray box shows the expected “limit cycle” - the path you expect to take if the spacecraft is doing the least amount of work possible to keep the target within the dead band.

In the video you can see what the limit cycle looks like in practice. Note that the thruster firings in pitch and yaw are slightly coupled (e.g. firing in yaw causes a small change to pitch rate). This is because the thruster pods on the Apollo CSM are slightly rotated around the vehicle, so e.g. the “yaw” thrusters are actually “mostly yaw and a little bit of pitch” thrusters.

Deadband Initial

Deadband Transition

Deadband Steady

Note: The referenced video doesn’t want to embed. You can see it here.

From Gravhoek on Discord:

For anyone interested in how RCS control works internally, I thought I would post a couple shots of its “brain” during a maneuver.

If you have some familiarity with how automatic controls work you’ve probably heard of PID - that’s not how this controller works. The problem with PID is that it doesn’t handle actuators (RCS jets, in our case) that have a “minimum impulse” very well. That is, you can’t fire an RCS thruster for an infinitely small amount of time. In practice, this means every correction you make is always at least a slight overcorrection, which means you’re going to have to accept a bit of “wobble” around your target.

To handle this without constantly firing back and forth and wasting fuel, you need what’s called a “dead band” where you just coast and allow your pointing angle to drift away from your target angle a little bit. Then, when you get too far away, you make a small correction and drift back the other way. When you end up in this pulse-drift-pulse cycle around your target and the pulses are minimum pulses (meaning the smallest possible RCS firing time), this is called a “limit cycle”, which we will see in this graph.

The graphs here display something called “phase space”, which is a general term in control theory. For our purposes, it is a graph of two errors - error being the distance from your target state to your current state. The two errors we care about for each axis are angular error (the X axis) and angular rate error (the Y axis). Basically, how far you are from the target and how fast you are going relative to the target.

The big red dot on the graph is your current location in phase space. The lines on the graph are called switching lines - hence why this is called a “switching line controller”. If you are below the lines, it means you need to increase your angular rate. If you are above the lines, it means you need to decrease your angular rate. Between the lines is the “dead band”, where all thrusters are off. You can see the lines converge towards zero rate and zero angle at the center, which is why this controller guides the spacecraft to its pointing target.

The three images here show a complete maneuver.

  1. The initial angle offset where the red dots are far outside the lines.
  2. Mid maneuver where the red dots are inside the lines but we are rotating around towards the target. This is the coast phase where we are spinning but there are no thrusters firing.
  3. The “on target” phase where errors are close to zero.

Once you get close to the origin (zero rate, zero angle), the shape of the lines change into the squarish structure you can see on the zoomed picture. Here you can see several things more clearly:

  1. The yellow lines are the switching lines described before.
  2. The green line is the target line - when you are outside the switching line, you try and fire thrusters to hit this target line.
  3. The gray box shows the expected “limit cycle” - the path you expect to take if the spacecraft is doing the least amount of work possible to keep the target within the dead band.

In the video you can see what the limit cycle looks like in practice. Note that the thruster firings in pitch and yaw are slightly coupled (e.g. firing in yaw causes a small change to pitch rate). This is because the thruster pods on the Apollo CSM are slightly rotated around the vehicle, so e.g. the “yaw” thrusters are actually “mostly yaw and a little bit of pitch” thrusters.

Deadband Initial

Deadband Transition

Deadband Steady

Note: The referenced video doesn’t want to embed. You can see it here.

0

"Solar Marathon", a.k.a. Gravhoek celebrating the flight computer attitude hold working as intended with RCS

preview

From Gravhoek on Discord:

Celebrating finally getting my RCS controller committed! Here is a “solar marathon” while holding a nose forward attitude using RCS.

From Gravhoek on Discord:

Celebrating finally getting my RCS controller committed! Here is a “solar marathon” while holding a nose forward attitude using RCS.

0

Atmospheric effects now take ozone into account

preview

From Blackrack on discord:

Atmosphere rendering improvements: Ozone and multiple scattering

As you’ve probably noticed in the last few videos, ozone is now supported. Unlike other atmospheric components, ozone only absorbs light (mainly green) instead of scattering it. This enhances the look of sunsets, as without ozone the atmosphere takes on a greenish hue.

The first screenshot compares a sunset without ozone on the left and with ozone on the right. The second screenshot shows the ozone layer from space which can be spotted as a distinct blue band, similar to this photo from the ISS.

Multiple scattering is also now implemented and can be seen on the third screenshot. It allows light to bounce several times in the atmosphere instead of just once. This can be subtle but helps with the realism of the atmosphere. It also works well with godrays, where objects block only the first light bounce, but the atmosphere can continue to receive light from the sky itself, softening the look of atmospheric shadows. The last screenshot shows a mountain casting a shadow on the atmosphere, with both ozone and multiple scattering, similar to this photo

Additional pictures:

.
. .

From Blackrack on discord:

Atmosphere rendering improvements: Ozone and multiple scattering

As you’ve probably noticed in the last few videos, ozone is now supported. Unlike other atmospheric components, ozone only absorbs light (mainly green) instead of scattering it. This enhances the look of sunsets, as without ozone the atmosphere takes on a greenish hue.

The first screenshot compares a sunset without ozone on the left and with ozone on the right. The second screenshot shows the ozone layer from space which can be spotted as a distinct blue band, similar to this photo from the ISS.

Multiple scattering is also now implemented and can be seen on the third screenshot. It allows light to bounce several times in the atmosphere instead of just once. This can be subtle but helps with the realism of the atmosphere. It also works well with godrays, where objects block only the first light bounce, but the atmosphere can continue to receive light from the sky itself, softening the look of atmospheric shadows. The last screenshot shows a mountain casting a shadow on the atmosphere, with both ozone and multiple scattering, similar to this photo

Additional pictures:

.
. .

0

RCS control at speed

preview

From Gravhoek on Discord:

Here’s what I’ve been working on since my aerobraking video ~1 week ago. This is our RCS attitude controller which can both null out rotation rates (detumble) and track pointing targets. Unlike in other space sims, our RCS thrusters have minimum firing times. This means spacecraft will use small pulses to steer themselves towards their targets, then “wobble” back and forth with the occasional thruster firing to keep themselves pointed in the same direction.

The extra special trick of KSA is this works at any time warp! In this video you can see the full timescale from 1x real time to 1 month/second of warp, with the controller holding its pointing targets and even transitioning between targets with perfect stability. No more sending your craft spinning into infinity if you time warp a bit too much!

When we eventually add reaction wheels and/or control moment gyros to the game, they will feel meaningfully different because they will be able to do very fine pointing without all the wobble (but won’t be nearly as powerful as RCS).

From Gravhoek on Discord:

Here’s what I’ve been working on since my aerobraking video ~1 week ago. This is our RCS attitude controller which can both null out rotation rates (detumble) and track pointing targets. Unlike in other space sims, our RCS thrusters have minimum firing times. This means spacecraft will use small pulses to steer themselves towards their targets, then “wobble” back and forth with the occasional thruster firing to keep themselves pointed in the same direction.

The extra special trick of KSA is this works at any time warp! In this video you can see the full timescale from 1x real time to 1 month/second of warp, with the controller holding its pointing targets and even transitioning between targets with perfect stability. No more sending your craft spinning into infinity if you time warp a bit too much!

When we eventually add reaction wheels and/or control moment gyros to the game, they will feel meaningfully different because they will be able to do very fine pointing without all the wobble (but won’t be nearly as powerful as RCS).

0

Blackrack showing off a Martian sunset

preview

From Blackrack via Discord:

A look at a blue sunset on Mars. More refinements will be made to the atmospheric scattering model to better reproduce Mars’s atmosphere. Unlike Earth’s sunsets, where Rayleigh scattering and wavelength-dependent extinction are responsible for the sunset color, Mars’s sunsets are controlled by a different mechanism where the scattering angle itself is what changes based on the wavelength.

All pictures from the post:

.

.

.

.

From Blackrack via Discord:

A look at a blue sunset on Mars. More refinements will be made to the atmospheric scattering model to better reproduce Mars’s atmosphere. Unlike Earth’s sunsets, where Rayleigh scattering and wavelength-dependent extinction are responsible for the sunset color, Mars’s sunsets are controlled by a different mechanism where the scattering angle itself is what changes based on the wavelength.

All pictures from the post:

.

.

.

.

0

24 Hours over Hawaii

preview

From Gravhoek on Discord:

While testing…other things, I captured this footage. This is 24 hours hanging over Hawaii (note that I turned clouds off so you can see the terrain better). I actually got into this orbit manually - even though it’s obvious that geosynchronous orbits would work in KSA, it’s still cool to see!

From Gravhoek on Discord:

While testing…other things, I captured this footage. This is 24 hours hanging over Hawaii (note that I turned clouds off so you can see the terrain better). I actually got into this orbit manually - even though it’s obvious that geosynchronous orbits would work in KSA, it’s still cool to see!

0

Relevant video from ShadowZone

play · youtube.com
YouTube 5 New Things in Kitten Space Agency (Progress Update) youtu.be
preview

It’s mostly stuff I’ve already covered in my posts, but I’d say it’s still worth a watch because:

  • He’s a generally good source of info, and a lot of t better at presenting objective facts than I ever will be.
  • Interest in his channel leads to interest in KSA, meaning (hopefully) more contributions to the game when it’s time for that.
  • There’s an interesting nugget of information about Nate Simpson
Tap for spoiler

of KSP2-fame (or infamy) (redacted due to coummunity rules)

…and what he’s been up to lately in there. I for one hope he succeeds, as I feel he got severely shafted by Take2.

It’s mostly stuff I’ve already covered in my posts, but I’d say it’s still worth a watch because:

  • He’s a generally good source of info, and a lot of t better at presenting objective facts than I ever will be.
  • Interest in his channel leads to interest in KSA, meaning (hopefully) more contributions to the game when it’s time for that.
  • There’s an interesting nugget of information about Nate Simpson
Tap for spoiler

of KSP2-fame (or infamy) (redacted due to coummunity rules)

…and what he’s been up to lately in there. I for one hope he succeeds, as I feel he got severely shafted by Take2.

0

Atmospheric drag during timewarp at 1 week/second

preview

From Gravhoek via discord:

Aerobraking passes at 1 week/second time warp. There is no trickery here - we are simulating all of the parts outside of the atmosphere with Kepler, and all of the parts inside the atmosphere with full physics.

We’ll see if it remains as efficient and flawless once they’ve implemented a more robust and realistic drag model instead of the current spherical placeholder.

From Gravhoek via discord:

Aerobraking passes at 1 week/second time warp. There is no trickery here - we are simulating all of the parts outside of the atmosphere with Kepler, and all of the parts inside the atmosphere with full physics.

We’ll see if it remains as efficient and flawless once they’ve implemented a more robust and realistic drag model instead of the current spherical placeholder.

0

Are you secretly funded by dogs?

preview

We have your plan figured out buddy, you are going to fill a spaceship with empty boxes and objects placed precariously close to edges, lure all of earth’s cats on and then send us to mars so dogs can rule earth.

Good luck herding us into the spaceship!

We have your plan figured out buddy, you are going to fill a spaceship with empty boxes and objects placed precariously close to edges, lure all of earth’s cats on and then send us to mars so dogs can rule earth.

Good luck herding us into the spaceship!

0

Testing a placeholder spherical drag model while falling through clouds

preview

Gravhoek on discord:

I added a simple spherical drag model to our humble CSM. Here we are falling through Blackracks beautiful clouds at terminal velocity.

Gravhoek on discord:

I added a simple spherical drag model to our humble CSM. Here we are falling through Blackracks beautiful clouds at terminal velocity.

0

Camera modes demo

preview

From Gravhoek on Discord:

Here are all the camera modes that are currently in the game. Each of them has their use, some more niche than others!

For those of you on mobile, the camera mode names can be a bit hard to see, but they are as follows, in order of appearance:

  • Parent
  • Stars
  • Chase
  • Surface
  • Orbit
  • (switched to map view, which seems to be a

From Gravhoek on Discord:

Here are all the camera modes that are currently in the game. Each of them has their use, some more niche than others!

For those of you on mobile, the camera mode names can be a bit hard to see, but they are as follows, in order of appearance:

  • Parent
  • Stars
  • Chase
  • Surface
  • Orbit
  • (switched to map view, which seems to be a
0

Looks like a placeholder "landing" mechanism is in place.

preview

Source: gitbot

gravhoek-rw

+ Added the ability for vehicles to collide with and rest on planetary surfaces. This is a very simple version to start which treats the vehicle as an analytic sphere and only collides directly in the radial direction. It also does not take the surface normal into account at the moment.
+ Added a symplectic Euler integrator which we use to resolve collision along with a scheme of sequential impulses.
* Major rework to vehicle state and update logic. We can now choose multiple different update methods within a single frame - for example, taking a Kepler step to the edge of the atmosphere, integrating with velocity Verlet to the surface, and resolving and impact with symplectic Euler.
* Added a minimum target framerate to prevent the FPS "death spiral" when there is too much work to get done in a single frame, so the target frame time increases exponentially each time. We will now scale back the time compression rate to try and fit within a reasonable frame rate.
+ Added a new Simulation tab to the game settings for various physics parameters.
* Adjusted celestial creation to be a full preorder traversal, meaning each celestial is fully baked before its children are instantiated.
* Lowered the minimum camera altitude to 0.5 meters.
+ Added some float3 extension methods and renamed DoubleVectorEx to Double3Ex.
+ Added a physics debug window.
* Changed the patched conics parent impact detector to use a direct calculation rather than a bisect search.
* Fixed attitude snapping using the wrong coordinate frame rates.
+ Fixed debug thruster arrows being drawn in the wrong location.
+ Added LC-39A to Earth landmarks.

Source: gitbot

gravhoek-rw

+ Added the ability for vehicles to collide with and rest on planetary surfaces. This is a very simple version to start which treats the vehicle as an analytic sphere and only collides directly in the radial direction. It also does not take the surface normal into account at the moment.
+ Added a symplectic Euler integrator which we use to resolve collision along with a scheme of sequential impulses.
* Major rework to vehicle state and update logic. We can now choose multiple different update methods within a single frame - for example, taking a Kepler step to the edge of the atmosphere, integrating with velocity Verlet to the surface, and resolving and impact with symplectic Euler.
* Added a minimum target framerate to prevent the FPS "death spiral" when there is too much work to get done in a single frame, so the target frame time increases exponentially each time. We will now scale back the time compression rate to try and fit within a reasonable frame rate.
+ Added a new Simulation tab to the game settings for various physics parameters.
* Adjusted celestial creation to be a full preorder traversal, meaning each celestial is fully baked before its children are instantiated.
* Lowered the minimum camera altitude to 0.5 meters.
+ Added some float3 extension methods and renamed DoubleVectorEx to Double3Ex.
+ Added a physics debug window.
* Changed the patched conics parent impact detector to use a direct calculation rather than a bisect search.
* Fixed attitude snapping using the wrong coordinate frame rates.
+ Fixed debug thruster arrows being drawn in the wrong location.
+ Added LC-39A to Earth landmarks.
0

Latest progress with procedural gauges

preview

From Dean Hall on Discord:

You can see the SDF font gauge is working great and there is almost no aliasing whether the gauge is large or small. Might be hard to wrap your head around, but in drawing these gauges no mesh or texture* is involved at all. (technically, a texture is used for the SDF font but not in a traditional texture sense). This has a lot of benefits I covered earlier. You can see animated mechanical rollers for representing numbers in this demonstration as well. These gauges are generated entirely from runtime “mod data” meaning the way we make them is the same way modders do. The shader itself is able to access a global shader binding that is very efficient when it comes to transfering data. Individual shaders/gauges don’t need special bindings for data, they have access to all the data. Allowing gauges of incredible complexity, for only the per-pixel cost of the shader itself.

From Dean Hall on Discord:

You can see the SDF font gauge is working great and there is almost no aliasing whether the gauge is large or small. Might be hard to wrap your head around, but in drawing these gauges no mesh or texture* is involved at all. (technically, a texture is used for the SDF font but not in a traditional texture sense). This has a lot of benefits I covered earlier. You can see animated mechanical rollers for representing numbers in this demonstration as well. These gauges are generated entirely from runtime “mod data” meaning the way we make them is the same way modders do. The shader itself is able to access a global shader binding that is very efficient when it comes to transfering data. Individual shaders/gauges don’t need special bindings for data, they have access to all the data. Allowing gauges of incredible complexity, for only the per-pixel cost of the shader itself.

0

Undocking Windows / Multi Window Rendering demo

preview

From Dean Hall on Discord:

This shows the early progress on multiwindow rendering, showing me “undock” the settings menu seamlessly. When the settings window is dragged outside of the main viewport, a new application window gets created. This has tremendous use for many situations, especially so when rendering different cameras such as when doing interplanetary transfers. Hopefully this video gives a good indication to people the power of this functionality.

From Dean Hall on Discord:

This shows the early progress on multiwindow rendering, showing me “undock” the settings menu seamlessly. When the settings window is dragged outside of the main viewport, a new application window gets created. This has tremendous use for many situations, especially so when rendering different cameras such as when doing interplanetary transfers. Hopefully this video gives a good indication to people the power of this functionality.

0

Latest Demonstration of progress with terrain (Spherical Billboarding)

preview

From Dean Hall on discord:

A lot of progress has been made improving a lot of our rendering process for many things, and terrain is one of them. This video shows off progress that has been made, with a great demostration of the seamlessness we now have with spherical billboarding. It is important to remember this video is taken live, realtime, from within the simulation at realistic scales (although the height of lunar features is exagerated for testing).

This video on discord is at 30FPS and and HD only, for a 60FPS and full HD download at: drive.google.com/file/d/…/view?usp=drive_link

(content creators welcome to use as always. attribution is not required)

HD version mirrored here

From Dean Hall on discord:

A lot of progress has been made improving a lot of our rendering process for many things, and terrain is one of them. This video shows off progress that has been made, with a great demostration of the seamlessness we now have with spherical billboarding. It is important to remember this video is taken live, realtime, from within the simulation at realistic scales (although the height of lunar features is exagerated for testing).

This video on discord is at 30FPS and and HD only, for a 60FPS and full HD download at: drive.google.com/file/d/…/view?usp=drive_link

(content creators welcome to use as always. attribution is not required)

HD version mirrored here

0

Experimenting with a highly customizable UI (screenshots and examples inside)

preview

From Dean Hall, playing around with navball config:

This new system allows you to write fragment shaders to “draw” widgets on the screen. All you need to do is write it in XML:

        <Gauge>
            <Component Id="Navball">
                <AnchorUv X="0" Y="1" />
                <PivotUv X="0.5" Y="0.5" />
                <SizePixels X="256" Y="256" />
                <OffsetPixels X="240" Y="-200" />
                <Rotation Degrees="0" />
            </Component>
            <Component Id="TBar">
                <AnchorUv X="0" Y="1" />
                <PivotUv X="0.5" Y="0.5" />
                <SizePixels X="48" Y="48" />
                <OffsetPixels X="240" Y="-200" />
                <!--<Rotation Degrees="45" />--> <!-- would need to use GaugeRotVert to use this -->
            </Component>
        </Gauge>

and these reference defined “GaugeComponents” can get reused:

<Assets>
    <GaugeComponent Id="Navball">
        <Vertex Id="GaugeVert"/>
        <Fragment Path="Shaders/Navball.frag"/>
        <Gauge Id="Fragment"/>
    </GaugeComponent>
    <GaugeComponent Id="TBar">
        <Vertex Id="GaugeVert"/>
        <Fragment Path="Shaders/GaugeTBar.frag"/>
    </GaugeComponent>
</Assets>

which this means is you can write fragment shaders (as an option) to make UI elements. THis is good, but also a little dangerous. If they are small - they are really chheap. but the bigger they get, the more expensive they are
In thiis screenshot i’ve “unlocked” them so you can see the borders

with this unlocked, I can customize it live, which helps me choose the values to put in the XML

you can resize manually, but in that slider is useful for more precise changes around the pixel etc…

Adjustments seem really fast and simple, both sensible tweaks, and not so sensible ones:

From Dean Hall, playing around with navball config:

This new system allows you to write fragment shaders to “draw” widgets on the screen. All you need to do is write it in XML:

        <Gauge>
            <Component Id="Navball">
                <AnchorUv X="0" Y="1" />
                <PivotUv X="0.5" Y="0.5" />
                <SizePixels X="256" Y="256" />
                <OffsetPixels X="240" Y="-200" />
                <Rotation Degrees="0" />
            </Component>
            <Component Id="TBar">
                <AnchorUv X="0" Y="1" />
                <PivotUv X="0.5" Y="0.5" />
                <SizePixels X="48" Y="48" />
                <OffsetPixels X="240" Y="-200" />
                <!--<Rotation Degrees="45" />--> <!-- would need to use GaugeRotVert to use this -->
            </Component>
        </Gauge>

and these reference defined “GaugeComponents” can get reused:

<Assets>
    <GaugeComponent Id="Navball">
        <Vertex Id="GaugeVert"/>
        <Fragment Path="Shaders/Navball.frag"/>
        <Gauge Id="Fragment"/>
    </GaugeComponent>
    <GaugeComponent Id="TBar">
        <Vertex Id="GaugeVert"/>
        <Fragment Path="Shaders/GaugeTBar.frag"/>
    </GaugeComponent>
</Assets>

which this means is you can write fragment shaders (as an option) to make UI elements. THis is good, but also a little dangerous. If they are small - they are really chheap. but the bigger they get, the more expensive they are
In thiis screenshot i’ve “unlocked” them so you can see the borders

with this unlocked, I can customize it live, which helps me choose the values to put in the XML

you can resize manually, but in that slider is useful for more precise changes around the pixel etc…

Adjustments seem really fast and simple, both sensible tweaks, and not so sensible ones:

0

30ish min youtube video with "gameplay". Recorded from Discord, but sadly without audio.

play · youtube.com
YouTube Gameplay (no audio) Kitten Space Agency 2025.5.11.1304-LOCAL youtu.be
preview

Keep in mind that this is an extremely early state of the game as it’s pre-alpha. It’s more akin to a tech demo at this stage.

Keep in mind that this is an extremely early state of the game as it’s pre-alpha. It’s more akin to a tech demo at this stage.

0

Procedural Navball Demo

preview

From Dean Hall:

So I’ve been working on moving away from always using meshes and textures for things like navballs, and doing it procedurally - in this case in a fragment shader alone. Why do this? Well, that’s actually a good question. Not one I have a great answer to. Primarily, it started (like much in this project) because I personally don’t like the way games look today. Everything is all washed out the heck, its all like someone has spread petroleum jelly over the screen (shakes fist at Tim Sweeney angrily). Bizarely, my time making a lot of complex avionics for my Stormworks vehicles also factored in this.

“What if”, I reasoned, “we could make it completely in the fragment”? Not only will it scale really well to any resolution - the nav ball will never have texture “pinching” at the poles, and modders could very easily replace any widget whenver they want with extreme ease. An added bonus you can see in this video, I can move the widget around very easily. To be fair, this would be true (to an extent) for a mesh + texture combo - but you can see it starts to look really great even when I scale it up. This has actually been a good example for me of the paradigm shift we face using BRUTAL. A lot of things get approached from first principles, which means you start asking all kinds of really weird questions and you end up asking what should i do?.

So whats the catch? Well, another really good question. I’m not a graphics programmer, but I’m tempted to say that this procedural shader willl always be less performant than doing it with a mesh + texture combo. However, whether you will notice the performance hit remains to be seen. This is because the entirety of drawing the procedural navball is drawn in the “fragment” shader, with essentially nothing at all from the CPU. No texture, no mesh (well, I do tell the GPU there is a quad - but it doesn’t exist, it is just used to make sure the fragment gets called). This has all been quite a ramble.

If I do end up continuing down this path successfully, I can make a lot of widgets like this, which can then be used for IVA gauges and the like, and then rendered on a separate framerate.

From Dean Hall:

So I’ve been working on moving away from always using meshes and textures for things like navballs, and doing it procedurally - in this case in a fragment shader alone. Why do this? Well, that’s actually a good question. Not one I have a great answer to. Primarily, it started (like much in this project) because I personally don’t like the way games look today. Everything is all washed out the heck, its all like someone has spread petroleum jelly over the screen (shakes fist at Tim Sweeney angrily). Bizarely, my time making a lot of complex avionics for my Stormworks vehicles also factored in this.

“What if”, I reasoned, “we could make it completely in the fragment”? Not only will it scale really well to any resolution - the nav ball will never have texture “pinching” at the poles, and modders could very easily replace any widget whenver they want with extreme ease. An added bonus you can see in this video, I can move the widget around very easily. To be fair, this would be true (to an extent) for a mesh + texture combo - but you can see it starts to look really great even when I scale it up. This has actually been a good example for me of the paradigm shift we face using BRUTAL. A lot of things get approached from first principles, which means you start asking all kinds of really weird questions and you end up asking what should i do?.

So whats the catch? Well, another really good question. I’m not a graphics programmer, but I’m tempted to say that this procedural shader willl always be less performant than doing it with a mesh + texture combo. However, whether you will notice the performance hit remains to be seen. This is because the entirety of drawing the procedural navball is drawn in the “fragment” shader, with essentially nothing at all from the CPU. No texture, no mesh (well, I do tell the GPU there is a quad - but it doesn’t exist, it is just used to make sure the fragment gets called). This has all been quite a ramble.

If I do end up continuing down this path successfully, I can make a lot of widgets like this, which can then be used for IVA gauges and the like, and then rendered on a separate framerate.