Stationeers Dev Tracker

The last few weeks we have worked closely with the community and server providers to improve on the work of our big refactor. A key focus was to get the old tutorials working, which we have. Expect changes to this in future. Additionally we have targeted some of the worst bugs and problems reported by the community and included these as fixes. We've also taken a first pass at improving some of the more confusing aspects of Stationeers, this week it is the save system.

Changes to save files

We have made important changes to save files. Now autosaves and manual saves will be grouped together, much like other games such as Oxygen Not Included. This work helps both make the game more intuitive and supports changes needed to better run servers

Please let us know if you have any issues. For now, there are some unusual restrictions such as you cannot name a save using "autosave" or "backup". This is temporary as we are making slow and... Read more

A lil somethin somethin: You can find the details for this event on the announcement page here.

A lil somethin somethin: You can find the details for this event on the announcement page here.

* Fixed Error Spam and Atmospheric Anomalies caused by a math error in the World atmosphere radiate heat function (which moves Temperatures of world atmospheres not in a room towards the global atmosphere Temperature)

A lil somethin somethin: You can find the details for this event on the announcement page here.

Cross learning and tech sharing between our projects brings you this update


Contrary to what has been incorrectly suggested in some reviews, the multi-team nature of our studio works towards better products, and this update is an excellent example of that. After technical review of our unreleased train tycoon game (Art of the Rail) by ICARUS technical team members, we embarked on a new approach to multi-threading for some core systems that took better advantage of multiple cores, and reduced thread concurrency dependency. What this means is we were able to squeeze better performance and reduce technical complexity (think: opportunity for really hard to fix bugs) at the same time.

We are really proud of how we have built a studio that has different teams, but are still able to share the lessons and grow better overall - and we h... Read more