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

[Savok]

If only so that we don't check df_28_181_40d6_win.zip every hour or so, do you have any idea when d6 will be up?

EDIT: also, convenient link to the file ↑ if you've got this page bookmarked.

[Baughn]

Hm. Toady's schedule is sometimes hard to grasp, but I think he'd normally be asleep at this time of day - or at least not working on 40d6 - so.. tomorrow sometime, I guess. No need to check for the next six hours, at any rate.

[Mel_Vixen]

Well i think hes is doing an real timout for now till the 2nd or 3rd then the normal developmenttime starts again. I mean d5 has nothing really critical right?

[Baughn]

He's already been looking at the latest set of patches from me, so it would make sense to release d6 first and *then* take a break, but you never know.

[Taritus]

Hm. Toady's schedule is sometimes hard to grasp, but I think he'd normally be asleep at this time of day - or at least not working on 40d6 - so.. tomorrow sometime, I guess. No need to check for the next six hours, at any rate.

Toady's GMT-8.  It's 4PM there.  I think he's awake.

[Baughn]

I know for a fact he's not following a.. standard schedule.

[Ubersoldat]

Does anyone else get a problem where the tiles are all... blurry? It's hard to describe. I run DF 800x600 with the grid set to 80:50, blackspace on, and 40d5 just looks funny compared to regular 40d. Does anyone know what I'm talking about, or do I need to post comparison screenshots? (Sorry if this has been solved, I didn't feel like sifting through 31 pages for an error that apparently wasn't important enough for the first post.)

[Baughn]

That happens if your tiles don't fit the grid size/window size combination properly. Turning black space on helps.

[Ubersoldat]

That happens if your tiles don't fit the grid size/window size combination properly. Turning black space on helps.

Which is precisely why I've already turned blackspace on.

[Baughn]

Ah, right. What tiles are you using?

Actually, I think a screenshot would be best.

[bhelyer]

I take it no one else has been experiencing the crashes mid-game that I mentioned before? I can't reproduce them consistently, and they happen fairly rarely.

[Ubersoldat]

Hmm, on closer inspection I must just be really whiny, or it was fixed in the most recent version. It's mostly text that is affected, which is slightly annoying, but I'll get over it. I'll post the comparison shots anyways:

Regular DF Title screen:

Spoiler (click to show/hide)

40d5 Title screen: (text is a tad blurry, not a big problem but hey)

Spoiler (click to show/hide)

Regular DF Game:

Spoiler (click to show/hide)

40d5 DF Game: (almost no change, but I could swear there's something there bugging me)

Spoiler (click to show/hide)

Init options (same for both):

Code: [Select]

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:800]
[WINDOWEDY:600]
[FONT:curses_800x600.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.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:50]
[FULLGRID:80:50]

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

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

[G_FPS_CAP:5000]

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

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]

[Baughn]

I see the problem, but I'm not sure there's anything to be done about it. Apparently your GPU is just a tad (well, more than a tad, really) inexact about texture coordinates; I don't get that behaviour myself, and any reasonable fix would just cause that problem for everyone else.

Oh, but if you've got any "quality<->speed" settings for opengl, or 3d graphics in general, sliding that all the way to quality might yield some benefits.

I'll look around for solutions, anyhow.


EDIT: Solution found.

[Baughn]

I take it no one else has been experiencing the crashes mid-game that I mentioned before? I can't reproduce them consistently, and they happen fairly rarely.

I left it running overnight with a fuzzer handing it random input (not including ESCs); it was still running the day after.

Have you replicated the crash in BC?

[bhelyer]

I take it no one else has been experiencing the crashes mid-game that I mentioned before? I can't reproduce them consistently, and they happen fairly rarely.

I left it running overnight with a fuzzer handing it random input (not including ESCs); it was still running the day after.

Have you replicated the crash in BC?

No. It's strange. I'll do some more testing, but it seems difficult to pin down.