Print

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

[Old-one-eye]

It sounds like you guys have the wrong creature vector. DF usually has between 1 and 4 creature vectors at a time, only 1 of which is kept up to date frame-to-frame. Either that, or it's something new entirely and will take some disassembly work to figure out.

Sorry I really don't understand that, is it fixable by someone with minimalnon-existent coding experience? 

[chmod]

It sounds like you guys have the wrong creature vector. DF usually has between 1 and 4 creature vectors at a time, only 1 of which is kept up to date frame-to-frame. Either that, or it's something new entirely and will take some disassembly work to figure out.

Sorry I really don't understand that, is it fixable by someone with minimalnon-existent coding experience? 

I mean that at the core, DT needs to have intimate understanding of how DF stores creatures, and all of their various attributes. Although the code for creatures may not change much from release to release, their locations after compilation might. This is pretty quickly found out via the scanner I provide as a part of DT. If nothing much changed, there is a simple process to map out a new version of DF. The instructions are here http://code.google.com/p/dwarftherapist/wiki/MappingNewVersions

That procedure will *NOT* work if several things have changed inside the creature's structure. Say if the race id of a creature changed offsets, it will take substantially more work to map a new version than just pressing a button in the scanner I wrote. Rest assured, I will add support for 08, and release it after I have tested it.

[Old-one-eye]

Oddly it's working now, out of the blue. Phew.

[Andir]

That's what I love in my applications... magic!

[Malicus]

Hrm, the creature vector I used for the SDL version was:
creature_vector = 0x0168171c (uncorrected:0x0168171c)

The other possible one I found was:
creature_vector = 0x01681794 (uncorrected:0x01681794)

I'll have to actually play DF tonight to see if one suddenly stops working after a while.  Maybe I goofed.

[Old-one-eye]

It seems to stop working if I mod the raws. :/

[SirBruce]

With .06 I would have random times when DT couldn't find DF.  Restarting both DF and DT fixed the problem.

[Ratboy]

I'm gonna keep messing around with it, but I'll ask here too: Where do those numbers etc go? I need my Therapist.

Assuming you're using Windows, they go in the (Dwarf Therapist)\etc\memory_layouts\windows directory.  There should be a bunch of similar files there already.

Yeah, just title it v0.31.08_graphics.ini.  Actually, just download this file and put it in that directory:
http://www.megaupload.com/?d=QZS4IATZ

That works for me but using dfoffsets.exe (dfhack 0.4.02) I get different offsets to what have been posted here, if I use them all DT crashes but if I just use the following changes - it still works. Haven't got a functioning fort to test this on though, so if someone wants to, then please do. Also could somebody explain why different people get different results please.

[addresses]
translation_vector      = 0x016c63d4
language_vector         = 0x016c63a4
creature_vector         = 0x0168172c
dwarf_race_index        = 0x014acef4

[peterix]

I'm gonna keep messing around with it, but I'll ask here too: Where do those numbers etc go? I need my Therapist.

Assuming you're using Windows, they go in the (Dwarf Therapist)\etc\memory_layouts\windows directory.  There should be a bunch of similar files there already.

Yeah, just title it v0.31.08_graphics.ini.  Actually, just download this file and put it in that directory:
http://www.megaupload.com/?d=QZS4IATZ

That works for me but using dfoffsets.exe (dfhack 0.4.02) I get different offsets to what have been posted here, if I use them all DT crashes but if I just use the following changes - it still works. Haven't got a functioning fort to test this on though, so if someone wants to, then please do. Also could somebody explain why different people get different results please.

[addresses]
translation_vector      = 0x016c63d4
language_vector         = 0x016c63a4
creature_vector         = 0x0168172c
dwarf_race_index        = 0x014acef4

dfdoffsets just prints what dfhack has... it's not necessatily right. Also, vectors are treated differently in DT and DFHack, so they will have different addresses.

[Ratboy]

I'm gonna keep messing around with it, but I'll ask here too: Where do those numbers etc go? I need my Therapist.

Assuming you're using Windows, they go in the (Dwarf Therapist)\etc\memory_layouts\windows directory.  There should be a bunch of similar files there already.

Yeah, just title it v0.31.08_graphics.ini.  Actually, just download this file and put it in that directory:
http://www.megaupload.com/?d=QZS4IATZ

That works for me but using dfoffsets.exe (dfhack 0.4.02) I get different offsets to what have been posted here, if I use them all DT crashes but if I just use the following changes - it still works. Haven't got a functioning fort to test this on though, so if someone wants to, then please do. Also could somebody explain why different people get different results please.

[addresses]
translation_vector      = 0x016c63d4
language_vector         = 0x016c63a4
creature_vector         = 0x0168172c
dwarf_race_index        = 0x014acef4

dfdoffsets just prints what dfhack has... it's not necessatily right. Also, vectors are treated differently in DT and DFHack, so they will have different addresses.

Ahuh, so just what actually is a vector in this sense briefly.

[peterix]

Ahuh, so just what actually is a vector in this sense briefly.

Well... a stretch of memory containing items of identical size and type. They have a descriptor part that says where they start, where the stretch of memory given to them ends (alloc_end) and how long they actually are (end). Depending on compiler and the implementation of vectors, the descriptors can have different layout in memory.

So... a vector descriptor on Linux is just the three values:
start, end, alloc_end

A vector descriptor old MS C++ compilers used looked like this:
nonsense, start, end, alloc_end

A vector descriptor new MS C++ compilers use:
nonsense, nonsense, nonsense, start, end, alloc_end

All parts have the size of 4 bytes. The nonsense parts have some internal use, but understanding them isn't essential for reading the data.
DT is using the second form even when it's not right (AFAIK, it's been some time I checked). DFHack can use all of them, depending on the particular version of DF it's working with. So to get the right address for DT, you have to do some hexadecimal arithmetic.

[Ratboy]

Ahuh, so just what actually is a vector in this sense briefly.

Well... a stretch of memory containing items of identical size and type. They have a descriptor part that says where they start, where the stretch of memory given to them ends (alloc_end) and how long they actually are (end). Depending on compiler and the implementation of vectors, the descriptors can have different layout in memory.

So... a vector descriptor on Linux is just the three values:
start, end, alloc_end

A vector descriptor old MS C++ compilers used looked like this:
nonsense, start, end, alloc_end

A vector descriptor new MS C++ compilers use:
nonsense, nonsense, nonsense, start, end, alloc_end

All parts have the size of 4 bytes. The nonsense parts have some internal use, but understanding them isn't essential for reading the data.
DT is using the second form even when it's not right (AFAIK, it's been some time I checked). DFHack can use all of them, depending on the particular version of DF it's working with. So to get the right address for DT, you have to do some hexadecimal arithmetic.

Interesting. Well, that explains that. I couldn't figure out why it worked for DFHack and stone sense RC2 - I used it to make a memory.xml which apparently works, and didn't work for DT. But as I'm interested in this sort of stuff, if you don't mind, what sort of maths I mean what calculations. Hex doesn't bother me, I've been playing around with it for years (more than most of the people here have been alive). But I need to know more about how memory actually works.

[chmod]

How about you guys take this conversation out of this thread please.

[Dark_T_Zeratul]

When I run Dwarf Therapist with version .08, it says, "I'm sorry but I don't know how to talk to this version of Dwarf Fortress!" The latest supported version it lists is .06.

[lodester]

When I run Dwarf Therapist with version .08, it says, "I'm sorry but I don't know how to talk to this version of Dwarf Fortress!" The latest supported version it lists is .06.

You are exactly right. You've won an all-expense paid weekend vacation in Winooski, VT!