We've just uploaded a new update: v1.1.51! This should resolve the issue for both Mac and Linux users (this issue didn't affect the Windows build). Please let us know if you still experience any problems. We've also set up the "Old_Build" branch to run v1.1.4, so if you still have issues, try that build instead and let us know if that works for you. To switch branch, go to the "Betas" tab in the Steam settings. For those wanting to know what the issue was I'll try to explain it. We have a system that stores game progress such as stats, achievements and unlocks. This system used to write to an xml file (GameStats.xml) every time a stat changed (i.e. fuel was spent by driving on the world map). This caused some issues for Windows users with certain antivirus software. Every time the file was changed, the antivirus software would scan the file. This caused the game to be unable to access the file while it was being scanned. Normally this wasn't really a problem as the scanning process is usually very fast and the file would only be accessed about once per second, but on some hard- and software combinations the file would be inaccessible too long resulting in the game throwing a bunch of errors and all kinds of strange issues. To remedy this problem, we changed the frequency the file would be accessed. Now it is only accessed whenever the game is saved, and all changes in between are stored in memory. This apparently introduced a new bug where on Mac and Linux systems the file would not be created if it didn't exist yet. It took us quite a while to figure out this was the issue since it only affected players who just bought the game. Due to the recent Steam sale, there has been quite an influx of new players so it makes sense that this bug suddenly came up a lot. We initially thought it might have been a driver or OS update that caused this, as all initial reporters had Macbook Pro models with an Intel Iris video chip. This theory was further supported when we tried to reproduce this issue and it was only reproducible on a new Macbook which of course had the Intel Iris chip. It was only when we received some decent error logs from you guys (thanks for that! <3 ) that we figured out what the actual issue was. Note: We've still got some mystery error logs that DO only seem to affect Mac users with Intel Iris chips. So if you still have issues with this new update, please let us know!

We've just uploaded a new update: v1.1.51! This should resolve the issue for both Mac and Linux users (this issue didn't affect the Windows build). Please let us know if you still experience any problems. We've also set up the "Old_Build" branch to run v1.1.4, so if you still have issues, try that build instead and let us know if that works for you. To switch branch, go to the "Betas" tab in the Steam settings. For those wanting to know what the issue was I'll try to explain it. We have a system that stores game progress such as stats, achievements and unlocks. This system used to write to an xml file (GameStats.xml) every time a stat changed (i.e. fuel was spent by driving on the world map). This caused some issues for Windows users with certain antivirus software. Every time the file was changed, the antivirus software would scan the file. This caused the game to be unable to access the file while it was being scanned. Normally this wasn't really a problem as the scanning process is usually very fast and the file would only be accessed about once per second, but on some hard- and software combinations the file would be inaccessible too long resulting in the game throwing a bunch of errors and all kinds of strange issues. To remedy this problem, we changed the frequency the file would be accessed. Now it is only accessed whenever the game is saved, and all changes in between are stored in memory. This apparently introduced a new bug where on Mac and Linux systems the file would not be created if it didn't exist yet. It took us quite a while to figure out this was the issue since it only affected players who just bought the game. Due to the recent Steam sale, there has been quite an influx of new players so it makes sense that this bug suddenly came up a lot. We initially thought it might have been a driver or OS update that caused this, as all initial reporters had Macbook Pro models with an Intel Iris video chip. This theory was further supported when we tried to reproduce this issue and it was only reproducible on a new Macbook which of course had the Intel Iris chip. It was only when we received some decent error logs from you guys (thanks for that! <3 ) that we figured out what the actual issue was. Note: We've still got some mystery error logs that DO only seem to affect Mac users with Intel Iris chips. So if you still have issues with this new update, please let us know!