Print

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

[Cyntrox]

are there any other things you folks would like to see added?

The ability to load the available options from a file (xml?) would be great. That way it doesn't have to be recompiled with new releases just for adding new options.

Other than that, great work!

[LucasUP]

Cool beans dude! Glad you can get to updating this again.

Unfortunatley I'm getting the error about missing COMDLG32.OCX or one if its dependencies. I'd occasionaly get a similiar issue with the other version, but it would work most of the time (and almost always when running in admin mode). Not so with this new version.

I'm running Windows Vista 64, and I have the latest VC x86 and x64 redistributables as far as I know.

Argh. Comdlg32 is a 'common' control for the file select dialog; what's so common about it when it has to be manually included is beyond me.  Also what the heck that file doesn't even exist on my computer.
I will find a copy and add it to the package. And hope it works.

Nice, it works! You still need to run in admin mode in vista, for anyone else having problems.

[thebigJ_A]

Hey, I just DL'd Phoebus' tileset along with DF .16. Then I downloaded this. A few odd things are happening.

When I go to save the settings, I get two error messages. One says "RESIZABLE was never loaded" and not to worry, it had been put back. The next is the same, but it says [:0] was put back.

The next thing worries me more. When I go to launch DF through DFinit, there's a popup asking if I want to rub un fullscreen (even though I have windowed toggled, and prompt untoggled). Whether I say yes or no, another error pops up saying "tileset not found" for the tileset curses_640x300.png.

Looking in the data/art folder, that tileset is there. Regardless, I'm using the Phoebus tileset.

The game launches when I start it directly, but this has me worried something is messed up. When I got .12 through the Lazy Newb Pack, everything worked fine, aside from the truetype message (which oddly isn't appearing anymore).

[xnrad]

Hey, I just DL'd Phoebus' tileset along with DF .16. Then I downloaded this. A few odd things are happening.

When I go to save the settings, I get two error messages. One says "RESIZABLE was never loaded" and not to worry, it had been put back. The next is the same, but it says [:0] was put back.

The next thing worries me more. When I go to launch DF through DFinit, there's a popup asking if I want to rub un fullscreen (even though I have windowed toggled, and prompt untoggled). Whether I say yes or no, another error pops up saying "tileset not found" for the tileset curses_640x300.png.

Looking in the data/art folder, that tileset is there. Regardless, I'm using the Phoebus tileset.

The game launches when I start it directly, but this has me worried something is messed up. When I got .12 through the Lazy Newb Pack, everything worked fine, aside from the truetype message (which oddly isn't appearing anymore).

Could I possibly see the init files you are using? I just opened the hood and resizable looks no different from all the other load/save functions. It almost sounds like your resizable value got borked and looks like
[RESIZABLE
:YES]
or something strange like that and I would like to see what makes my program throw up all over itself so I can perhaps add a bib.
Also, you just reminded/inspired me to add a label stating which directory DFInit is working in, as it doesn't necessarily have to be working in the DF folder it is currently in. It may be trying to mess with another directory entirely, yielding these errors.

[LucasUP]

I don't know if this helps, but I've gotten the "tileset not found" error before. It happened with my batch files "run DF" command AS WELL AS running DFInit through the batch file and then clicking "launch DF".
The problem was something to do with the batch file trying to run the program without actually changing its current working directory. It was as if DF launched but it didn't know what directory it was supposed to be in (and where its supporting files were!).

Everything was fixed when I explicitly told the batch file to CHANGE DIRECTORY to where DF is, and THEN launch the .exe

Didn't work:

Code: [Select]

START "" "Dwarf Fortress 31.14\Dwarf Fortress.exe"
Worked:

Code: ( Worked) [Select]

SET dfDir=Dwarf Fortress 31.14
...
CD %dfDir%
START "" "Dwarf Fortress.exe"

[thebigJ_A]

Lucas, hitting the change directory button worked, I can now launch the game through DFinit.

I still get the errors when I save, though. Xnrad, I've got two sets on inits, the rgular ones, and ones that came with Phoebus (called init.phoebus and d_init.phoebus). I'll assume you want the regular ones, though idk which the game uses.

Here's the init:

Spoiler (click to show/hide)

WARNING: Do NOT copy over the init.txt from an earlier version of DF.
Always read the file carefully, including the comments.

In general, you can copy savegames and tilesets from older DF
versions, but you should not copy anything else.  You should not, under any
circumstances, unpack a new DF on top of an older one.


Change this to turn sound off.

[SOUND:YES]

The sound volume runs from 0 (off) to 255 (full).  You can set the volume from the ESC options menu as well.

[VOLUME:100]

Change this to skip the wonderful intro movies.

[INTRO:NO]

This lets you set the starting windowed/fullscreen setting.  Can be YES, NO or PROMPT.

[WINDOWED:YES]

This is the size and font for windowed mode.  Changing to the 800x600 font might make you happier.
If set below 256x256 it specifies the grid size instead, with a minimum of 80x25.

[WINDOWEDX:0]
[WINDOWEDY:0]
[FONT:Phoebus_16x16.png]

You may disable window resizing if you wish.
[RESIZABLE:YES]

Full screen info.  The 0s below mean that the game will choose a resolution for you, but you can set it yourself as well.

[FULLSCREENX:0]
[FULLSCREENY:0]
[FULLFONT:Phoebus_16x16.png]

If this is set to NO, tiles will be stretched to fit the screen if there is a resolution mismatch.
If this is set to YES, the tiles will not be stretched, but rather the game view will be centralized, surrounded by black space.  Tiles that are too large will always be compressed rather than running off the screen.

[BLACK_SPACE:YES]

Graphics info, most of it as above.  Set GRAPHICS to YES to turn it all on.  This will use the "raw/graphics" folder for tile information.  Currently this is limited to whatever creature graphics you have downloaded.  The game comes with a few pictures to demonstrate.  As of October 2010, the Dwarf Fortress Wiki has custom tilesets available at http://df.magmawiki.com/index.php/Tileset_repository and creature graphics at http://df.magmawiki.com/index.php/Graphics_set_repository.

[GRAPHICS:YES]
[GRAPHICS_WINDOWEDX:1280]
[GRAPHICS_WINDOWEDY:800]
[GRAPHICS_FONT:Phoebus_16x16.png]
[GRAPHICS_FULLSCREENX:800]
[GRAPHICS_FULLSCREENY:600]
[GRAPHICS_FULLFONT:Phoebus_16x16.png]
[GRAPHICS_BLACK_SPACE:YES]

These settings can have a significant impact on frame rate, especially for people that have slow frame rates on the title screen.  Available modes are 2D, 2DSW, 2DASYNC, STANDARD, PARTIAL:<number>, ACCUM_BUFFER, FRAME_BUFFER and VBO. The number after PARTIAL refers to how many frames it will redo a printed tile before skipping it, so you might try increasing it a bit if you have flickering when PARTIAL is set.  Please note that any of these combinations might cause frame rates to drop significantly or cause unpleasant side effects like flickering.

By and large, 2D should be the most reliable, while STANDARD has a good combination of speed and reliability. However, all 2D modes are normally far slower than even STANDARD, which may be the slowest OpenGL mode.

2DASYNC may be slightly more responsive than 2D on a multi-core machine, but this has recently become doubtful due to improvements to the other modes.

Linux/OS X users may also use PRINT_MODE:TEXT for primitive ncurses output.

[PRINT_MODE:STANDARD]
   Mode examples:
    PRINT_MODE:2D
    PRINT_MODE:TEXT
    PRINT_MODE:FRAME_BUFFER
    PRINT_MODE:PARTIAL:0
[SINGLE_BUFFER:YES]

Change this to YES if you want to experiment with the TrueType font support that is currently in progress.  It only works in the 2D print mode set above.

[TRUETYPE:NO]

Change this to YES to keep the DF window on top of your other windows.

[TOPMOST:NO]

Change this to YES if you want to see an FPS counter at the top left.

[FPS:YES]

Use this to set the maximum frame rate during play.  The movies are always capped at 100.  A frame in this case is not graphical but related to the movement speed of a creature.  A healthy, unencumbered dwarven peasant takes one step every 10 frames.

You may set FPS_CAP to 0 to make it uncapped.

[FPS_CAP:100]

Use this to set the maximum graphical frame refresh rate during play.

[G_FPS_CAP:25]

On cards that support the OpenGL ARB_sync extension, turning this on can improve framerates in GPU overload conditions. It defaults to NO, as many cards that claim to support this will crash if asked to do so.

[ARB_SYNC:NO]

This sets the applications vertical synchronization behavior.  Changing this to YES can impact your FPS if your G_FPS is high. ARB_SYNC is a better option, if your system supports it.

[VSYNC:NO]

Change this to NEAREST if you want the texture values to use the nearest pixel without averaging.
Change this to LINEAR if you want the texture values to be averaged over the adjacent pixels.

[TEXTURE_PARAM:LINEAR]

Change this to make the dwarfort.exe process have a different priority.  From highest to lowest, the options are REALTIME, HIGH, ABOVE_NORMAL, NORMAL, BELOW_NORMAL and IDLE.

[PRIORITY:HIGH]

Use this to set how fast the game zooms.  The default corresponds to
increasing grid size by 10 units each time you zoom.

[ZOOM_SPEED:10]

Change this to NO if you don't want to have the mouse involved at all.

[MOUSE:YES]

Change this to YES if you'd like to use a BMP for the mouse cursor.  The image currently lags when the game is lagging however.

[MOUSE_PICTURE:NO]

This controls the number of milliseconds that must pass before a held key sends an initial repeat press to the game.  You might need to adjust this.

[KEY_HOLD_MS:250]

This controls the number of milliseconds that must pass before a held key sends a repeat press to the game after the repeat process has begun.

[KEY_REPEAT_MS:150]

If you set KEY_REPEAT_ACCEL_LIMIT above one, then after KEY_REPEAT_ACCEL_START repetitions the repetition delay will smoothly decrease until repetition is this number of times faster than at the start.

[KEY_REPEAT_ACCEL_LIMIT:8]
[KEY_REPEAT_ACCEL_START:10]

This controls the number of milliseconds between macro instructions.

[MACRO_MS:15]

This controls the number of milliseconds that must pass before input works again after the view recenters on an event in dwarf mode.

[RECENTER_INTERFACE_SHUTDOWN_MS:0]

Change this to NO if you want to leave save uncompressed (you might want to do this if you are experience save corruption).

[COMPRESSED_SAVES:YES]

and d_init:

Spoiler (click to show/hide)

[AUTOSAVE:SEASONAL]
[AUTOBACKUP:YES]
[AUTOSAVE_PAUSE:YES]

Set this to YES if you want it to save the game when you start a new fortress.  If AUTOBACKUP above is set to YES, it will also create a copy of this new save.

[INITIAL_SAVE:YES]

Set this to NO to make Dwarf Fortress remain in the saved pause state when you load an active game.

[PAUSE_ON_LOAD:YES]

Set this to YES if you want Dwarf Fortress to show the warning window on embark as a confirmation even if there are no issues.

[EMBARK_WARNING_ALWAYS:YES]

You can change these to ALWAYS and NO.  More restrictive world parameter settings override these.  ALWAYS lets you see the features in the Local view during embark, and NO stops you from looking for features in the site finder (though if you really want to stop the finder, it might be better for you to generate worlds that restrict the use of this feature completely, in which case you don't need to change the settings here).

[SHOW_EMBARK_TUNNEL:ALWAYS]

Use these options to remove features from the game.  Permitted values are YES and NO.  Removal might speed the game up in the case of temperature and weather.

[TEMPERATURE:NO]
[WEATHER:NO]
[ECONOMY:NO]
[INVADERS:YES]
[CAVEINS:YES]
[ARTIFACTS:YES]
[ZERO_RENT:NO]
[TESTING_ARENA:YES]
[RESIZABLE:0]
[:0]

Change this to YES to output the reasons for world map rejection into a file.

[LOG_MAP_REJECTS:NO]

Change these numbers to make the embark rectangle start at a different size.  The format is (EMBARK_RECTANGLE:<width>:<height>).  Numbers may run from 2 to 16.  The map size warning message will go by these numbers.

[EMBARK_RECTANGLE:4:4]

Change these numbers to set the default weights for traffic designations.  If you make the last numbers too large, pathfinding might lag.
The format is (PATH_COST:<high>:<normal>:<low>:<restricted>).

[PATH_COST:1:2:5:25]

Alter these options to control how aggressively your dwarves place objects in a container with like items (rather than an empty container).  The default options are very aggressive.  STORE_DIST_ITEM_DECREASE controls the cap on objects it will consider -- for each object it finds in a container, one tile is removed from its apparent distance to the dwarf, up to this cap.  The others control how many tiles are removed for each combination type for any match at all.  For instance, if ITEM_DECREASE is set to 20, and SEED_COMBINE is set to 100, a dwarf carrying seeds will see a seed bag with 15 seeds as 115 tiles closer than it actually is (and thus pass up any empties within that distance), whereas a seed bag with 30 seeds would be treated as 120 tiles closer (because it hits the ITEM_DECREASE cap).  Values from 2 to 1000 are permitted.  Before these init options, the behavior was roughly ITEM_DECREASE 2, SEED_COMBINE 2 and the rest at 1000.

[STORE_DIST_ITEM_DECREASE:20]
[STORE_DIST_SEED_COMBINE:1000]
[STORE_DIST_BUCKET_COMBINE:1000]
[STORE_DIST_BARREL_COMBINE:1000]
[STORE_DIST_BIN_COMBINE:1000]

Change this to YES to disallow pets from coffin burial as the default option.

[COFFIN_NO_PETS_DEFAULT:NO]

Use these to set the color of wounded body parts.  The format is <foreground color>:<background color>:<brightness>.

[WOUND_COLOR_NONE:7:0:1]
[WOUND_COLOR_MINOR:6:0:0]
[WOUND_COLOR_INHIBITED:6:0:1]
[WOUND_COLOR_FUNCTION_LOSS:3:0:1]
[WOUND_COLOR_BROKEN:4:0:1]
[WOUND_COLOR_MISSING:0:0:1]

This controls the display of areas that are far below outside.  The format is SKY:<character>:<foreground color>:<background color>:<brightness>.  The <character> can be either an ASCII tile number or a character in quotes, like '#'.

[SKY:255:7:0:1]

As above, for inside/subterranean areas.

[CHASM:255:0:0:1]

Pillar tile, <character> as above.

[PILLAR_TILE:199]

This controls the "IDLERS: <number>" that is displayed in dwarf mode.  You can set it to TOP, BOTTOM or OFF.

[IDLERS:TOP]

You can set the maximum population of your fortress here.  Keep in mind that your population must be at least 80 to get a king and 100 to obtain the current game features.

[POPULATION_CAP:200]

This allows you to control the number of babies+children in your fortress.  The first number is an absolute cap on the number of babies+children.  The second is a percentage of the current number of adults in your fortress (the default is the essentially meaningless 1000% here).  The lower number is used as the cap.  The cap only prevents further pregancies, so migrant children, multiple births and existing pregnancies from old saves can still push you over the cap.  Setting either number to zero will disallow pregnancies in the fortress.

[BABY_CHILD_CAP:100:1000]

If you don't like the ,.`' ground, try setting this to NO.  The ground will turn into periods only.

[VARIED_GROUND_TILES:YES]

If you'd like your engravings to start off looking the same (you can toggle them on individual later), set this to YES.

[ENGRAVINGS_START_OBSCURED:YES]

If you get annoyed by seeing items like *<*sword*>* you can
get rid of the outside ** by setting this to NO.

[SHOW_IMP_QUALITY:YES]

Set this to YES to display fluids as numbers indicating depth.

[SHOW_FLOW_AMOUNTS:YES]

If you'd prefer to leave the history behind every engraving for your adventurers to discover, then set this to NO.

[SHOW_ALL_HISTORY_IN_DWARF_MODE:YES]

This controls "more" in adventure mode.  If MORE is set to NO, all announcements will be skipped.  DISPLAY_LENGTH controls how many lines are printed before it gives you the "more" prompt.

[MORE:YES]
[DISPLAY_LENGTH:23]

Set this to YES if you want traps to affect you in adventure mode.  This is not recommended -- there are lockup issues with cage traps, and you cannot disarm any of the traps yet, so they effectively stops you from exploring your old fortresses.

[ADVENTURER_TRAPS:NO]

Set this to NO if you want the game to recenter on your adventurer only when you've gotten close to the edge of the view.

[ADVENTURER_ALWAYS_CENTER:YES]

This controls the up/down views in adventure mode.  The first parameter can be OFF, UNHIDDEN, CREATURE or ON.  UNHIDDEN makes the view appear when it contains any unhidden square.  CREATURE makes the view appear when it contains a creature.  The second parameter is the size of the view.  It can be 3, 5, 7 or 9.  A smaller view lets it stack more of them in the column (3 at size 5, and 5 at size 3).

[ADVENTURER_Z_VIEWS:UNHIDDEN]

You can use these to say how nicknames are displayed in each mode
Options are REPLACE_FIRST, CENTRALIZE (between first and last), REPLACE_ALL
[NICKNAME_DWARF:REPLACE_FIRST]
[NICKNAME_ADVENTURE:REPLACE_FIRST]
[NICKNAME_LEGENDS:REPLACE_FIRST]

[xnrad]

[TEMPERATURE:NO]
[WEATHER:NO]
[ECONOMY:NO]
[INVADERS:YES]
[CAVEINS:YES]
[ARTIFACTS:YES]
[ZERO_RENT:NO]
[TESTING_ARENA:YES]
[RESIZABLE:0]
[:0]

So it turns out I omitted the letter 'D' from the code handling the new spatter options.

[thebigJ_A]

[TEMPERATURE:NO]
[WEATHER:NO]
[ECONOMY:NO]
[INVADERS:YES]
[CAVEINS:YES]
[ARTIFACTS:YES]
[ZERO_RENT:NO]
[TESTING_ARENA:YES]
[RESIZABLE:0]
[:0]

So it turns out I omitted the letter 'D' from the code handling the new spatter options.

I don't... what?

[SolarShado]

Misspelled variable name? AFAIK VB's pretty loose about the "declare before first use" thing. (I could be completely wrong, never much used VB.)

[thebigJ_A]

I don't understand. You just made part of the init I sent you bold. I know those lines are in there, that's what makes the error message strange.

[xnrad]

I highlighted it because that's what tipped me off to what was going wrong.

ahem

The array that holds init.txt is called iniArray; d_init's is DiniArray.
While saving, for each line in each init file, it looks for a number in column 10, which gets assigned the line number during loading when the line in question has an editable value. This was done to separate the values from the rest of the text.
If it finds a number in line x, column 10, it begins a big case statement to match the value it's looking at, so it can save from the proper text box/checkbox/dropdown menu.
For the spatter options, I thought they belonged to init.txt, so I omitted the D, thus resulting in that statement looking at the wrong array and getting resizable and a blank line instead of dwarfspatter and adventurespatter.


tl;dr I had a brain fart while programming.

[SolarShado]

I love being right (even if it was for the wrong reason)

[thebigJ_A]

Ah, I get it now.

Well, at least it's nothing major. I mean, blood tracking is off by default in fortress mode anyway, and I doubt its somethng people would change often. Glad I could help with this quite useful utility.

Now, if only someone could make something like Therapist for the military, I'd have everything I need (aside from a better processor on my pc!  ).

[xnrad]

OK then, I have finally received my gaming laptop, which comes with Win7 64bit and I now see what issues you people have been going through. I will do my best to fix these and deliver the DFInit experience as it was originally intended.

[daveftw]

Hi, I noticed a small bug in 1.53, dunno how far back it goes.  On initial startup, when DFInit asks for the Dwarf Fortress directory, canceling the open file dialog causes an alert box to pop up: "Can't save or load or do anything useful until DF folder is located."  When you click OK, the open file dialog is displayed again.  If you close the alert box window, DFInit's main window displays, but the program hangs.  It seems like closing the alert box should terminate the program instead.  Just my two cents, good program otherwise!