Map out 0.31.04 legacy version

[GoogleCodeExporter]

What steps will reproduce the problem?
I really don't know. I downloaded the newest version of Dwarf Therapist when 
I got the popup. I looked at the changelog and saw that it had support for DF 
0.31.04, which I didn't know was out. I downloaded that as well, and placed 
the two together in the same way I had for the previous versions of both.

What is the expected output? What do you see instead?
I played a new game of DF and once the immigrants arrived I loaded up 
Therapist. Got an error message saying

I'm sorry, but I don't know how to talk to this version of Dwarf Fortress!
(Checksum:0x4befdde5)

What version of the product are you using? On what operating system?
0.5.2 of Therapist. 0.31.04 of DF from the forums. The legacy one.

Please provide the "run.log" file in the "log" directory of DwarfTherapist
when this error occurred.

I did a quick check on the "issues" page, but didn't see anything related to 
this. I'm sorry for wasting your time if I the error is my fault and I'm just 
being stupid.

Original issue reported on code.google.com by NolanBow...@gmail.com on 20 May 2010 at 8:31

Attachments:

• run.log

[GoogleCodeExporter]

This is very strange. According to the log you attached, your copy of 0.31.04 
has a 
different checksum than my copy of 0.31.04.

I'm wondering if Toady shipped two different versions and called them both 
0.31.04 
(that would be very bad)

Original comment by treyst...@gmail.com on 20 May 2010 at 9:01

• Changed state: Accepted
• Added labels: Priority-High, Version-0.5.2, Milestone-0.5.3, Component-Logic
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I just double-checked, and yes, it looks like there are actually two completely
different .exe files for the "small" and "legacy" downloads... which kind of 
makes
sense, I think.

Most obvious differences: different filenames ("small" has "Dwarf Fortress.exe"
whereas "legacy" has the classic "dwarfort.exe"), different file sizes (legacy 
.exe
is exactly 65536 bytes smaller), different modify dates (legacy is almost 4 
hours
older), lack of ICON resource in the non-legacy.

Original comment by octavs...@gmail.com on 21 May 2010 at 4:30

[GoogleCodeExporter]

I downloaded the "small" 31.04, and it doesn't want to work with Therapist 
either, but 
I get a different message this time. Now it says that DF has stopped running or 
I 
unloaded a game, even though I've got a fort up and active. Here's the log for 
that 
one.

Oh, and I'm using Vista. I forgot to mention that in the first post. Not sure 
if it 
will make a difference at this point, but who knows?

I'll probably be going back to DF 31.03 for know. Therpist makes the game so 
much 
easier to manage, and 31.04 seems to have it's own batch of new bugs that need 
to be dealt with.

Original comment by NolanBow...@gmail.com on 21 May 2010 at 12:55

Attachments:

• run.log

[GoogleCodeExporter]

The new error, invalid creature_vector address, sounds the same as issue 233, 
and I
think they might both be the same bug. I don't really use 31.04 (cba to get 
graphical
tilesets working), so cannot report on the effects of trying to keep a 
long-running
game in it.

Out of curiosity, Nolan, does it start working again if you save and reload the 
game
in DF (i.e. force DF to reallocate all its interesting memory again)? I suspect 
not,
though, given you're getting the error pretty much as soon as you run DT. Also, 
I
think Trey might ask you to upload your savegame when he gets around to this so 
could
I bother you to do it beforehand? At the very least, I can see if it also fails 
to
work on my copy of DF.

Original comment by octavs...@gmail.com on 21 May 2010 at 1:08

[GoogleCodeExporter]

I'm still fairly new to DF, so I don't have any ongoing saved files, but I just 
finished work, and I've got the whole weekend ahead of me. I will do this FOR 
SCIENCE! 
Feel free to use me as a guinea pig for the next couple days.

Give me a couple hours to try out your suggestions, and I'll upload everything 
as soon 
as I can.

Original comment by NolanBow...@gmail.com on 21 May 2010 at 1:15

[GoogleCodeExporter]

Well, now. that worked out just fine. Opened 31.04 small, made a fortress, 
opened 
Therpist. Connection error.

Exited DF, reloaded the saved game, opened Therpist. Bam! All seven dwarves.

Original comment by NolanBow...@gmail.com on 21 May 2010 at 1:35

[GoogleCodeExporter]

Interesting! According to issue 234, you will probably need to redo the 
save/reload
every migration wave, as well. Beyond that, I think we've narrowed down the 
problem a
little bit, which always helps :)

Original comment by octavs...@gmail.com on 21 May 2010 at 1:42

[GoogleCodeExporter]

Sorry for so many comments. I feel like I'm spamming this thing. Should I still 
upload 
anything now that the problem has been found. (I think it's been found.)

I just made a second fortress, and haven't saved it yet. Therapist doesn't want 
to see 
these dwarves now. It only seems to be able to see the ones from a game thats 
been 
saved.

I'm going to play through my first save a bit to see about the migrants thing.

Original comment by NolanBow...@gmail.com on 21 May 2010 at 1:45

[GoogleCodeExporter]

Think you should hold off on uploading anything for now, since the issue only 
seems
to occur when creating a new fort rather than after loading a savegame. I'll 
try to
replicate it, as well, when I have some time later tonight, and will report 
back my
success or lack thereof. Until then, have some fun, find more bugs, do 
everything you
were going to do anyway :)

(Also, keep in mind I'm not a contributor to DT (yet), so if Trey shows up and 
asks
for whatever, he's the one who knows what's really going on here. Might be 
obvious,
and if so, my apologies, I'd just rather make it clear where I'm coming from.)

Original comment by octavs...@gmail.com on 21 May 2010 at 1:53

[GoogleCodeExporter]

Oh, no. Thanks very much. Thanks to you I've got the two doing something that 
resembles 
woring together. Ha ha. Now it's mostly the new settings in DF itself that seem 
to be 
fighting me.

Original comment by NolanBow...@gmail.com on 21 May 2010 at 2:01

[GoogleCodeExporter]

I've got time now and I've managed to get some nice big trace logs down, but I'm
going to place my findings in issue 233, since this one is about DT not 
speaking to
DF 0.31.04 legacy.

Original comment by octavs...@gmail.com on 21 May 2010 at 8:06

[GoogleCodeExporter]

changing title as this is a problem with there being two "0.31.04" versions 
floating 
around.

Original comment by treyst...@gmail.com on 22 May 2010 at 10:07

• Changed title: Map out 0.31.04 legacy version

[GoogleCodeExporter]

fixed in r4b0dcd6877

Original comment by treyst...@gmail.com on 1 Jun 2010 at 12:41

• Changed state: Fixed