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

[Karlito]

40d12 isn't displaying a save-file select screen for me.  Its just going straight to loading the first file in the directory.

[jamoecw]

the game runs pretty good, the middle menu needs some work (as some things are cut off, such as 'help' just has 'he'), the game help that talks about which keys do what sometimes says broken in red (not that big of a deal really, it says what is what in the middle menu), zoom shrinks everything (kind of expected actually considering it is an ascii game, and the zoom is sort of 3rd party), every second or two the game thinks, which causes a very slight hiccup in speed, if one is rapidly jumping through z layers then this turns into a complete stop for about half a second to a second (40d11 didn't have this but wasn't as fast either, and 40d got got slower than this, though consistently as in per tick).

i have weather turned off in the init.txt, underground features turned to always, and i had forgotten to set it to show fluid amounts (which i did while typing this).  i use windows xp pro, athlon xp 1800 (1.54gh), 150 Gb ram, DF is on a second HD which uses ntfswith 18.9Gb free, while my main uses fat32 with 1.38Gb free.  you probably don't need to know the HD stuff, but some games do weird stuff with virtual memory.

[Baughn]

40d12 isn't displaying a save-file select screen for me.  Its just going straight to loading the first file in the directory.

That's bizarre, and also doesn't happen to me.

Does this still happen if you use a clean install?

[Slinkyfest]

Just tried to play once more, getting the below error message. Im actually having issues running a number games, they all start up and then crash as they begin to initialize. At least DF gives me an error code.

Error Given

Spoiler (click to show/hide)

AppName: dwarf fortress.exe   
AppVer: 0.0.0.0   
ModName: atioglxx.dll
ModVer: 6.14.10.8543   
Offset: 0051a66e

Comp Stats

Spoiler (click to show/hide)

Windows XP Home Edition SP2
AMD Athlon~1.1GHz
512MB RAM
Card name: ATI Radeon 9550 / X1050 Series

The resolution is 1360x768 and I have been having this problem since day one of running this computer.

[Siquo]

No crash, but also no screen. It starts, and in "processes" I see it running, but there's no window, and alt-tabbing also shows no application...

Running on Win XP Pro SP3, clean install of 40d12

[Baughn]

To the last two: Try it on Linux.

Go on, download Wubi and try it. There's a good chance that would make it work, but if it doesn't, at least I can get some more useful debugging information.

And unfortunately, the radeon 9550 is too old. ATI is well known for dropping support for older cards within two or three years; the 9550 is seven. That's just one reason I'm sticking to nVidia...

(But Linux has an open-source radeon driver that often works when ATI's doesn't)

[Da King]

Runs well for me, being able to see this much of the map in fullscreen is awesome. About 400 FPS in windowed, 300 FPS in fullscreen.

[Slinkyfest]

To the last two: Try it on Linux.

Go on, download Wubi and try it. There's a good chance that would make it work, but if it doesn't, at least I can get some more useful debugging information.

And unfortunately, the radeon 9550 is too old. ATI is well known for dropping support for older cards within two or three years; the 9550 is seven. That's just one reason I'm sticking to nVidia...

(But Linux has an open-source radeon driver that often works when ATI's doesn't)

But it would work on my previous computer that lacked a graphics card... Any way I can install linux without wiping my harddrive?

[Baughn]

Yes. Use Wubi.

DF 40d was compatible with the windows software-renderer, indeed. The next version won't be, so.. sorry about that, but pretty much any card on the market today would be fifty times faster than the one you've got, even the el-cheapo $30 ones.

[0x517A5D]

The resizing code works for me.  I immediately noted that the 80x25 startup screen start out centered, but jumps to the top left of the window as soon as the window is resized or even moved.  Resize during a game works.

Zoom out works but i don't really like it.  Zoom in doesn't expand past the actual size of the font but it does resize the area of the window that is used.  The "step" of the zoom feels far too small, like 1% or so.  I would like 25% or 50%.

This is with a Radeon 4870 and the February 2009 drivers.

With the new resizing code comes a housekeeping task:

• Rename curses_640x300.png to curses_8x12.png or similar
• Rename curses_800x600.png to curses_10x12.png or similar
• Create a pixel-doubled version of each, giving them appropriate names.

And an aside: I very much want to be able to start the game with the window position and size the same as when I last quit.

My preferred window position actually starts off the screen, with the top left at X=-3,Y=-12.  Combining this with a WINDOWEDX/Y of 1680/1008 lets me maximize the client area's space while still allowing my taskbar to be visible.

In 40d9 I do this with a combination of the stated WINDOWEDX/Y settings and a custom startup command that positions the window.

It would be preferable for DF to remember its previous window position.  If that's not practical, I would at least want to continue to be able to set window size in the init.txt file.


Edit: In fullscreen, my flashing bottom line bug is once again occurring.  Setting FULLGRID vertical size to overwrite the flashing bottom line is not acceptable to me because of very ugly font resizing.

[Baughn]

All your complaints have already been addressed for the next version, except saving the window size/position for next time. That would be nice, though..


Oh well. I'm hereby announcing that I'm going on vacation tomorrow; I'll be back in 14 days or so. If anyone wishes to ask something, this'd b the time.

[Slinkyfest]

Yes. Use Wubi.

DF 40d was compatible with the windows software-renderer, indeed. The next version won't be, so.. sorry about that, but pretty much any card on the market today would be fifty times faster than the one you've got, even the el-cheapo $30 ones.

Eh, downloading wubi now... Fingers crossed I want me some kitten porridge tonight! Oh, and thanks for the recommendation Baughn, I hope it works.

[Rivaryn]

Sorry for the long delay...

Here is the original init.txt for the 40d5 one:

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

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:1600]
[WINDOWEDY:1140]
[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: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 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.png]
[GRAPHICS_FULLSCREENX:1280]
[GRAPHICS_FULLSCREENY:800]
[GRAPHICS_FULLFONT:curses_square_16x16.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:200:95]
[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: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:500]

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

[G_FPS_CAP:50]

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

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]

And here is the unified diff of the 40d12 I tried using compared to it:

Spoiler (click to show/hide)

--- init.txt.old   2009-01-01 12:46:57.000000000 -0500
+++ init.txt.new   2009-06-21 14:00:11.000000000 -0400
@@ -26,6 +26,7 @@
[FULLSCREENY:600]
 [FULLFONT:curses_800x600.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]
@@ -46,9 +47,10 @@
 [GRID:200:95]
 [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.
+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.
 
-[PARTIAL_PRINT:NO:2]
+[PRINT_MODE:STANDARD]
+[SINGLE_BUFFER:NO]
 
 Change this to YES to keep the DF window on top of your other windows.
 
@@ -70,6 +72,7 @@
 
 [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:NEAREST]
@@ -191,10 +194,18 @@
 
 [SHOW_ALL_HISTORY_IN_DWARF_MODE:NO]
 
-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.
+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]

(I figured a diff would be better than simply reposting the new one, since it would be a lot easier to see what I changed).  I copied them to my linux system and diffed them there, but I run DF on windows XP SP3

Hope that helps...

[Veroule]

Still, the keyboard input isn't working exactly like 40d9. I am using an alternate layout called Colemak, on a qwerty keyboard.

Now the game seems to take most of the input correctly, except some, where it reads me as pressing the qwerty equivalent. An example is at the embark screen, the physical N on my computer should be 'K'. But when I press the N key (expecting the embark square to move down), the game wants me to make a note. The interesting thing is the physical 'J' key, which should be N, reads as N, and also prompts me to make a note. There are other examples of this in the other menus as well.

Thank you for the detailed report.  I thought I was being a little too agressive by checking both scan codes and converted unicode values.  It is very easy to have it not look at the scan code when the unicode value is available, and that will fix the problem you are seeing.

[Narmio]

I think I asked this a few pages ago, but it went unanswered.  Sorry for the repost:

How does one use this macro designation feature I hear being discussed?  I can't find it, nor any documentation related to it.  Am I blind, or is it a very stealthy feature?