Grimrock

There has been a steady crash in location Cian's Mansoleum while trying to save game after taking power gem and pressing on the lever and a button on the wall. Even when I try to go back or go into another room I can not save the game.
The screenshot below.
What to do in this case? I would not want to throw the game after so many hours... If necessary, the savegame file attached below...
https://dropmefiles.com/Arf4M

Is there an error message?

Nathaniel wrote:There has been a steady crash in location Cian's Mansoleum while trying to save game after taking power gem and pressing on the lever and a button on the wall. Even when I try to go back or go into another room I can not save the game.

Hi, Nathaniel,
I have played this puzzle room with your save, picked up the power gem, and... save, and all works!
Here is the save after (don't forget to pick up the carved runes) : https://www.dropbox.com/s/vo6xbnkqctywt ... 2.sav?dl=0

I wonder about this, but I don't see what the hell is going on! Did you play 2.2.4 version of LOG2?
Other possible cause: memory crash. Can occurs if you have too little RAM or eventually if you have too much saves in the LOG2 folder (put the oldest in another folder).
I hope your problem is solved by this save!
Enjoy!

Duncan1246 wrote:

Nathaniel wrote:Did you play 2.2.4 version of LOG2?

Yes, 2.2.4! But I have repack of version 2.2.4 because Steam client consumes a lot of RAM and play hard... But repack is normal. For I went seven times the original game and a few more additions. No problems were not. As for memory then I have really only 4 GB of RAM, the operating system is Windovs XP 5.1 Service Pack 3.
I've played enough seventeen hours, but I have never had such problems. I often save the game and copy some files to a backup folder...

Here is a screenshot of the error... But the fact that immediately after writing the previous post, I decided to just get away from the problem location and quite a lot has passed. And now when you try to go back to the mausoleum, I still can not save the game. We have to leave the location and stored there.

P. S. I will try to remove the old savegames, clean the system and return to the mausoleum. And if the problem persists. I'll write again...

Nathaniel wrote: But the fact that immediately after writing the previous post, I decided to just get away from the problem location and quite a lot has passed. And now when you try to go back to the mausoleum, I still can not save the game. We have to leave the location and stored there.

P. S. I will try to remove the old savegames, clean the system and return to the mausoleum. And if the problem persists. I'll write again...

So, I suppose you don't use the save I have uploaded for you because you are elsewhere... No problem, if at your next visit to Cian's the same issue occurs, link your save and I shall upload a new save.
NB: I have tested this mod with Windows 7 and Mac OS 10.8, but I don't know how it works on XP. Perhaps some others guys on the forum know if Windows XP is the problem . The fact is that starting with your quicksave, I can play this puzzle and save without any problem on Windows 7.. So it isn't a bug in the mod.

Duncan

Nathaniel wrote:

Duncan1246 wrote:

Nathaniel wrote:Did you play 2.2.4 version of LOG2?

Yes, 2.2.4! But I have repack of version 2.2.4 ...

Huh? What exactly is a "repack" of 2.2.4?

Nathaniel wrote: Here is a screenshot of the error...

SpoilerShow

fw: cannot serialize function with upvalues <-- I wonder what this could mean?

It means the dungeon defined a function that uses upvalues, in a place where the game will try to save it. Don't do that, upvalues can't be saved.

minmay wrote:It means the dungeon defined a function that uses upvalues, in a place where the game will try to save it. Don't do that, upvalues can't be saved.

I have used Nathaniel's last save, played with it, saved the game without crash. How is it possible if it is an internal issue?? The crash should occurs each time in the same situation?

It is a bug in your mod, and it definitely exists. The solution is very simple: stop using upvalues. I see in your dungeon.lua that you are defining lots of upvalues in places where they will cause a crash if the game is saved.