Hrm, it should have worked, but you couldn't do a spiral or any similar trick.
The room would need more than the half length of the long tavern in terms of covered map width or map height.
To be more exact, if you put an rectangle around the entire tavern floor room, the rectangle put around the room you need to build must have at least half of the area than the rectangle around this tavern floor.

However this is a complicated workaround and it shouldn't take long before the patch comes out.

Cheers :)

Hello Dark,
first of all thank you for this excellent bug report.
It contains all information one could wish to track down a problem.
This is not self-evident nowadays :)

I have loaded your save game and got the exact same behaviour.
The warning popup is there to prevent the game from crashing when something went utterly wrong.
As far I could figure you saved your game with something in your hand which died/was destroyed before you saved.
While this case can happen under rare circumstances, it is handled correctly while just playing the game.
But the deserialization routine was not able to handle data stored in this odd state and was thus trying to access a null reference.

We have now fixed that such cases can cause issues with save games.
A patch removing the issue should come in a couple of days.

However I was able to "repair" your save game.
After fixing the issue locally i quickly dropped what you had in your hand and saved again, so that this issue is circumvented.
Simply put it into the folder where you took the other save games, then quit+restart steam
and you should find it in load menu "Campaign" under "Dark 7 fixed loading issue".
Here are the files:
fixed-savegame.zip

Cheers and Thank you for reporting :)

Thank you and please add any additional info you have (eg. questions above).
Cheers

Hello Thadir,
I can not see any issue in the log. It looks like a normal session without problems.

Did you restart the game since the issue occured?
In this case all logs overwritten, we need a log from a play session where the issue occured.
If it happens again, then please grab the log before restarting the game.
Also when did it happen?
Only once or multiple times?
On game start or in the middle of playing a map and if which map?
Do you use Windows 7 32bit or 64bit?

The issue is already fixed and will be patched in a couple of days.

However if you want to avoid the problem right now, it should not freeze, if you build a room which is at least half as long as this tavern floor, you can sell it afterwards.
This will make sure that an internal buffer is increased so that the problem does not happen.

Hope that helps!

This sounds really odd and so far I have no clue why it doesn't work for you.
Can you start the game just trigger the issue and close it, then grab the Player.log and upload it here?
(As specified here https://forum.subterraneangames.com/threads/please-read-how-to-report-a-bug.4689/ )
Maybe this gives us pointers what is going wrong on your end.

Thanks

It's still running out of memory like before.
So what ever you try to save is still too big for your available RAM.
Since you have now 3.5 GB usable I wonder if you run other memory intense processes next to the game.
Can you right click on the taskbar to open the Task Manager, switch to "Processes" tab and sort all by "Mem Usage"
Like here:


What does it show upmost?
Is it something required while you play?

Also are you still using Windows XP 32bit?

Hello Thadir,
which OS are you using (Win XP, 7, 8.1, 10) and is it 32 or 64 bit?
Can you upload your logs as specified here https://forum.subterraneangames.com/threads/please-read-how-to-report-a-bug.4689/
?

Cheers

Hello Julianb3000,
we got a similar report recently, which we fixed already:
https://forum.subterraneangames.com/threads/unclaimable-neutral-tiles.9864/

However when the old bug forums was locked, I continued the thread with the reports in a private conversation on forum.
We figured out this is a map editor bug which creates invalid claimed tiles which are "fortified" (which is only meant for walls) when you paint claimed tiles over fortified walls.
Since these claimed tiles have the fortified flag (you can identify those when tooltip shows "[Fortified]" http://imgur.com/8732oYj) some game machanics considers them as walls.

Now there is a game mechanic that makes sure:

When ever you claim a new tile all adjacenting walls which do not have

at least one claimed tile of their owner in 8 neighbors around is automatically unfortified.

(you might have already seen that enemy walls are unfortified when you claim around them)

So when you claim any neighbor of of such "fake fortified wall" the game

will in this process "unfortify" the claimed tile, which does simply remove ownership.

What remains is a claimed tile without an owner, something which should never exist.

Workers who try to unclaim can't do it and will get stuck.

We fixed the issue on both two ends.

- Fixed that the map editor can create such tiles

- Made sure that a tile having the issue is automatically fixed on map loading

I guess you have the same issue and it is fixed already.

A patch will be coming quite soon.

Hint:
Until patched, you should be able to fix affected tiles simply by applying the Annex spell on them.

Please let me know if you think it is not this bug we have fixed.

Cheers

PS. I was not able to open your link as it points to "myworkshopfiles" which something you can only access private

Just for others reading this:
So what did you do to fix the issue?

For the saving issue:
When you did your report on the old bug forum your logs clearly said you did run out of RAM.
If you have now more RAM saving should work flawlessly.
Do you still have issues?
If yes, please upload another output_log so we can see why.
In this case, under Control Panel -> System what does it say how much RAM you have usable?
Cheers