Still far from ideal but glad to see movement so quickly from the dev team and as has been mentioned the game is certainly playable albeit with some setting tweaks.
You would think a little more time would be put into reaching at least some reasonable performance level.
Unfortunately, negative publicity from bad performance doesn't really stop these games from selling well, as proven by most AAA releases in the past few years.
The studio already killed a series once with a bad second entry, cities in motion 2...
Oh yeah, everyone remember the Panama papers? Yeah seems the public have forgotten about them a long time ago. What was done about em? Humans only remember some things.
These two issues were glaringly, obviously wrong in core modules, and 100% reproducible.
Both were bad queries (static but parameterized). One resulted in an error from the DB server, and the other was a full join rather than filter by parameter (x=x vs x=:x), so spectacularly wrong results. Both were triggered by doing typical operations in our application.
Both issues had been in our code for many, many months, yet somehow the thousands of users we have across our several hundred customers somehow didn't report or experience these issues.
I fixed both issues in less than 15 minutes.
This isn't the first time. Sometimes I'm amazed how long such glaring issues manages to survive out in the wild amongst our customers.
Not saying they didn't know. Just saying that sometimes these things just happen.