Print

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

[timmeh]

This is awesome, thanks!

Quick suggestion though, specify the river type, if that's possible.  I.E. Only return sites with a major river.

Maybe waterfalls too, although that would likely be difficult, since you can't see those from the embark screen, so far as I know...

[Lamp]

Quick suggestion though, specify the river type, if that's possible.  I.E. Only return sites with a major river.

Maybe waterfalls too, although that would likely be difficult, since you can't see those from the embark screen, so far as I know...

Rivers may be hard, especially if people are using graphics sets, because GFX would have to find a way to determine the picture the rivers use for everyone. Waterfalls may not be too hard, once rivers work atleast. It would just have to find where the river is on the embark, check the elevation and if there was a large difference from 2 points on the river, there would most likely be a waterfall.

On another note, GFX if you re-vamped the search so that it fully checks every place in the map for the features I would love you forever.

EDIT: Few minor problems with v2.8 (As follows is a journal of my bad luck)

Spoiler (click to show/hide)

First test, I left it on for 10 minutes and came back to an embarked map, and before hand I had deleted everything in my save folder, so I don't know what went wrong there.

Next test it genned a world, got back to the main menu, and then didn't do anything else.

And the final time It generated 2 worlds, first world turned up with nothing good in it, so it goes and generates a second world. After the world is generated, it goes back to the main menu and then proceeds to start an adventurer.

By this time I figured the key delay was too short, so I set it to 300. This just caused it to pause generating a world a few seconds in. I tried it again at 200, still stopped just a little later. Set it back to 150, great it's still happening.

So, I re-download it. It starts working fine again. Wait, hold on, we're back to the second problem, it gens a world and then stops at the main menu.

Alright, 9th time's the charm. I got it to generate 6 worlds before it tried to make an adventurer again.

[timmeh]

Rivers may be hard, especially if people are using graphics sets, because GFX would have to find a way to determine the picture the rivers use for everyone. Waterfalls may not be too hard, once rivers work atleast. It would just have to find where the river is on the embark, check the elevation and if there was a large difference from 2 points on the river, there would most likely be a waterfall.

It already asks if you're using a graphics set, so I would guess that GFX is already checking at least some of the letters in this way.  Even if not, depending on how he's writing it (didn't notice a programming language, wasn't really looking for it though) there may be a way to pull a section out of the graphic sheet and check it against the screen.  Again, I don't know how it's being written so I can't be sure.

[Lamp]

Yeah I guess that's true.

I just realized something though, the in-game search almost always leaves you with at least some mountain, and the only kind of river you can get there is the smallest one, so it would take forever (Or be impossible) to find a different sized river...

If it's possible UltraFinder should be able to check which process has focus, so in case something pops up UltraFinder will pause so you can deal with it instead of having it spam what ever popped up.

Spoiler (click to show/hide)

I'm sorry, I'll stop telling you how to do your job now

[timmeh]

I just realized something though, the in-game search almost always leaves you with at least some mountain, and the only kind of river you can get there is the smallest one, so it would take forever (Or be impossible) to find a different sized river...

If it's possible UltraFinder should be able to check which process has focus, so in case something pops up UltraFinder will pause so you can deal with it instead of having it spam what ever popped up.

Good point....  maybe the major river thing is more of a request for ToadyOne....

I didn't have a problem with it, but then again I usually disable my anti-virus whenever I'm not either updating it or running a scan, so I don't typically have many popups...  Definitely a good idea though.

[GFXiNXS]

Quick suggestion though, specify the river type, -snip- Maybe waterfalls too...

I've actually looked into both of these and both pose a few problems with the programs current functionality. I'll explain further down.

It already asks if you're using a graphics set, so I would guess that GFX is already checking at least some of the letters in this way.

Heh, this was actually general slackness on my behalf (there is a lot of that in this program). It's lingering on from the alpha version when I didn't have the program properly scan your init file and I just got users to tell it instead. Consider it fixed for the next release.

The program doesn't scan your character set _at all_. I looked into getting it to read tile data, but it was pushing the boundaries of how far I was willing to take this program. At the moment, all it does is detect colour changes (hence why some shaded character sets + colour schemes make this program throw a hissy fit). This is also why "Haunted/Terrifying" are bundled in the same word group. They are both the same colour.

I can have the program identify what it "thinks" is a river but several conditions would have to be met like having the river span multiple tiles of the embark rectangle so that they show up blue on black, though you then face the problem of the program mixing up underground rivers with brooks etc.

Lamp got it right about elevation and rivers pertaining to instancing of waterfalls, though, again theres the problem in that the program would pull up underground rivers too. The only way around this would be to forcibly set underground rivers to "No" if such a feature was checked.

Though, perhaps that is a price people would be willing to pay.

Also, until (if ever) I scan individual tiles, finding specific river types looks like it is going to be out.

Yes, the inbuilt finder favours mountain sites, but users also seem to favour mountain biome features. If you set the program to turn out sites with only a river and a magma pipe with a sedimentary layer, for example, the majority of sites turned out are devoid of mountain tiles all together.

If it's possible UltraFinder should be able to check which process has focus, so in case something pops up UltraFinder will pause so you can deal with it instead of having it spam what ever popped up.

Another winning idea. Consider it in. I had Avira's evil popup interrupt my scan last night. That bastard.

And, as per your problems: if the program takes a wrong turn at any corner, it's missinterperated where Dwarf Fortress is at in the plethora of menus. As explained above, the program reads colour changes, so, if your tiles aren't of a 1:1 aspect (thus causing the interpolated pixels to throw my program off), contain shading, or you are using a colour scheme where the difference between two colours is too close the program simply runs blind. Rather than changing key delays etc, I'd be messing with your tileset and/or colour scheme.

On another note, GFX if you re-vamped the search so that it fully checks every place in the map for the features I would love you forever.

Yeah, again, sorry; this won't go in unless I scan the actual tiles from the character sets and given the impending release of the new Dwarf Fortress along with shortage-of-time factors in my life, this is a highly improbable eventuality.

Hopefully I covered everything. I appreciate the communities' input.


Cheers,

GFXiNXS

[Neyvn]

I was thinking, I am gonna attempt something on one world, problem is I need around 4 or 5 different sites, one on a volcano, one in a lake, one near the sea, one over a bottomless pit and another on the plains...

What if the Finder would allow you to search a pre gen map (like 10 already made) over and over again with those different settings without having to set up a world gen parameter. You know, Sorry if this lack of English makes no sense, came up with the thought at work and while I cool down afterwards, English don't come to me naturally, and I speak it as my first language...
Ugh, energy drain...

[Lamp]

I'm running 40d11, using mayday's graphics set.

Spoiler: Init (click to show/hide)

Change this to turn sound off.

[SOUND:OFF]

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

[VOLUME:255]

Change this to skip the wonderful intro movies.

[INTRO:OFF]

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 800x600 and the 800x600 font might make you happier.

[WINDOWEDX:640]
[WINDOWEDY:300]
[FONT:curses_640x300.png]

Full screen info.

[FULLSCREENX:800]
[FULLSCREENY:600]
[FULLFONT:curses_800x600.png]

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:NO]

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 September 2008, the Dwarf Fortress Wiki has graphical tilesets available at http://www.dwarffortresswiki.net/index.php/List_of_user_graphics_sets.

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

This is the dimensions in tiles of the display grid.  Minimum x is 80.  Minimum y is 25.  Maximums are 200.  Make sure the window size or full screen resolution matches the grid/tile size if you don't want the display to be squashed or stretched.  The default windowed font has tiles that are 8x12 pixels, for instance, so for a 80x25 grid, you use a 640x300 window, and for a 125x50 grid, you'd use a 1000x600 window.  FULLGRID is used in full screen mode, whether graphics is on or not.

[GRID:80:50]
[FULLGRID:80:64]

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 STANDARD, PARTIAL:<number>, ACCUM_BUFFER and FRAME_BUFFER.  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.

[PRINT_MODE:STANDARD]
[SINGLE_BUFFER:ACCUM_BUFFER]

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.

[FPS_CAP:120]

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

[G_FPS_CAP:25]

This sets the applications vertical synchronization behavior.  Changing this to ON can impact your FPS if your G_FPS is high.  The other options are ON and DEFAULT.  DEFAULT uses whatever settings you have your system at in general.

[VSYNC:OFF]

Change this to LINEAR if you want the texture values to be averaged over the adjacent pixels.

[TEXTURE_PARAM:NEAREST]

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:NORMAL]

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]

Use these to control the automatic saving behavior in the dwarf fortress mode of game.  AUTOSAVE can be set to NONE, SEASONAL or YEARLY.  This updates your save at these intervals, so that some of your progress will be saved in case of system instability.  You can set AUTOBACKUP to YES if you want the updated save to be copied to another folder so that you'll have several copies of your world at different times.  Set AUTOSAVE_PAUSE to YES if you want the game to pause every time it autosaves.

[AUTOSAVE:YEARLY]
[AUTOBACKUP:YES]
[AUTOSAVE_PAUSE:NO]

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 YES to make Dwarf Fortress start paused whenever you load an active game.

[PAUSE_ON_LOAD:NO]

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_RIVER:ALWAYS]
[SHOW_EMBARK_POOL:ALWAYS]
[SHOW_EMBARK_M_PIPE:ALWAYS]
[SHOW_EMBARK_M_POOL:ALWAYS]
[SHOW_EMBARK_CHASM:ALWAYS]
[SHOW_EMBARK_PIT:ALWAYS]
[SHOW_EMBARK_OTHER:ALWAYS]
[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]

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:6:6]

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:50]

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]

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:178:3:0:0]

As above, for inside/subterranean areas.

[CHASM:250:0:0:1]

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:90]

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:0:0]

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 have it show the history behind every engraving you view in dwarf mode, etc., then set this to YES.

[SHOW_ALL_HISTORY_IN_DWARF_MODE:YES]

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

[KEY_HOLD_MS:150]

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]

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:9]

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]

These are the display colors in RGB.  The game is actually displaying extended ASCII characters in OpenGL, so you can modify the colors.

[BLACK_R:0]
[BLACK_G:0]
[BLACK_B:0]
[BLUE_R:73]
[BLUE_G:95]
[BLUE_B:157]
[GREEN_R:89]
[GREEN_G:117]
[GREEN_B:55]
[CYAN_R:101]
[CYAN_G:144]
[CYAN_B:158]
[RED_R:146]
[RED_G:0]
[RED_B:0]
[MAGENTA_R:165]
[MAGENTA_G:54]
[MAGENTA_B:101]
[BROWN_R:138]
[BROWN_G:105]
[BROWN_B:59]
[LGRAY_R:128]
[LGRAY_G:128]
[LGRAY_B:128]
[DGRAY_R:80]
[DGRAY_G:80]
[DGRAY_B:80]
[LBLUE_R:111]
[LBLUE_G:138]
[LBLUE_B:165]
[LGREEN_R:160]
[LGREEN_G:200]
[LGREEN_B:82]
[LCYAN_R:159]
[LCYAN_G:196]
[LCYAN_B:210]
[LRED_R:206]
[LRED_G:73]
[LRED_B:1]
[LMAGENTA_R:239]
[LMAGENTA_G:150]
[LMAGENTA_B:207]
[YELLOW_R:255]
[YELLOW_G:198]
[YELLOW_B:0]
[WHITE_R:255]
[WHITE_G:255]
[WHITE_B:255]

Using "Another Colour Scheme", none of the display settings for Mayday were changed, other then the print mode.
It worked fine on v2.6, except I had to change my colour scheme to default whenever I wanted to use the program.

Spoiler: More Brain Diarrhea (click to show/hide)

If you ever do implement the full scanner, it would be awesome, yes, but also more efficient. Mostly because the default scanner only shows up with ONE match, while if you had your own scanner it could leave a note at any embark that meets your requirements.

Hey, who here remembers that old program for searching maps, regional prospector? GFX, if you ever get bored, try and get in contact with the guy who made it(I think it was 0x517A5D), he may divulge the source code and all you would have to do at that point is merge and update for 40d#. (Or at least use it as a reference)

Oh, and with what Neyvn said, I guess it could be useful to load multiple settings files, as in it scans using one setting, then again with the other one(s).

[GFXiNXS]

Still have yet to test out your problems, Lamp. I haven't been home in a few days, but I should get back some time this weekend and I'll test it out then. I apologise for any frustration you may be experiencing

Multiple init files is definately doable. I'll just need to get the user to create UlltraFinder_Init_2.txt etc and it'll cycle through.

And yeah, I remember good old regional prospector. I believe its functionality was partially derived from an image based search which meant you had to be using the default tileset in order for it to work. This comes back to me having to call up specific tiles and it's just a matter of finding a simple enough way to do so. One of the biggest problems is, once I have called up the right tile from data\art, I then have to get the colour right. Eg. A magma pipe with the embark rectangle over it is red on black, whilst without the embark rectangle over it, it is black on brown and I'd have to factor in the shading on each tile, too.

Once that is done, the rest will come easy, though it'd be a lot of work to get to that point. It'd also make more advanced searches a hell of a lot more tangible, things like oceanside forts with magma pipes etc.

I'll likely try and wrap up the current feature set before even attempting such a big move, so I wouldn't hold your breath.

Cheers guys

[uran77]

does it work with d13?

[GFXiNXS]

It should work with 40d and everything above

[Criptfeind]

I know that that this has been mentioned before, but the fixes for it are not working for me. It is saying:

Spoiler (click to show/hide)

Error: Failed attempt to launch program or document:
Action <Dwarf Fortress.exe>
Params: <>

The current thread will exit.

Specifically: the system cannot find the file specified.

   Line#
--->   008: Run,Dwarf Fortress.exe

But the file is named Dwarf Fortress.exe I even tried DwarfFortress.exe, dwarffortress.exe, Dwarf Fort.exe, and Dwarf Fort.

But it does not work on any.

Also here is a snap shot of my directory.

Spoiler (click to show/hide)

2.6 is not in the shot but i have tryed it on that as well.

Here is my int

Spoiler (click to show/hide)

Change this to turn sound off.

[SOUND:ON]

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

[VOLUME:255]

Change this to skip the wonderful intro movies.

[INTRO:OFF]

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 800x600 and the 800x600 font might make you happier.

[WINDOWEDX:640]
[WINDOWEDY:300]
[FONT:curses_640x300.bmp]

Full screen info.

[FULLSCREENX:800]
[FULLSCREENY:600]
[FULLFONT:curses_800x600.bmp]

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:NO]

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 September 2008, the Dwarf Fortress Wiki has graphical tilesets available at http://www.dwarffortresswiki.net/index.php/List_of_user_graphics_sets.

[GRAPHICS:NO]
[GRAPHICS_WINDOWEDX:1280]
[GRAPHICS_WINDOWEDY:400]
[GRAPHICS_FONT:curses_square_16x16.bmp]
[GRAPHICS_FULLSCREENX:1280]
[GRAPHICS_FULLSCREENY:800]
[GRAPHICS_FULLFONT:curses_square_16x16.bmp]
[GRAPHICS_BLACK_SPACE:YES]

This is the dimensions in tiles of the display grid.  Minimum x is 80.  Minimum y is 25.  Maximums are 200.  Make sure the window size or full screen resolution matches the grid/tile size if you don't want the display to be squashed or stretched.  The default windowed font has tiles that are 8x12 pixels, for instance, so for a 80x25 grid, you use a 640x300 window, and for a 125x50 grid, you'd use a 1000x600 window.  FULLGRID is used in full screen mode, whether graphics is on or not.

[GRID:80:25]
[FULLGRID:80:25]

Change this to YES to only refresh portions of the screen that need to be refreshed.  This can have a significant impact on frame rate, especially for people that have slow frame rates on the title screen.  The number refers to how many frames it will redo a printed tile before skipping it, so you might try increasing it a bit.  PARTIAL_PRINT only works on certain systems, so you might have to disable it again if you notice your display isn't working properly.  Fixes are being investigated.

[PARTIAL_PRINT:No:2]

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:NO]

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.

[FPS_CAP:100]

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

[G_FPS_CAP:30]

This sets the applications vertical synchronization behavior.  Changing this to ON can impact your FPS if your G_FPS is high.  The other options are ON and DEFAULT.  DEFAULT uses whatever settings you have your system at in general.

[VSYNC:OFF]

Change this to LINEAR if you want the texture values to be averaged over the adjacent pixels.

[TEXTURE_PARAM:NEAREST]

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:NORMAL]

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]

Use these to control the automatic saving behavior in the dwarf fortress mode of game.  AUTOSAVE can be set to NONE, SEASONAL or YEARLY.  This updates your save at these intervals, so that some of your progress will be saved in case of system instability.  You can set AUTOBACKUP to YES if you want the updated save to be copied to another folder so that you'll have several copies of your world at different times.  Set AUTOSAVE_PAUSE to YES if you want the game to pause every time it autosaves.

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

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 YES to make Dwarf Fortress start paused whenever 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:NO]

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_RIVER:ALWAYS]
[SHOW_EMBARK_POOL:ALWAYS]
[SHOW_EMBARK_M_PIPE:ALWAYS]
[SHOW_EMBARK_M_POOL:ALWAYS]
[SHOW_EMBARK_CHASM:ALWAYS]
[SHOW_EMBARK_PIT:ALWAYS]
[SHOW_EMBARK_OTHER:ALWAYS]
[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:YES]
[WEATHER:NO]
[ECONOMY:YES]
[INVADERS:YES]
[CAVEINS:YES]
[ARTIFACTS:YES]
[ZERO_RENT:NO]

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

[LOG_MAP_REJECTS:YES]

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:3:3]

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:YES]

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:178:3:0:0]

As above, for inside/subterranean areas.

[CHASM:250:0:0:1]

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:20]

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:NO]

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 have it show the history behind every engraving you view in dwarf mode, etc., then set this to YES.

[SHOW_ALL_HISTORY_IN_DWARF_MODE:YES]

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

[KEY_HOLD_MS:150]

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]

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:9]

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]

These are the display colors in RGB.  The game is actually displaying extended ASCII characters in OpenGL, so you can modify the colors.

[BLACK_R:0]
[BLACK_G:0]
[BLACK_B:0]
[BLUE_R:0]
[BLUE_G:0]
[BLUE_B:128]
[GREEN_R:0]
[GREEN_G:128]
[GREEN_B:0]
[CYAN_R:0]
[CYAN_G:128]
[CYAN_B:128]
[RED_R:128]
[RED_G:0]
[RED_B:0]
[MAGENTA_R:128]
[MAGENTA_G:0]
[MAGENTA_B:128]
[BROWN_R:128]
[BROWN_G:128]
[BROWN_B:0]
[LGRAY_R:192]
[LGRAY_G:192]
[LGRAY_B:192]
[DGRAY_R:128]
[DGRAY_G:128]
[DGRAY_B:128]
[LBLUE_R:0]
[LBLUE_G:0]
[LBLUE_B:255]
[LGREEN_R:0]
[LGREEN_G:255]
[LGREEN_B:0]
[LCYAN_R:0]
[LCYAN_G:255]
[LCYAN_B:255]
[LRED_R:255]
[LRED_G:0]
[LRED_B:0]
[LMAGENTA_R:255]
[LMAGENTA_G:0]
[LMAGENTA_B:255]
[YELLOW_R:255]
[YELLOW_G:255]
[YELLOW_B:0]
[WHITE_R:255]
[WHITE_G:255]
[WHITE_B:255]

[GFXiNXS]

That... is just plain wierd. Your snapshot clearly depicts that everything as it should be, and your init.txt shouldn't really be part of the problem.

Perhaps you could offer up your operating system and your dwarf fortress version as well?

Technically, seeing as it is clearly in the same directory, and clearly has the appropriate name, it should at least run. The only thing I can think of is that perhaps your full directory listing contains some funky characters like My Docs\£¥Ú»╚\My Games\Dwarf Fortress\.

Either that, or if you are running Vista, and have the dwarf fortress directory listed under Program Files, you may want to try moving it to a different location.

Cheers

[Criptfeind]

I am not vary computer savvy so I may be wrong, but I think my operating system is:
Vista
Processor: AMD Phenom(tm) 9100e quad-core processor 1.80 GHz
RAM: 4.00 GB
64-bit operating system.

It is under:
Family>Documents>Dwarf Fort>DDF

[GFXiNXS]

Alright... doing some reading would show that some users of AutoHotKey (the program I used to make this application) in conjunction with Vista 64, encounter problems when running with UAC on (User Account Control).

There is a tutorial on disabling it here: http://www.howtogeek.com/howto/windows-vista/disable-user-account-control-uac-the-easy-way-on-windows-vista/

It can also be re-enabled in the same way, though I'm not sure about how far you are willing to go in order to get this thing to run. It's a rather extreme measure, but this is the first instance of this problem that I've really seen come up, so I'm grasping as straws.

Failing that, you could try running it from a different location, say, C:\Dwarf Fortress\, but I really don't think that will help.

Heh, I'm at work, so it's hard to properly troubleshoot, sorry.