Print

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

[Dark_Author]

I just attemted to play Masterwork DF and I can't seem to get the included Dwarf Therapist working.  I have no idea why, and it was working fine before (I think).  Anyway, it crashes as soon as it tries to connect to DF.  I even tried moving it to the games exe file location and had no luck.

Any ideas on how to fix this?

Note:  Since Masterwork uses version 34.11 of DF, I even tried redownloading that version of DT again.  That one didn't work, either.

Note 2:  Dwarf Therapist for the 40.24 LNP works great.

[Dark_Author]

No one has any ideas about what could be happening here?  I even completely redownloaded Masterwork.  No luck.

[smakemupagus]

If it's something really related to Masterwork you might have more luck if you ask in the Masterwork forum, but I don't remember seeing reports of anyone else having this problem.

[Dark_Author]

Me either.  I did a search and looked all over.  I found a few people on Reddit who had this issue but it wasn't with Masterwork.  They were able to resolve it by starting a new fortress in the same world.  I tried that and it didn't work.

The thing is, it used to work.  All that has changed on my computer in the last couple of months since I've played is I finally let my Catalyst drivers update.  I can't see how this would affect Dwarf Therapist, and even if it did, other people would have noticed for sure.

[Dark_Author]

Sorry for the double posting but I fixed it!  I was able to find the solution by changing the searches I was doing from "Dwarf Therapist crash" to dwarf therapist has stopped working.  That led me to this post here: http://www.bay12forums.com/smf/index.php?topic=66525.2835

The solution is to go into appdata/roaming/UDP Software/Dwarf Therapist and delete or rename the dwarf therapist.ini file.  Aparently this can get corrupted.  Not sure why the LNP 40.24 version worked and not the the one from 34.11 or Masterwork but, hey, this fixed it.  So, if anyone else has this issue, I thought I should post the solution.