Print

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

[Finndibaenn]

Hi

I'm been able to pinpoint down a crashing bug, it seems to be caused by a caravan arrival. (that's the last line in gamelog.txt)
Is this known and is there a workaround ?


edit : dffd link to the save http://dffd.wimbli.com/file.php?id=9852

[wierd]

Have you been doing any modding?

(Installing a graphics pack counts.)

[Finndibaenn]

yes, this is using dfhack and phoebus tile sets.

caravans have been coming and going for 4 years without noticeble issues previously though

[ptb_ptb]

Done any retiring / unretiring / abandoning / reclaiming?
Done any adventuring?

[Finndibaenn]

no adventuring, but i retired/unretired a few times the same fort to try and understand why no goblins would visit.

I'm currently uploading the save to dffd if anyone wishes to look

[Finndibaenn]

added a link to the save in the initial post

[ptb_ptb]

Did it crash within one and a half months of when you last unretired? And have you ever used dfhack LAIR?

[Finndibaenn]

I think it's been more time since i unretired, but i'm not sure if i can check that ?
Regarding the "Lair" dfhack thing, i'm not aware of it.

AFAIK the features i use are autobutcher and workflow

according to legends viewer
In 128, early winter, The Diamond Mirror of The Sack of Ink  launched an expedition to reclaim Lancebeach.

In 129, midspring, The Diamond Mirror of The Sack of Ink  launched an expedition to reclaim Lancebeach.
In 129, early autumn, the dwarf Datan Whipflag created a masterful (UNKNOWN) for The Diamond Mirror at Lancebeach.

edit 2 : digging into the legends xml to try to get more precision on the reclaim dates
<historical_event>
      <id>34056</id>
      <year>128</year>
      <seconds72>332557</seconds72>
      <type>reclaim site</type>
      <civ_id>68</civ_id>
      <site_civ_id>456</site_civ_id>
      <site_id>404</site_id>
      <unretire/>
   </historical_event>

<historical_event>
      <id>34123</id>
      <year>129</year>
      <seconds72>54568</seconds72>
      <type>reclaim site</type>
      <civ_id>68</civ_id>
      <site_civ_id>456</site_civ_id>
      <site_id>404</site_id>
      <unretire/>
   </historical_event>

the crash time is a bit after the retre event (that's me restoring the save to go to legends mode)
<historical_event>
      <id>34258</id>
      <year>129</year>
      <seconds72>213043</seconds72>
      <type>site retired</type>
      <civ_id>68</civ_id>
      <site_civ_id>456</site_civ_id>
      <site_id>404</site_id>
   </historical_event>


I have no idea how to translate the "seconds72" to a date though

The crash happens at 10th Limestone

edit 3 : according to http://dwarffortresswiki.org/index.php/v0.31:XML_dump, a year is 12 months of 28 days and is also 403200 seconds , meaning 1200 seconds per day.

THat would put my unretire at 18 slate, roughly 4.5 months before the crash

[ptb_ptb]

In Dwarf Fortress, apparently, there are 50 seconds in an hour, 24 hours in a day, 28 days in a month, 12 months in a year

Crash Seconds72 213043 = 178 days into year 129
Last unretire Seconds72 54568 = 45 days into year 129

A bit under 5 months after your last unretire (if I didn't make any mistakes).

Which makes it different to the crashes I've seen recently.

[EDIT] Welp, I've not got a clue. I think you should write that sucker up on the bugtracker.

If you want to 'bypass' the crash immediately retiring then unretiring might work.

[Finndibaenn]

I will submit a bug in mantis then, thanks for your time ptb

edit : submitted http://www.bay12games.com/dwarves/mantisbt/view.php?id=8398

[ptb_ptb]

Oh yeah, in the bug report you should mention that disabling dfhack doesn't make any difference (I just checked).

[Finndibaenn]

just added that as a note, thanks again for caring and taking the time

[Codyo]

I'm having this problem too in a vanilla game. Any liaison freezes the game when they arrive at my fort. Changing out nobles, deconstructing the trade depot isn't fixing it.