In this BETA patch we see a continuation of the saving and loading mechanics introduced in 5.3, one handy item is the 'emergency save' feature which will automatically save your game if there is a crash.

Otherwise we continue the combat mechanics focus of Update 5 in general preparing to switch on unit veterancy and experience, and adding in idle shield recharge when not in combat.

In addition there are a bunch of fixes and tweaks as suggested by the community - keep them coming!

• Added emergency save-game on crash
  
• Added Officer/experience framework
  
• Added ranks to sample ships
  
• Added shield recharge when ship out of combat for 45 seconds
  
• Added shield recharge rolling HUD text
  
• Added ship tooltip to targetbox, and tactical and fleet icons
  
• Added save message to notification panel
  
  
• Fixed crash on ship UI animation
  
• Fixed issue with fleet icons not appearing for sighted enemy
  
• Fixed Space Object text no longer affected by time scaling
  
• Fixed issues clearing down refinery dialog options
  
• Fixed crash switching zones if mouseover Space Object
  
• Fixed correct behavior on ESC press when save/load window shown
  
  
• Updated Space Object tooltips

Note this patch is currently in BETA, but you can access it if you own the game:

1. Right click on the game in your Steam library
   
2. Select 'Properties'
   
3. Select 'BETAS' tab
   
4. Select 'testing - Overhaul Beta' from the list

BETA patches are only available on Windows and Linux.

In this BETA patch we see a continuation of the saving and loading mechanics introduced in 5.3, one handy item is the 'emergency save' feature which will automatically save your game if there is a crash.

Otherwise we continue the combat mechanics focus of Update 5 in general preparing to switch on unit veterancy and experience, and adding in idle shield recharge when not in combat.

In addition there are a bunch of fixes and tweaks as suggested by the community - keep them coming!

• Added emergency save-game on crash
  
• Added Officer/experience framework
  
• Added ranks to sample ships
  
• Added shield recharge when ship out of combat for 45 seconds
  
• Added shield recharge rolling HUD text
  
• Added ship tooltip to targetbox, and tactical and fleet icons
  
• Added save message to notification panel
  
  
• Fixed crash on ship UI animation
  
• Fixed issue with fleet icons not appearing for sighted enemy
  
• Fixed Space Object text no longer affected by time scaling
  
• Fixed issues clearing down refinery dialog options
  
• Fixed crash switching zones if mouseover Space Object
  
• Fixed correct behavior on ESC press when save/load window shown
  
  
• Updated Space Object tooltips

Note this patch is currently in BETA, but you can access it if you own the game:

1. Right click on the game in your Steam library
   
2. Select 'Properties'
   
3. Select 'BETAS' tab
   
4. Select 'testing - Overhaul Beta' from the list

BETA patches are only available on Windows and Linux.

As mentioned, a new beta branch has been opened up. The purpose of the BETA is to ensure that updates are more thoroughly testing before they hit the public domain, more information about this here.

To get to the BETA:

1. Right click on the game in your Steam library
   
2. Select 'Properties'
   
3. Select 'BETAS' tab
   
4. Select 'testing - Overhaul Beta' from the list

Note that the BETA is only available on Windows and Linux.

Saved games will be transferable but you'll need to fish them out of the 'SavedGames' folder in the main game folder in your Steam library (soon we'll enable Steams 'Cloud Save' which will hopefully do this for us.)


- Added save/load buttons to menu
- Added save game window (New, Replace, Delete)
- Added load game window (Load, Delete)
- Added most recent save selected ready to go
- Added F5 quick save game
- Fixed crash closing petty trade window after cancelled trade
- Fixed crash using ability if context target is destroyed

As mentioned, a new beta branch has been opened up. The purpose of the BETA is to ensure that updates are more thoroughly testing before they hit the public domain, more information about this here.

To get to the BETA:

1. Right click on the game in your Steam library
   
2. Select 'Properties'
   
3. Select 'BETAS' tab
   
4. Select 'testing - Overhaul Beta' from the list

Note that the BETA is only available on Windows and Linux.

Saved games will be transferable but you'll need to fish them out of the 'SavedGames' folder in the main game folder in your Steam library (soon we'll enable Steams 'Cloud Save' which will hopefully do this for us.)


- Added save/load buttons to menu
- Added save game window (New, Replace, Delete)
- Added load game window (Load, Delete)
- Added most recent save selected ready to go
- Added F5 quick save game
- Fixed crash closing petty trade window after cancelled trade
- Fixed crash using ability if context target is destroyed

It’s that time again folks, but this time, rather than the mindless utterances of a dedicated developer – we’re going to directly discuss some of the feedback that’s coming in.


We do have in-game help listing controls with a basic explanation of some of the games mechanics (top-centre left, question mark button,) but it’s becoming increasingly apparent that there needs to be some degree of ‘show me’ style instruction to the game.

It’s been suggested that a video tutorial would suffice but experience tells us that these are too quickly rendered obsolete, so the tutorial needs to be in-game.

The problem is, as more mechanics are introduced, the tutorial will have to be continually rewritten to accommodate them leading to a duplication of effort.

Looking at the feedback now coming in, we now accept that we will have to concede to the request of the Players for a tutorial and have plans to include a modular tutorial that will grow as the games mechanics grow. To start with, the basic module might encompass fleet manoeuvres and management later including an intermediate module of resource collecting and trade.

In any case, you have spoken and we are listening – the tutorial is now a top priority.


I’d like to start off by saying that actually we have quite a slick bug reporting and resolving process here!

When the game crashes it tells you exactly what has happened and copies it to your clipboard. When we receive the crash report, either on the Steam forums or the Official game forums we are able to directly patch the issue and have a hotfix uploaded to all three platforms often within a day.

Let’s break down our rough 4 week development and release cycle:

• Week 1: Major update; new features – new bugs introduced
  
• Week 2 & 3: Incremental updates; Hotfixes and additional supporting features introduced – bugs get addressed
  
• Week 4: Update freeze – game is relatively stable

This really works from an internal development point of view; the project moves quickly, features are introduced and tested and from the feedback the bugs are squashed. To some degree this is an ideal reality of ‘bleeding edge’ alpha software.

The problem is, people are paying money for this and content aside - people rightly expect the alpha to be playable and with this current system sometimes it’s only stable for 50% of a cycle which is simply not good enough (though it should be considered that we are adding stuff during that 50%!)

So what’s the problem? Well to a degree we are pushing forward at a pace that doesn’t really allow for sufficient testing to be completed before the updates are released. Often, only the new stuff that is coded is tested but the new stuff is breaking the old stuff. Problems of this type are known as regression issues which is the price of our rapid progress.

We can’t slow the project down, there is too much to do. But the issues are annoying some Players and getting us out of bed at 2am to fix them isn’t much fun.

So how can we have our cake and eat it?

Well we need to ‘airlock’ the newest updates in another BETA branch in Steam.

Similar to how we managed the Open-world Overhaul when it was being updated in parallel with the old alpha, we’ll continue the fast pace and put it out of the way but still accessible to anyone that comes looking with instructions on the update articles. Once we’re sure the new stuff isn’t causing any problems we’ll then make it live.

This way the game is stable 100% of the time and we get to keep the rapid rate of progress. Ideal.

We’ll be opening up the BETA of Update 5.3 early next week and will post some instructions on gaining access.


A number of you have expressed strong desires to be able to save and load.

The reason why so far this has been omitted is because really the sandbox was only a small cross-section of what is to come. So far we have been focused on injecting mechanics into the alpha. But with the mechanics already in-game and those due to be added shortly, we are now far enough along to consider this a priority.

Saving/Loading will be part of Update 5.3 which will be in BETA early next week.

We really appreciate the positivity and support of the comments in previous posts, there is simply nothing more motivating than that.

Once again let me take the opportunity to thank-you for your patience, the bug reports you’re sending in are massively helpful please keep them coming and brace yourselves because great things are inbound!

James

It’s that time again folks, but this time, rather than the mindless utterances of a dedicated developer – we’re going to directly discuss some of the feedback that’s coming in.


We do have in-game help listing controls with a basic explanation of some of the games mechanics (top-centre left, question mark button,) but it’s becoming increasingly apparent that there needs to be some degree of ‘show me’ style instruction to the game.

It’s been suggested that a video tutorial would suffice but experience tells us that these are too quickly rendered obsolete, so the tutorial needs to be in-game.

The problem is, as more mechanics are introduced, the tutorial will have to be continually rewritten to accommodate them leading to a duplication of effort.

Looking at the feedback now coming in, we now accept that we will have to concede to the request of the Players for a tutorial and have plans to include a modular tutorial that will grow as the games mechanics grow. To start with, the basic module might encompass fleet manoeuvres and management later including an intermediate module of resource collecting and trade.

In any case, you have spoken and we are listening – the tutorial is now a top priority.


I’d like to start off by saying that actually we have quite a slick bug reporting and resolving process here!

When the game crashes it tells you exactly what has happened and copies it to your clipboard. When we receive the crash report, either on the Steam forums or the Official game forums we are able to directly patch the issue and have a hotfix uploaded to all three platforms often within a day.

Let’s break down our rough 4 week development and release cycle:

• Week 1: Major update; new features – new bugs introduced
  
• Week 2 & 3: Incremental updates; Hotfixes and additional supporting features introduced – bugs get addressed
  
• Week 4: Update freeze – game is relatively stable

This really works from an internal development point of view; the project moves quickly, features are introduced and tested and from the feedback the bugs are squashed. To some degree this is an ideal reality of ‘bleeding edge’ alpha software.

The problem is, people are paying money for this and content aside - people rightly expect the alpha to be playable and with this current system sometimes it’s only stable for 50% of a cycle which is simply not good enough (though it should be considered that we are adding stuff during that 50%!)

So what’s the problem? Well to a degree we are pushing forward at a pace that doesn’t really allow for sufficient testing to be completed before the updates are released. Often, only the new stuff that is coded is tested but the new stuff is breaking the old stuff. Problems of this type are known as regression issues which is the price of our rapid progress.

We can’t slow the project down, there is too much to do. But the issues are annoying some Players and getting us out of bed at 2am to fix them isn’t much fun.

So how can we have our cake and eat it?

Well we need to ‘airlock’ the newest updates in another BETA branch in Steam.

Similar to how we managed the Open-world Overhaul when it was being updated in parallel with the old alpha, we’ll continue the fast pace and put it out of the way but still accessible to anyone that comes looking with instructions on the update articles. Once we’re sure the new stuff isn’t causing any problems we’ll then make it live.

This way the game is stable 100% of the time and we get to keep the rapid rate of progress. Ideal.

We’ll be opening up the BETA of Update 5.3 early next week and will post some instructions on gaining access.


A number of you have expressed strong desires to be able to save and load.

The reason why so far this has been omitted is because really the sandbox was only a small cross-section of what is to come. So far we have been focused on injecting mechanics into the alpha. But with the mechanics already in-game and those due to be added shortly, we are now far enough along to consider this a priority.

Saving/Loading will be part of Update 5.3 which will be in BETA early next week.

We really appreciate the positivity and support of the comments in previous posts, there is simply nothing more motivating than that.

Once again let me take the opportunity to thank-you for your patience, the bug reports you’re sending in are massively helpful please keep them coming and brace yourselves because great things are inbound!

James

As promised another round of incremental updates to fix bugs introduced in 5.2 which was released last week.

A new BETA branch will shortly open up increasing the pace of the adding of new features and increasing overall stability by including a more regimented testing phase between the updates.

More details on this to follow.

Massive thanks to all those reporting the issues, please do keep those bug reports coming in!


- Fixes preventing player units from leaving playable area
- Fixes to range delimiting circle despawning
- Fixes to crash detecting mouseover text links


- Fixes to range delimiting circle despawning crash
- Fixes to double tapping camera focus when no fleet assigned


- Update transparency of various windows reduced
- Fixed selection issues after unit construction
- Fixed mission/context indicator visible for containers
- Fixed dialog/objective crash caused by save game prep
- Fixes to crash updating context panel buttons

As promised another round of incremental updates to fix bugs introduced in 5.2 which was released last week.

A new BETA branch will shortly open up increasing the pace of the adding of new features and increasing overall stability by including a more regimented testing phase between the updates.

More details on this to follow.

Massive thanks to all those reporting the issues, please do keep those bug reports coming in!


- Fixes preventing player units from leaving playable area
- Fixes to range delimiting circle despawning
- Fixes to crash detecting mouseover text links


- Fixes to range delimiting circle despawning crash
- Fixes to double tapping camera focus when no fleet assigned


- Update transparency of various windows reduced
- Fixed selection issues after unit construction
- Fixed mission/context indicator visible for containers
- Fixed dialog/objective crash caused by save game prep
- Fixes to crash updating context panel buttons

Good news, Update 5.2 is now available Commander!

Additional markings on the Battlegrid should aid perspective and understanding of the visible area.

The last week or so we have predominantly focused on hardening the codebase in preparation for Single Player campaign and Multiplayer - nothing exciting enough to talk about. But in addition, we've added some more useful markings to the Battlegrid; namely adjoining scanning circles for player/allied units and a range finder for the currently selected ship (or lead ship.)

Some very interesting feedback over on the Official forums as to what our priorities should be with 95% of voters saying they would enjoy MP but 80% of voters say that we should focus on the SP experience first. Who are we to argue with the Players?! So brace yourself for advancements in SP as we set our sights back on rolling in new content after another short round of bug fixes.

We expect to maintain a quick pace as we roll features, persistency and missions/encounters into the sandbox, but as mentioned, for the purposes of bug control, we'll likely open a separate Beta branch for the testing of the new SP features which will start to be introduced in 5.3 - more information on that to follow.

Cheers for the support and keep those bug reports coming in!


- Fixes further to stability
- Fixes to Ships sometimes spawning without weapons
- Fixes to Ship Builder UI appearance issue (post 5.4 upgrade)

- Added player/allied forces adjoining scanning circles
- Added Selected Ship 2D distance rulers

- Updated 'Jump Safe Area' markers

Good news, Update 5.2 is now available Commander!

Additional markings on the Battlegrid should aid perspective and understanding of the visible area.

The last week or so we have predominantly focused on hardening the codebase in preparation for Single Player campaign and Multiplayer - nothing exciting enough to talk about. But in addition, we've added some more useful markings to the Battlegrid; namely adjoining scanning circles for player/allied units and a range finder for the currently selected ship (or lead ship.)

Some very interesting feedback over on the Official forums as to what our priorities should be with 95% of voters saying they would enjoy MP but 80% of voters say that we should focus on the SP experience first. Who are we to argue with the Players?! So brace yourself for advancements in SP as we set our sights back on rolling in new content after another short round of bug fixes.

We expect to maintain a quick pace as we roll features, persistency and missions/encounters into the sandbox, but as mentioned, for the purposes of bug control, we'll likely open a separate Beta branch for the testing of the new SP features which will start to be introduced in 5.3 - more information on that to follow.

Cheers for the support and keep those bug reports coming in!


- Fixes further to stability
- Fixes to Ships sometimes spawning without weapons
- Fixes to Ship Builder UI appearance issue (post 5.4 upgrade)

- Added player/allied forces adjoining scanning circles
- Added Selected Ship 2D distance rulers

- Updated 'Jump Safe Area' markers