Print

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

[Drengor]

  I've been having an issue with 43.03 and 42.06 twbt mode as distributed with Peridexis's starter pack.  If a window size is specified in the init, the graphics will fail after 30-50 seconds or so.  It switches into twbt mode fine, it's a delayed problem. 

  When the graphics fail, it's basically just background colors.  A screenshot is at http://imgur.com/a/Oe3sy .

  Fortunately, resizing the window fixes it, turning it from a breaking bug into a nuisance.  A screenshot after resizing is at http://imgur.com/a/fVNVe .

  I can supply additional information as needed... Here is the basics...

  Windows 7 SP1 x64
  16G
  SAPPHIRE Radeon R9 270X (2G)
  Radeon Software Version 16.7.3


Here's the graphics portion of the init...

Spoiler (click to show/hide)

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:100]
[WINDOWEDY:60]
[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_640x300.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 May 2016, the Dwarf Fortress Wiki has custom tilesets available at http://dwarffortresswiki.org/index.php/Tileset_repository and creature graphics at http://dwarffortresswiki.org/index.php/Graphics_set_repository.

[GRAPHICS:YES]
[GRAPHICS_WINDOWEDX:100]
[GRAPHICS_WINDOWEDY:60]
[GRAPHICS_FONT:Phoebus_16x16.png]
[GRAPHICS_FULLSCREENX:0]
[GRAPHICS_FULLSCREENY:0]
[GRAPHICS_FULLFONT:Phoebus_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.

On a multi-core machine none of this is very likely to matter; stick to 2D.

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:TWBT]
   Mode examples:
    PRINT_MODE:2D
    PRINT_MODE:TEXT
    PRINT_MODE:FRAME_BUFFER
    PRINT_MODE:PARTIAL:0
[SINGLE_BUFFER:NO]

Switches truetype on whenever the vertical tile size is this many pixels or larger.  You may also use YES/NO to force it on/off.  Turning it off may provide a minor speed boost (using font small enough that it doesn't activate won't).

[TRUETYPE: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:100]

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

[G_FPS_CAP:25]

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

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]

 

[jecowa]

That's interesting. What's your screen resolution?

[Drengor]

1920x1080

[jecowa]

I was thinking your screen might be too short for those settings, but 1600x960 should fit very easily in 1920x1080, even when accounting for ~64 vertical pixels taking by the Windows dock and the border of the Dwarf Fortress window. I guess I should have seen from the first screen shot that that wasn't the problem.

[mifki]

1920x1080

Last time I played on TV in this resolution, it was fine, I'll test it again.

[Russell.s]

I really love TWBT but don't like having to wait for dfhack to update in order to use it. I don't use any of the other dfhack features. Is it possible to run TWBT without dfhack? Or run it in some way so that I don't need to wait for dfhack to update to the latest version?

Thanks very much for your help .

[Rose]

I really love TWBT but don't like having to wait for dfhack to update in order to use it. I don't use any of the other dfhack features. Is it possible to run TWBT without dfhack? Or run it in some way so that I don't need to wait for dfhack to update to the latest version?

Thanks very much for your help .

No.

[lethosor]

Although you could technically build DFHack and TwbT from source, if DFHack is too buggy to release, it's likely that TwbT will be unstable too.

[Russell.s]

No.

Although you could technically build DFHack and TwbT from source, if DFHack is too buggy to release, it's likely that TwbT will be unstable too.

Okay, thanks you two. I'll just have to wait patiently for DFhack to reach the latest version before striking the earth!

[milo christiansen]

Is there any way to fix DFHack menus/sidebars/dialogs showing the map display area as black when they are open?

[lethosor]

Is there any way to fix DFHack menus/sidebars/dialogs showing the map display area as black when they are open?

Besides disabling TwbT, not yet. I'm working on a way to let TwbT avoid breaking those, but it's not done yet. I might be able to get to it today or tomorrow, though.

[figment]

I've gotten TWBT at least partially working with 0.43.05 and my current build on Win32 so I thought I'd share the key information to possibly save someone else time.  I added a dummy parameter for edx value on fastcall.  Haven't really tested the p_render_lower_levels patch yet but the rest of the code loads now without crashing so thats something.

Convert_magenta may be back but seems unused and possibly not a bool but int with value of 3 but since apparently unused it doesn't matter.

Spoiler (click to show/hide)

Changed LOAD_MULTI_PDIM to the following.

Code: [Select]

typedef int (__fastcall *LOAD_MULTI_PDIM)(df::enabler::T_textures *pEcx, void* pEdx, const string &filename, long *tex_pos, long dimx, long dimy, bool convert_magenta, long *disp_x, long *disp_y);
#define load_tileset(filename,tex_pos,dimx,dimy,disp_x,disp_y) _load_multi_pdim(&enabler->textures, nullptr, filename, tex_pos, dimx, dimy, true, disp_x, disp_y)

#elif defined(DF_04305)

    #if defined(WIN32) && defined(DFHACK64)

        #define A_LOAD_MULTI_PDIM 0xA36AD0
        #define A_RENDER_MAP      0x8170B0
        #define A_RENDER_UPDOWN   0x593F30

        static patchdef p_display = { 0x35C4CB, 5 };

        static patchdef p_dwarfmode_render = { 0x31266A, 5 };

        static patchdef p_advmode_render[] = {
{ 0x265A6B, 5+5 },{ 0x265ABC, 5+5 },{ 0x265B06, 5+5 },{ 0x265FF4, 5+5 }
        };
        static patchdef p_render_lower_levels = {
            0xB7F500, 15, true, { 0x36,0x8b,0x84,0x24,0x0C,0x00,0x00,0x00, 0x3e,0xc6,0x00,0x00, 0xC2,0x1C,0x00 }
        };

    #elif defined(WIN32) && !defined(DFHACK64)

        #define A_LOAD_MULTI_PDIM 0x00C9F050
        #define A_RENDER_MAP      0x00AD1E90
        #define A_RENDER_UPDOWN   0x008C02C0

        static patchdef p_display = { 0x006DDAF1, 5 };

        static patchdef p_dwarfmode_render = { 0x006A1776, 7 };

        static patchdef p_advmode_render[] = {
            { 0x0060C4ED, 2+5+5 }, { 0x0060C53A, 2+5+5 }, { 0x0060C583, 2+5+5 }, { 0x0060CA06, 2+5+5 }
        };

        static patchdef p_render_lower_levels = {
            0x00DAD330, 15, true, { 0x36,0x8b,0x84,0x24,0x0C,0x00,0x00,0x00, 0x3e,0xc6,0x00,0x00, 0xC2,0x1C,0x00 }
        };

    #endif
#else


Win64 requires the the following vtable patch as well.

Code: [Select]

library/VTableInterpose.cpp | 18 +++++++++++++++---
 1 file changed, 15 insertions(+), 3 deletions(-)

diff --git a/library/VTableInterpose.cpp b/library/VTableInterpose.cpp
index c547800..f63d1a4 100644
--- a/library/VTableInterpose.cpp
+++ b/library/VTableInterpose.cpp
@@ -143,9 +143,21 @@ int DFHack::vmethod_pointer_to_idx_(void *pptr)
         return ((int8_t)pval[1])/sizeof(void*);
     case 0xA0FF018BU: // mov eax, [ecx]; jmp [eax+0x????????]
         return ((int32_t)pval[1])/sizeof(void*);
-    default:
-        return -1;
-    }
+#if _M_X64
+ case 0xff018b48U:
+ switch (((int8_t *)pval)[4])
+ {
+ case 0x20:  // mov rax, qword ptr[rcx]; jmp qword ptr[rax]
+ return 0;
+ case 0x60:  // mov rax, qword ptr[rcx]; jmp qword ptr[rax+0x??]
+ return (((int8_t *)pval)[5]) / sizeof(void*);
+ case 0xA0:  // mov rax, qword ptr[rcx]; jmp qword ptr[rax+0x????????]
+ return *(int32_t*)((int8_t *)pval+5) / sizeof(void*);
+ }
+ break;
+#endif
+ }
+ return -1;
 }
 
 void* DFHack::method_pointer_to_addr_(void *pptr)


[Meph]

A question/request: Would it be possible to split TWBT multilevel and TWBT overrides into two plugins?

[Dirst]

A question/request: Would it be possible to split TWBT multilevel and TWBT overrides into two plugins?

Both plugins would need to hook into the same rendering steps.  I think that setting multilevel 0 effectively turns off that portion of the code.  One could also disable overrides by not having an overrides file, though I don't know if that "disables" the feature in the sense of avoiding crashes associated with the override engine.

[Meph]

Yeah, I was thinking of enabling multilevel, but disabling the override tiles.

I was looking at installing more tilesets for MasterworkDF and I'm trying to come up with a good way to swap tilesets using TWBT, but the override tiles make it difficult... I have some unique ones per tileset, some that are always on, and other that should probably be disabled if you play with ASCII or an ASCII-like tileset.

I was really hoping to get GemSet to work, but its rather difficult. Tilesets, overrides, TWBT font tileset, creature sprites, different size (32x)... but that is another topic.