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

[cbpye]

I get this when I try to run the latest release (40d13):

Code: [Select]

bash-3.1$ ./df
./dwarfort.exe: /usr/lib/libpng12.so.0: no version information available (required by ./libs/libSDL_image-1.2.so.0)
Using OpenGL output path with client-side arrays
Ideal catalog size: 353x341
./df: line 5: 21773 Segmentation fault      ./dwarfort.exe $*
It's done this both before and after I've copied the new libgraphics.so file from the HEAD release.

[cbpye]

After replacing my init.txt with the stock init.txt, I got the following:

Code: [Select]

bash-3.1$ ./df
./dwarfort.exe: /usr/lib/libpng12.so.0: no version information available (required by ./libs/libSDL_image-1.2.so.0)
Using OpenGL output path with client-side arrays
Ideal catalog size: 277x267
Using OpenGL output path with client-side arrays (this line repeated about 10 times)
./df: line 5: 21882 Segmentation fault      ./dwarfort.exe $*
UPDATE:
Ignore me.  Ugh.  I keep doing dumb things whenever there's a new release.

[sawtooth]

Regarding the talk about exported map data that was going on before I would appreciate a human readable format over a binary one.  It might cost a bit more in time to dump the data but any tools that can read the data would be more robust when it came down to changes in different versions.

For human readable serialization there's always YAML libraries to do the work for you.  It would be a nice cross platform format as well as it has libraries so the data could be used in many different languages easily, (C, Perl, Ruby, python, etc.)

[Andir]

To me as a co-developer of khazad, it seems rather sub-optimal. Extracting the *whole* map this way (not just a single z-level) takes too long. I brewed some tea after staring at it for a couple of minutes. Khazad does this in seconds through the tiny 4B window of the Linux ptrace function. Also the amount of raw data produced is quite staggering. A well documented binary format would be better IMHO.

That wouldn't really have any advantage over text - either he has to convert into it (slow, just like the text format), or he has to freeze the internal structures (not gonna happen)

The way you do it now is only fast because you have to adapt to any changes he makes to the internal structures.

If he didn't want to go with a raw binary format, he could make a few methods to handle a lot of the functionality without the lag:

getMapData(x, y, z, x1, y1, z1)
getTileInfo(x, y, z)

This way the external app can call for data for specific tiles instead of the whole map or single tiles.  It can be in the same format (JSON?**)  The packet sent back can be dynamic just as the file is now.  You could even include a getCursorLocation() method that returns the active tile location.  It would be more efficient than dumping the entire map every time.  You could default the MapData function to a coordinate to match the current viewport and the TileInfo to the cursor location.

If he wanted to do binary dumps, he could just release the struct formats/changes for it each release and whoever makes the addon could easily integrate them into the addon.

**I said JSON because it's a name/value dataset that's smaller than XML, similar to C structures (in look and use) and there are a few different C++ libraries out there for it.

[alway]

I seem to be gettin a fairly significant FPS improvement on my favorite map. In D11 it got around 20-25 fps, now it appears to be getting 25-30 fps

[Blank]

• build and designation menus are garbled, as others mentioned. It seems to by some justify problem - hotkeys are mixed in with text and it looks ugly. When I double info window size via Tab, it's somehow better, because most letters are right of the text as they used to be, but still not correctly aligned. For me, this is rather show stoper, because I am stilll new to this great game and I don't really know menus by memory. And I use these menus all the time, so I'll proably just use previous version for now.

Ditto, only the Windows version, instead. Hitting Tab repeatedly will sometimes rearrange the text, but it never gets fixed. Totally screwed up. =(

Also, partial printing with a 60 FPS graphical cap... Is this possible? I've tried lots of combinations and either got lightning-fast blinkies in all screens, or only some screens. Should I be trying huge numbers like 20..?

[Shoku]

• build and designation menus are garbled, as others mentioned. It seems to by some justify problem - hotkeys are mixed in with text and it looks ugly. When I double info window size via Tab, it's somehow better, because most letters are right of the text as they used to be, but still not correctly aligned. For me, this is rather show stoper, because I am stilll new to this great game and I don't really know menus by memory. And I use these menus all the time, so I'll proably just use previous version for now.

Ditto, only the Windows version, instead. Hitting Tab repeatedly will sometimes rearrange the text, but it never gets fixed. Totally screwed up. =(

Also, partial printing with a 60 FPS graphical cap... Is this possible? I've tried lots of combinations and either got lightning-fast blinkies in all screens, or only some screens. Should I be trying huge numbers like 20..?

For me the text is mostly ok when the menu is tabbed to double width- it's that the keys are not lining up properly. They're nearly on the left edge in single width and in double width that's still far enough over to overlap much of the text.
With workshops they are so far over that in single width I only see a few of the brackets.

[Shoku]

What do translucent tilesets in a one-tile-per-square system actually do?  Or is that supposed to mean graphic sets?

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.

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.

So transparency allows some more control over this.
Now with engravings transparency 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.) 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.

Though it will also draw colors besides A B C, such as red or green. It hasn't been so much a limitation of how it does things so much as a way to make automatic color from grayscale. For this reason you can see a lot of tilesets with levers that have some color to tell their states apart, yet the handle is still cinnibar-red or granite-gray.

[Sevrun]

I haven't disabled the FPS cap, but I never seemed to get above about 60 before testing this.  Haven't tested it extensively as of yet, but the initial results are very promising on my rig running at 1440x900  Normal 6x6 grid (which usually drug me down a bit)  Clips right along around the cap 95-100 FPS

only complaint is REALLY minor, namely that tweak doesn't work for it

Yeah, I'm a lazy bugger.  Awesome work, and I don't say that often

[aklyatne]

I know it's been reported already, but...
Can't get out of map travel in adventure mode.  Which is a pain, because I have to wander around in a forest to get out of travel.  And then I get eaten by jaguar|bear|wolves|etc.

Is it just a key binding problem where shift+period doesn't work?

[da dwarf lord]

I don't know if some one has already reported this but the mouse designation selection option has stuffed up on mine and now if i have the designation screen open and move the mouse over the window even without clicking it designates random squares for mining

[virus_found]

It designates those squares, which you point with a mouse. Though, it should only trigger with a click, not with a mere mouse movement.

[Veroule]

I know it's been reported already, but...
Can't get out of map travel in adventure mode.  Which is a pain, because I have to wander around in a forest to get out of travel.  And then I get eaten by jaguar|bear|wolves|etc.

Is it just a key binding problem where shift+period doesn't work?

Yes.  Set another key for the Travel End binding.  I used 'q' and it worked just fine.

I don't know if some one has already reported this but the mouse designation selection option has stuffed up on mine and now if i have the designation screen open and move the mouse over the window even without clicking it designates random squares for mining

Added to my bug list.

[Mel_Vixen]

Could you set a "Keybind-file" where everything works into the wiki or the OP? I am sure that would help the people here who have problems with the bindings.

[strich]

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]