Print

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

[Azrayel]

No longer can I impersonate a Diving Being.

It was inevitable.

[Tawa]

Hm. I should check the version number on the title screen to be certain.

Oops, I had accidentally used 40.01.

Sorry about that, ehehe.

[Nopenope]

Crashed already; alt-tabbed on Linux while the game was loading a map in adventurer, suddenly the game window was simply not there and the process was killed. No idea what happened.

[thewonderidiot]

It was inevitable.

Stopped autosave features from corrupting worlds

Does that mean that only saves made with autosave were getting corrupted?
If I didn't use autosave, can I still play my current fort in 40.01 for a while without worrying about corruption causing crash?

Yes -- the corruption was caused by initial/seasonal/yearly autosaves deleting randomly generated object interactions (one of the functions that got called incorrectly assumed that the game would exit after save, like normal manual saves do). So long as you have all autosaves disabled, you won't be hit by this save corruption glitch.

[WillowLuman]

Was getting some crashes in the last version that had no errorlog, but I believe had something to do with cavern creatures dying by the dozen every month.

[Alev]

Thanks,Toady!

[Rafal99]

Does that mean that only saves made with autosave were getting corrupted?
If I didn't use autosave, can I still play my current fort in 40.01 for a while without worrying about corruption causing crash?

Yes -- the corruption was caused by initial/seasonal/yearly autosaves deleting randomly generated object interactions (one of the functions that got called incorrectly assumed that the game would exit after save, like normal manual saves do). So long as you have all autosaves disabled, you won't be hit by this save corruption glitch.

Thank you.
I have had set

Code: [Select]

[AUTOSAVE:NONE]
[AUTOBACKUP:NO]
[AUTOSAVE_PAUSE:NO]
[INITIAL_SAVE:NO]in the d_init.txt so it seems my fort should be ok.

[kingubu]

The guy who figured out blood_max = 1/10th body size should get credit somewhere for the growth bug.

That guy was awesome, whoever he was.

[Archereon]

For the people still getting crashes on deity conversations and so on, is there any chance you're playing a save from the original release of 0.40? I haven't had time to test it myself, or even test whether old saves that aren't affected by the autosave bug would even load, but I suspect this could be an issue.


Anyone, now that the most reliable crashes have been squashed, what do you think you'll be tackling next? Retirement in both versions is somewhat wonky at this time, making it somewhat difficult to play with the now dynamic worlds then come back to your fort/adventurer to see what's happened in the intervening time, though I have no idea whether the associated problems there would be easy to fix.

Aggression and fear could definitely use some tweaking; necromancers will frequently end up fleeing from their own undead, and friendly boogeymen have been reported in several games, for two examples of oddities with the new system that should never happen.

[Toady One]

I haven't gone over everything yet, but the calendar is really slow, and that affects everything.  Mystery babies seem like potential catastrophic trouble, if it is coming from scheduled births around the world (as that might corrupt the files having them two places at once).  Retired adventurer clones or whatever seem pretty bad.  Yeah, the whole matter of decision-making is messed up all around, though I'll probably snatch up some more of these game-stoppers first.

[XXSockXX]

I just had a crash when bringing up the quest menu (Q) while fast-travelling, no errorlog. Can't reproduce it however. I think I've seen this on the bugtracker already.

Yup, here it is:
http://www.bay12games.com/dwarves/mantisbt/view.php?id=6543

I think I can reliably reproduce this one, uploaded a save: http://dffd.wimbli.com/file.php?id=8846

I started with a dwarf in one of the hillocks, fast-travelled, hit Q and it crashes, multiple times now.

[Archereon]

I haven't gone over everything yet, but the calendar is really slow, and that affects everything.  Mystery babies seem like potential catastrophic trouble, if it is coming from scheduled births around the world (as that might corrupt the files having them two places at once).  Retired adventurer clones or whatever seem pretty bad.  Yeah, the whole matter of decision-making is messed up all around, though I'll probably snatch up some more of these game-stoppers first.

Sounds nice, keep up the great work!

In regards to the adventurer cloning, I've heard that the issue will frequently affect other characters when loading/unloading sites, you think there might be a relationship between it and the mystery babies?

[Toady One]

It's almost futile to guess this early on -- it's best just to get a reproducible method or a broken save and follow the trail.

[mario384]

It's almost futile to guess this early on -- it's best just to get a reproducible method or a broken save and follow the trail.

  Did we figure out what was with the mystery babies yet?  Is it those new underground goblin forts?

[Dante]

DF2014: The "Don't tell your god that mystery babies were inevitable" version.