Okay, made some serious testing with the speed. Here is the settings I use:
WARNING: Do NOT copy over the init.txt from an earlier version of DF.
Always read the file carefully, including the comments.
In general, you can copy savegames and tilesets from older DF
versions, but you should not copy anything else. You should not, under any
circumstances, unpack a new DF on top of an older one.
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 the 800x600 font might make you happier.
If set below 256x256 it specifies the grid size instead, with a minimum of 80x25.
[WINDOWEDX:80]
[WINDOWEDY:25]
[FONT:curses_640x300.png]
You may disable window resizing if you wish.
[RESIZABLE:YES]
Full screen info. The 0s below mean that the game will choose a resolution for you, but you can set it yourself as well.
[FULLSCREENX:0]
[FULLSCREENY:0]
[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]
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:0]
[GRAPHICS_WINDOWEDY:0]
[GRAPHICS_FONT:curses_square_16x16.png]
[GRAPHICS_FULLSCREENX:0]
[GRAPHICS_FULLSCREENY:0]
[GRAPHICS_FULLFONT:curses_square_16x16.png]
[GRAPHICS_BLACK_SPACE:YES]
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 2D, 2DSW, 2DASYNC, 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.
By and large, 2D should be the most reliable, while STANDARD has a good combination of speed and reliability. However, all 2D modes are normally far slower than even STANDARD, which may be the slowest OpenGL mode.
2DASYNC may be slightly more responsive than 2D on a multi-core machine, but this has recently become doubtful due to improvements to the other modes.
Linux/OS X users may also use PRINT_MODE:TEXT for primitive ncurses output.
[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.
You may set FPS_CAP to 0 to make it uncapped.
[FPS_CAP:2000]
Use this to set the maximum graphical frame refresh rate during play.
[G_FPS_CAP:20]
On cards that support the OpenGL ARB_sync extension, turning this on can improve framerates in GPU overload conditions. It defaults to NO, as many cards that claim to support this will crash if asked to do so.
[ARB_SYNC:NO]
This sets the applications vertical synchronization behavior. Changing this to YES can impact your FPS if your G_FPS is high. ARB_SYNC is a better option, if your system supports it.
[VSYNC:NO]
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:HIGH]
Use this to set how fast the game zooms. The default corresponds to
increasing grid size by 10 units each time you zoom.
[ZOOM_SPEED:10]
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]
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:250]
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]
Change this to NO if you want to leave save uncompressed (you might want to do this if you are experience save corruption).
[COMPRESSED_SAVES:YES]
The settings are more or less the same I used with .03, though raise the FPS_GAP to 2000 from 1500.
Title screen:
In .03, the maximum was somewhere 1000-1200 FPS, so never reached the gap. In .04, I reached the 2000 FPS, which is the maximum with my settings
World generation with parameters -screen:
In .03 it was around 1000 FPS. In .04, It started in 1500, stayed there for a bit, then raised to 2000.
The world generation:
.03: Starts out with 100 FPS, usually drops down to 10 FPS pretty soon. Most of the times even as low as 1 FPS if I'm genning world with more history than 300 years.
.04: While creating the actual world, the FPS hanged around 200 FPS. When history creation begun, the FPS dropped to 9 FPS for brief moment, then went back to 15 FPS. After that, it dropped about 1 FPS per 100 years, ending around 9 FPS with history of over 1000 years.
Offloading units:
.03: The numbers were stranges, jumping even up to 20k.
.04: Slow, went down to 300 FPS and still dropping.
Embark location selection -screen:
.03: Around 400 FPS, dropping down to 100 when moving cursor.
.04: 2000 FPS all the time
The game:
.03: While paused, the normal is somewhere around 500-800 FPS, depending on the location of embark (3*3 with brook). While running, the FPS may get to even 250 FPS, but that's rare, usually it stays somewhere around 100-120 FPS, dropping down to 70 FPS after some time. So far it has been pretty stable 70, only occasion peeks in lag, usually caused by something like generating invasion or such.
.04: Paused stays in 2000 FPS. Unpaused, fresh game runs in mighty 550 FPS with one woodcutter cutting trees and one miner mining couple of 3 tiles wide passage.
So, to summarize the results, which does not take in account the possible affects of graphics, generally the game is running much faster than .03. I will return to this when I have fort with bit of age behind, so I can tell how the FPS changes during the time.
Author
Topic: The DF 0.31.04 Work-In-Progress Thread (Read 220725 times)