Print

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

Faster than 40d, no problems

42 (26.1%)

Faster than 40d, problems

72 (44.7%)

No slower than 40d, no problems

14 (8.7%)

No slower than 40d, problems

16 (9.9%)

Slower than 40d, no problems

2 (1.2%)

Slower than 40d, problems

3 (1.9%)

Doesn't work (please explain)

12 (7.5%)

Total Members Voted: 160

[Peewee]

DJDD: This thread is specifically for bugs in the 40d# versions. Bugs related to gameplay still go in the bug reports forum.

[Baughn]

Right, that's it. I'm moving the project over to github; the bandwidth's better, and this thread does not make a good bug-tracker anymore, if it ever did.

Anyone with a bug, try to register it in http://github.com/Baughn/Dwarf-Fortress--libgraphics-/issues. I'll try to register those I find, but I could easily miss something.

Veroule, from now on, please push to there. You'll need to make an account before I can add you as a contributor, though.

[Shoku]

I'm confused. We're not posting in the designated DF Bug Reports forum?

On another note. Maydays latest MIX tileset doesn't appear to work properly. Dwarfs appear to each have been dipped into a primary color of paint. It could be that they're trying to a new tactic to scaring away Carp, but I sermise that such folly could not be the work of my Dwarves. Needless to say, it is how it is...
D12:


D13:


D13 INIT:

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:1888]
[WINDOWEDY:1152]
[FONT:maydayMIN.bmp]

Full screen info.

[FULLSCREENX:1280]
[FULLSCREENY:1024]
[FULLFONT:maydayMIN.bmp]

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: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:1888]
[GRAPHICS_WINDOWEDY:1152]
[GRAPHICS_FONT:maydayMIX.bmp]
[GRAPHICS_FULLSCREENX:1280]
[GRAPHICS_FULLSCREENY:1024]
[GRAPHICS_FULLFONT:maydayMIX.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:118:72]
[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, 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.

[PRINT_MODE:STANDARD]
[SINGLE_BUFFER: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.

[FPS_CAP:100]

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

[G_FPS_CAP:20]

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 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: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:NONE]
[AUTOBACKUP:NO]
[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:NO]

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

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

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

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

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]

This controls the number of milliseconds between macro instructions.

[MACRO_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:30]
[BLUE_G:50]
[BLUE_B:168]

[GREEN_R:60]
[GREEN_G:128]
[GREEN_B:0]

[CYAN_R:0]
[CYAN_G:128]
[CYAN_B:140]

[RED_R:200]
[RED_G:20]
[RED_B:0]

[MAGENTA_R:128]
[MAGENTA_G:50]
[MAGENTA_B:200]

[BROWN_R:140]
[BROWN_G:98]
[BROWN_B:56]

[LGRAY_R:192]
[LGRAY_G:192]
[LGRAY_B:192]

[DGRAY_R:128]
[DGRAY_G:128]
[DGRAY_B:128]

[LBLUE_R:0]
[LBLUE_G:120]
[LBLUE_B:255]

[LGREEN_R:170]
[LGREEN_G:255]
[LGREEN_B:0]

[LCYAN_R:0]
[LCYAN_G:200]
[LCYAN_B:255]

[LRED_R:255]
[LRED_G:50]
[LRED_B:0]

[LMAGENTA_R:210]
[LMAGENTA_G:10]
[LMAGENTA_B:255]

[YELLOW_R:255]
[YELLOW_G:232]
[YELLOW_B:76]

[WHITE_R:255]
[WHITE_G:250]
[WHITE_B:230]

That's the default graphics that come with the game- what shows up if you turn graphics on in init but don't install any.
You probably just overwrote all of the stuff in your old file huh?

If you get another copy of the raw->graphics folder from the mayday pack and copy that stuff over again it will look like what you are used to.

[Andir]

Aren't Mayday's graphics are still BMP instead of PNG?  It could just be an issue of recoding the tile.  (Open in your favorite editor and save to PNG...)

[Baughn]

No, it still reads BMPs just fine.
PNGs are preferred for the compression support, that's all.

[Bunny]

Firstly, that was one awesome cute little adventure mode spoiler!

Also, issue I have noticed - mouse is no longer viable for mining... game registers when you click to start placing tiles for mining etc, but does not register when you unclick, resulting in streams of random tiles being marked to be mined out when you try to move the mouse.  No other problems on my one juuust yet

[Shoku]

Aren't Mayday's graphics are still BMP instead of PNG?  It could just be an issue of recoding the tile.  (Open in your favorite editor and save to PNG...)

Well, precisely what I expect the problem is is that it overwrote the .txt files that say which graphics to use for what.

[Corona688]

It has to do with the way the tiles are handled. There is color A B C... this is easiest to see with smoothed and then engraved floors (if you have them obscured.) If you've got one of those tilesets where a smoothed floor is basically a + but an engraved floor has extra lines making it into a spiral or laying down a bunch of small squares in the corners. The game makes both of those from the same tile in the font file.

So engravings have a hidden third color, while smoothed floors don't...?

Now, with doors you've surely noticed that sometimes it is a black border with a whatever color door in the middle but other times it is a black door-shape in the middle with a whatever color frame. Again, same tile but the game is looking at the colors in the image file and deciding how to draw them in the game.

But its the same tile...  How does looking at the colors in the image file tell it when to draw which?

Now with engravings transparency is the color that shows up in addition to what there was smoothed (instead of perhaps just inverting it so that your screen became a glob of white, gray, or microcline-blue.)

What is this third color and where does it come from?

or you can make something like a barrel have some 50% transparency that will make it actually, say, act like a shadow instead of just some third color that may or may not be appropriate.

And make your pumps more barrel-like than ever   So it will draw the underlying floor tile, then the barrel on top?  Or the underlying tile color, then the barrel on top?

[Arktanis]

My fort stopped working overnight D:
I'm currently using Ubuntu 9.04 and, before today, DF worked perfectly.
After unpacking the new SDLDF I couldn't get it started again, it only segfaults. Not even reverting to the old version works any more.
I'm truly confused since all the packages required for it to run are there, as they've always been, up to date.

Any clue on what could it be?

[cbpye]

My fort stopped working overnight D:
I'm currently using Ubuntu 9.04 and, before today, DF worked perfectly.
After unpacking the new SDLDF I couldn't get it started again, it only segfaults. Not even reverting to the old version works any more.
I'm truly confused since all the packages required for it to run are there, as they've always been, up to date.

Any clue on what could it be?

Try a "fresh" copy of DF.  I had the same (well, I haven't seen your output, but mine was segfaulting) problem prior to that.  I think it had to do with the way keybindings are handled and copying my old interface.txt.  Once you try that and everything works OK, then bring over your fortresses.

[Richards]

A few problems as some others are having too
-Sometimes gets "stuck" on [d]esignate and no key press will work, but you can still exit and save the game.
-Adventure mode world travel doesn't allow you to visit site unless you rebind the key, (I think I had to do it a few times for it to work).
-build menu text items are garbled

[Baughn]

So engravings have a hidden third color, while smoothed floors don't...?

It depends on the tileset. To be precise, what happens is this:

The window is, obviously, divided into rectangular tiles.

For each tile, DF supplies the render code with a background color, a foreground color, and a texture.

The renderer first draws the background color to the entire tile.

It then draws the texture on top of that, using GL_MODULATE to merge the foreground color and the texture. You can look up the exact math for that on opengl.org, but to put it very vaguely it combines the texture pixel color and the foreground color. The texture color is often grayscale, in which case you more or less get the hue of the foreground color combined with the brightness of the texture color, but it doesn't have to be grayscale.

Lastly, wherever a texture pixel has an alpha value of less than 1, the background color will shine through. In most tilesets the alpha is either 0 or 1, but again, intermediate values are fine. This is just a linear interpolation.

[Veroule]

I have worked through most of the bugs on my list.  There were a few I spotted that weren't reported in the thread here, and those have all been fixed as well.

I will finally be adding the zoom bindings this time, which will break the repository version for those that are compiling it themselves.  It is possible that the addition of few new functions that are needed already breaks the repo.

I will push the fixes up in seperate commits so that some can have the mouse back to working.

[ac31]

so after a bit of configuring i managed to get a save that had recently begun to run slowly to work with d13

about 25 dwarfs, not TOO many pets, caravan currently at depot

i havent really noticed a difference in frame rate, tried upping the priority to realtime, but that about it.

nothing has really changed since 4-5 saves ago but its just running as slow as a wet week.

still, if this ver helps future df releases be a bit more optimised im all for it

[Keizo]

Throwing in my vote along with everyone else having keybinding issues. Keys just seem to stop working pretty quickly in dwarf mode. My guess is the completely revamped interface.txt and interface system has something to do with it...