An update from my side after the Hotfix on Thursday (yes, the problem persists):

It’s curious that you mention in the Hotfix description as the very first item:
“* Fixed a bug which caused performance issues whenever approaching or logging in near a base”

Because that exactly seems to be the root cause - BUT it is still the problem AFTER the hotfix. So, either you have just fixed one aspect and there are more, or it is still a problem related to my specific setup/save game/database.
Like I said in the original post, I can circumvent the crash by using a game.db older than the AoW2 update, that always loads and I can play. Getting the tip from your “Fix Description” I tried logging out/disconnecting/quitting the game outside of my base and it worked. I could load the game after restarting the game. However, it led to the same problem again when I logged out at a new tiny test base.
Looking into my Saved folder I can also see now two additional files next to the game.db, named game.db-shm and game.db-wal, which are technically related to the sqlite technology… So, I wonder if somebody from the Funcom Support Team can shed some light on the situation because obviously the issue is NOT fixed and I’m afraid there won’t be any other fix once the issue "is addressed " as stated in the Hotfix. Logging out outside of the base is very counter-intuitive and is another step in destroying the immersion of the game. And the price of failing to do so is high, I loose all my progress when I accidentally log out in my base.

1 Like