Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Grue]

After two of my worlds were killed by inflate error bug (game crashes on saving then fails to load), I'm thinking that there is a corellation between sleeping in adv mode and this bug. Both of characters slept in the city before saving (to wait for the mayor to come). Both times the game crashes when I saved those characters. These were the only times I ever had this bug. I think the latest version introduced the bug, because I never had it before.

[Grue]

Also, noticed this in error log:

DOUBLE TAGGED ITEM: Sleep
DOUBLE TAGGED ITEM: Sleep
DOUBLE TAGGED ITEM: Sleep
DOUBLE TAGGED ITEM: Sleep
...

May be related, huh?

[Heliopios]

When your game crashes it never stops properly, and when you load up that same save before the crash, it sometimes get a Pime Taradox and fucks itself up by thinking both of the game were playing at once, or something along those lines, and creates that inflate error.

[Grue]

I understand, but it has to be found why it crashes in the first place. It's not like it's supposed to happen at random times.

[4bh0r53n]

I think that toady said in some other thread that the inflate -3 error is caused by the price of plant cheese....

[herrbdog]

I've gotten it on worlds that I had only played Dwarf mode... so... dunno

Backup Early and Backup Often! (for EVERYTHING you do on a computer!)

[Gaulgath]

quote:Originally posted by 4bh0r53n:
<STRONG>I think that toady said in some other thread that the inflate -3 error is caused by the price of plant cheese....</STRONG>

Actually, that can be one of the many causes to destroy a world. Must be hard living in a place that you know could crumble at any moment by the price of a nonexistent cheese from a nonexistent plant...

[Grue]

Backup doesn't help if a crash reliably happens after some action. It's not a random punishment from gods, it's just a bug in the code.

[Dreamer]

quote:Originally posted by herrbdog:
[QB]I've gotten it on worlds that I had only played Dwarf mode... so... dunno
QB]

It was because the dwarves were sleeping.

I've had the same thing happen in Adventurer mode - Made the mistake of sleeping and got the error.  Never had it happen with one of my Fortress maps, even when I've had adventurers prior to settling down.

[Neopergoss]

Yes, it must be cheese.  It happened to me soon after I bought cheese for the first time from the dwarven caravan.

No, it has nothing to do with adventure mode, as I haven't played it yet.

  I was farther than I'd ever been before, too.  It exited and saved normally, but the next time I tried to load it...

I'm a perfectionist and I was getting everything just right this time...after starting over many times before.  Oh well, at least I already know what to do in the beginning.

[LSTAR]

Yeah, this is one of the harder things to bear with Fortress right now.
If there's a famine; nyeh, it was the immigrants' fault, should have  made more food.
If a goblin invasion puts everyone to the sword; so what? We took most of them with us!
If you permaflood your fort; well that was stupid wasn't it?

But this? There's no closure! No cool last moments! No desperate stands! Not even a chance to reclaim later. Just nothing...
I usually tell myself the whole world was destroyed by a natural disaster like a comet strike.

[Toady One]

The plant cheese problem was fixed.

The only sure way to create an inflate -3 that I'm aware of is quitting out of the game prematurely or backing up saves improperly or using a save after a crash, and most of the recent inflate -3 reports have been caused by this (a lot of the older ones were caused by bugs).  If there's still a bug for this, I'm not sure how to reproduce it.  In adventure mode, I think there might be a crash issue with wrestling.

[Neopergoss]

quote: The only sure way to create an inflate -3 that I'm aware of is quitting out of the game prematurely or backing up saves improperly or using a save after a crash, and most of the recent inflate -3 reports have been caused by this (a lot of the older ones were caused by bugs).  

So if, say, I were to quit the game with ctrl+alt+delete without saving, then load it, play for a while, and save again, it's not unusual for this kind of error to occur the next time I try to load it?

[Toady One]

Yeah, the game is interacting with several world files while it plays -- the game you select when you load the game is being altered in part as you play, and those alterations are not finalized if you quit out early.  I'm going to put in autosaves and so on in a bit, but right now, you have to create your own backups.

[Neopergoss]

Ok, good to know.  And thanks for the quick response.