Print

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

[seanb]

I don't have a clue what any of that means, but i'm glad to see you are back to working on it! This will help out a bunch!

[Aklyon]

Ooh, a chance to answer a question!

Dwarf Foreman's basic function is to allow you to automatically create jobs to keep a specific stockpile for common items such as fuel, cloth, thread, bins, and barrels.  It helps you never have to say "Whoops!  I forgot to make sure I brewed some drinks this season!"  Instead, you just tell Dwarf Foreman that you always want at least X drinks on-hand, and it will automatically queue up some brewing jobs when your supplies dip below X.

YES. I want this, and am joining the couple people hurrahing your return, devek.

[vrga]

quicky question, this is windaz only, right?

[devek]

Can you guys help me for a bit? Foreman isn't ready but I have something that needs to be tested.

http://dffd.wimbli.com/file.php?id=4100

Download that and test it for me? All the buttons should work on the left for any vanilla version of df above 0.13. I haven't added the robustness to deal with modded versions of DF, but I will add that once I actually get a release out. The dump jobs obviously won't show anything if your manager isn't trying to assign any

The cool thing is that my code no longer relies on offsets and seems to do a good job of finding what it needs

quicky question, this is windaz only, right?

Yes.

[Aklyon]

SDL or Legacy DF?

[devek]

I can't say for sure, I imagine legacy is just legacy. It might be supported on accident though

[seanb]

Appears to work perfect with .31.25

[Aklyon]

No problems in .31.25 w/Ironhand graphics, but this two sounded a bit odd.

Code: [Select]

20 other materials found!
-snip-
#17 UNKNOWN_SUBSTANCE
-snip-
#19 CREATURE_1

[devek]

That is an actual material, hehe.

Thanks for the testing, hope to have a release out tomorrow. I'm dying to get back to my fort :/

[forsaken1111]

I'll be testing shortly as well to see how it works on an existing fort, 200+ dorfs

Worked great on everything I tried it on, even some forts which I ported from other versions.

[devek]

FUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU

With the old MSVC, it was forgiving if you tried to free a memory address you didn't allocate.. with the new MSVC compiler he has been using since .13, it crashes every freaking time.

1) Foreman connects to DF.
2) Foreman allocates memory inside of DF and relocates the manager vector to that memory.
3) Foreman creates a job in the allocated memory space and links it into the vector.
4) DF finishes the job and tries to free its memory. "Undefined" behavior by the C standard, but harmless with MSVC 8. Crash under MSVC2010.

So ya, I finished updated it.. but its useless and causes a crash if you ever finish a job and Foreman will be on hold indefinitely until I find a resolution. I've checked, double checked, and triple checked and will check again when I wake up. I'm so spoiled by my own utility, DF isn't even fun to play without it TBH.

Anyone know a forum with REALLY elite windows hackers I can ask for help?

[Kogut]

So why it worked for forsaken?

[neverknown]

hm im no coding expert but why do you relocate the vector? and how does that look like in the source?

[devek]

hm im no coding expert but why do you relocate the vector? and how does that look like in the source?

C++ does this anyway, because the vector needs to grow when you add things to it. I just push the process along and grow it to 1000 entries which is more than I will need and prevents it from up and moving while I am in the middle of using it. This alone isn't a problem and I can continue to use dwarf fortress in any way without a crash, since the entire vector is never freed from memory. When you add jobs from within DF it will allocate them into their own memory and also have no problem freeing them.

A STL vector in MSVC 2010 is 16 bytes. There is a pointer to its base, a pointer to its current position, and a pointer to its highest address, and then 4 bytes of unused padding.

In code, moving it from another process kind of looks like..

Code: [Select]

        const LPVOID lpvResult = VirtualAllocEx(hDF, NULL, 0x20000, MEM_COMMIT | MEM_RESERVE, PAGE_READWRITE);

        const uint32_t queuebase = readDWord(queuePointer);
        const uint32_t queuepos = readDWord(queuePointer+4);
        const uint32_t queuesize = queuepos-queuebase;

        const uint32_t queue = (uint32_t *) malloc(queuesize);
        ReadProcessMemory(hDF, (void *) queuebase, (void *) queue, queuesize, 0);
        WriteProcessMemory(hDF, (void *) lpvResult, (void *) queue, queuesize, 0);
        free ((uint32_t *) queue);
        writeDWord(queuePointer, (uint32_t) lpvResult);
        writeDWord(queuePointer+4, ((uint32_t) lpvResult) + queuesize);
        writeDWord(queuePointer+8, ((uint32_t) lpvResult) + 0x0FA0);
        writeDWord(queuePointer+12, 0xDEADBEAF);
And of course, the read/write dword code looks kind of like..

Code: [Select]

uint32_t readDWord(const uint32_t address)
{
    uint32_t dword = 0;
    ReadProcessMemory(hDF, (void *) address, (void *) &dword, 4, 0);
    return dword;
}

bool writeDWord(const uint32_t address, const uint32_t data)
{
    return(WriteProcessMemory(hDF, (void *) address, &data, 4, 0));
}

It is all typically stuff we do when we hack games, it is just rare we have to add stuff that the game will want to free later So now I am studying the internat heap structure of MSVC 2010 and how to add my own allocations to it, lol.

[forsaken1111]

So why it worked for forsaken?

The test file worked for me. He didn't distribute the actual application.