Hi MarAri,

Apologies for the late response, I've not been too well lately.

I suspect your issue is in fact related to another issue. I am merging your thread with that one. I advise rolling back to 1.4.1 as a temporary work-around but we're hoping to rollout a hotfix soon that should correct the issue.

Hi Guillermo,

Sorry for the late reply, I've not been well for the past few days and I've just taken a look at your output logs with one of our coders.

A recurring theme is we're seeing lots of Unity code being fired but none of ours however something that does seem to occur in all cases is the game being unable to access memory.

We suspect that your game might be running out of memory, something that can happen on large or busy maps if you're running on a low amount of RAM. When you listed your system specs It seemed that most of them seemed to be in order especially the incredible 64GB of RAM!

However I failed to notice initially that you're running a 32-bit Operating System unfortunately this means that your OS is only able to address 3.5GB of memory which could be the cause of your issues. Have you considered upgrading to a 64-bit OS?

As you can see if you're running a 32-bit OS and only 4GB (3.5 addressable) memory you're only hitting our very minimum spec requirements. System Requirements

Hope that helps,

Lee

Closing due to lack of response from customer.

Closing due to lack of response from Customer.

I see a couple of Nullrefs in the output log, but I don't think there's anything related to Annex. I've not been able to replicate but I've also not been able to load your save game. Passing on to code for further investigation.

Hi Bulbaneer,

I think the savegame crashing is likely related to this thread: http://brightrockgames.userecho.com/topics/1236-after-142-update-i-can-not-load-some-saves/ Try rolling back to 1.4.1 via the betas tab and see if your save file works again. (We're trying to build a new hotfix version but all of a sudden unity is throwing up some unusual errors.)

With regards to possession I've seen only one crash related to that and neither we nor the person affected could replicate. It seemed that his game entered windowed mode all of a sudden while possesion was occuring and suddenly the game crashed.

Hi Trajan,

Sorry to hear you've been affected by this problem, as I've outlined a bug we've not been able to pin down why it occurs for some users but we do know it is a result of the Unity Version that built the game during the latest patch.

This issue is currently worked around by rolling back to Patch 1.4.1 which was built on an older version of Unity, you can do so via the betas tab on steam. We're also looking to release a public test version of the upcoming hotfix tomorrow. Which you will be able to opt into once it goes live.

Hi Guys, I'm going to merge this with a related thread. We're rolling out a hotfix for public testing tomorrow, but for now you can rollback to Patch 1.4.1 using the betas tab on steam.

Keeping this as accepted until we open public testing for the hotfix. For some reason Steam is now not accepting new builds from us!