Print

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

[Regal]

After a pretty long hiatus, I've been getting back into the game again, and have liked the changes I've seen so far. However, the version of LNP I've been using did not include DFHack (which I believe it previously did, at least a couple years ago). I got along without it for a while, but I decided I had some need for the reveal function and downloaded the most recent version of DFHack. I extracted the .zip into my Dwarf Fortress folder, but DFHack doesn't show up on startup, whether I launch directly or through the LNP.

It's probably something obvious, but I'm honestly not really knowledgeable about computers and I don't know what to do. The DFHack readme said something about overwriting SDL.dll, but it doesn't look like anything happened to that file, if it matters. Should DFHack be within its own folder inside of my DF folder (which is what happens when I simply extract it into the DF folder as the readme says to do), or should I move the files out into the DF folder itself? Is there any other place it would have to go? Do I need to delete SDL.dll for it to work properly? If it helps, I'm certain that the versions are the same (0.34.11 for both), and like I said, I'm using Lazy Newb Pack too. Thanks in advance for any help.

[jwest23]

From your description of the problem, it sounds like what you need to do is just extract it slightly differently.

If you open up the dfhack folder in your df directory, I'm assuming you'll see at least an SDL.dll and SDLreal.dll in there.  When dfhack is installed properly, these files will be in your df folder instead of a sub-folder.

If my assumption is correct, you should be able to remove the current dfhack folder.  Then, extract the zip again.  In the "Select a Destination and Extract Files" dialog it will default to a folder that ends in "dfhack-0.34.11-r2-Windows".  Don't use that.  Instead, point it directly to your df folder. 

If you do this, then you should end up with a warning that it's going to replace SDL.dll.  That's what you want to see.

Hope this helps!