Print

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

Faster, no (unknown) problems

Faster, problematic

Same speed, no (unknown) problems

Same speed, problematic

Slower, no other (unknown) problems

Slower, problematic

Doesn't work at all

[Andir]

Not really a bug, per-say, but at the default windowed resolution with fps display on, the fps screen covers everything in the world name except for "the".
~die images die~

Also, this problem on the "z" screen for the date. WHAT DAY IS IT?

A nice workaround would be to put it on the bottom...

Putting it on the bottom then covers the messages :p  I know... I know... nothing important shows up there, and if it does you can hit A to see the previous messages.  Personally, I'd love to see a marquee message notification on the bottom with the FPS off to the side where the marquee space increased with window size.

[nitnatsnoc]

In side by side tests of world gen, 40d19 beat 40d everytime.

This was on a Phenom II X4 945 (3.0ghz), 4gb RAM, GeForce GTX 260, Windows 7 64bit.

All modes were playable, with the exception of Shader (with and without ARB_SYNC). I couldn't see any error details, but if I've missed them, let me know and I'll post them.

[dorf]

Someone did, I'm fairly sure, which is why you keep getting people who are using it.

I am, howe'er, unable to find it presently.

Found it!
http://dffd.wimbli.com/file.php?id=920

[dorf]

- loaded reinhammers save (same results as in d17 and d18):
40d: 11 FPS; [PARTIAL_PRINT:YES:0]
40d19: 7(7)/7 FPS, works fine; [PRINT_MODE:PARTIAL:0]
[...]

At this point I'm goin to chalk that up to optimization differences in DF itself. It pretty much can't be due to the graphics code, not with all the modes giving the same FPS.

I've freshly embarked on a 6x6 map with a river, little wildlife and idling dwarves.

I've tested it in 40d and 4019_2 with similar inits and 40d was almost twice as fast as 40d19_2 (using partial print).
40d: 300> FPS
40d19_2: ~175 FPS

Is it possible to add Toady's old graphics code? It seems, his way of doing things is faster for older cards.

[Banana]

i would love to know how to change the interface file so i can actually play this on my laptop(since my computer is a laptop)

[quinnr]

i would love to know how to change the interface file so i can actually play this on my laptop(since my computer is a laptop)

Why can't you?

[Rafal99]

Not really a bug, per-say, but at the default windowed resolution with fps display on, the fps screen covers everything in the world name except for "the".
~die images die~

Also, this problem on the "z" screen for the date. WHAT DAY IS IT?
A nice workaround would be to put it on the bottom...

Yeah I noticed that too. It covers both the day and the month of the date in the (z) screen. And I use it quite a lot, to see how much time left to arriving/leaving of the caravans for example.

[Malicus]

I zoom around when I need to see the date, but that might not work for everyone.

[Banana]

nevermind i got it to work

[quinnr]

How?

[Leotto]

If he told you, he would have to kill you.

[Baughn]

So let's see..

- I've already altered -head so both ^? and C-h are treated as backspace. Since there is no line editing possible, that should be a sufficient solution.
- (In d19_2_win) I fixed the ATI shader compilation, but not the shaders themselves, since I don't have any modern ATI hardware to test on. It should be possible for someone who does to finish the job, now.
- Did d19_2 solve any problems for anyone? It stopped it crashing on /my/ windows installation, at least..
- The game is indeed supposed to be linking to ncursesw, not ncurses. Actually, according to ldd it /is/. Can you provide the full ldd dwarfort.exe output?
- My current plan for the FPS counter is to search for unused space and move it around accordingly. Grumblerumble.

EDIT: Oh, I see what's going on. I must have forgotten to mention ncursesw properly to toady.. grab d19-head, and it should work.

[Baughn]

I've recompiled d19-head with Clang, which seems to give a noticable (well, to counters) speed boost. Using that on DF itself should give a rather larger one.

Unfortunately, there's a minor chance of issues, so d19-head users beware. 

[Toksyuryel]

First off, me love you long time for creating the TEXT output option

On to business: I am getting the following error when I attempt to run in TEXT mode:

Code: [Select]

terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
./df: line 6: 22786 Aborted                 ./dwarfort.exe $*This error also results in the terminal going wonky, requiring me to close it and open a new one (had to use redirection to save this error message- saving standard input is a lost cause because it wipes itself out when the error occurs and seems to insert the same wonkyness into the log file itself, rendering the terminal wonky after cating it).

[darius]

Wee shader works on ATI, changes:

Code: [Select]

//in vec4 gl_Vertex;
//in int gl_VertexID;
in shader.vs and

Code: [Select]

//out vec4 gl_FragColor;
in shader.fs
Also no flickering (even using graphics). Although bold is somewhat broken: in main menu it works, but not in game. When using graphics somehow it does not detect grayscale and shows all dwarfs as gray. FPS:~230

Looks like i fixed bold problem:

Spoiler (click to show/hide)

Code: [Select]

#version 140 // -*- mode: C -*-
// Defines emitted by gridrectst::init_gl at load:
// dimx, dimy:      Grid size of the screen array
// dispx, dispy:    Grid-cell (font) size
// vec4 colors[16]: Color palette; first non-bold, then bold
#ifdef GRAPHICS
// offset_texpos, offset_addcolor, offset_grayscale, offset_cf, offset_cbr:
//   offsets of the corresponding graphicst arrays in data
#endif

uniform isamplerBuffer data;
uniform samplerBuffer coords;
uniform isamplerBuffer fontmap;

uniform uint frame; // Counts up from 0

//in vec4 gl_Vertex;
//in int gl_VertexID;

flat out vec4 frontColor;
flat out vec4 backColor;
smooth out vec2 texCoords;

void main() {
  int tile = gl_VertexID / 6;
  int offset_tile = tile * 4;

  int ch   = texelFetch(data, offset_tile).a;
  int fg   = texelFetch(data, offset_tile+1).a;
  int bg   = texelFetch(data, offset_tile+2).a;
  int bold = texelFetch(data, offset_tile+3).a;

#ifdef GRAPHICS
  uint texpos = texelFetch(data, offset_texpos + offset_tile).a;
  texpos += texelFetch(data, offset_texpos + offset_tile + 1).a * 256u;
  texpos += texelFetch(data, offset_texpos + offset_tile + 2).a * 65536u;
  texpos += texelFetch(data, offset_texpos + offset_tile + 3).a * 16777216u;
  uint addcolor = texelFetch(data, offset_addcolor + offset_tile).a;
  uint grayscale = texelFetch(data, offset_grayscale + offset_tile).a;
  uint cf = texelFetch(data, offset_cf + offset_tile).a;
  uint cbr = texelFetch(data, offset_cbr + offset_tile).a;


  vec4 tex_square;
  if (texpos != 0u && ch != 0) {
    tex_square = texelFetch(coords, int(texpos));
    if (grayscale != 0u) {
      frontColor = colors[int(cf + cbr * 8u)];
    } else if (addcolor != 0u) {
      frontColor = colors[fg + bold * 8];
    } else {
      frontColor = vec4(1);
    }
  } else {
    tex_square = texelFetch(coords, texelFetch(fontmap, ch).a);
    frontColor  = colors[fg + bold * 8];
  }
#else
  vec4 tex_square = texelFetch(coords, texelFetch(fontmap, ch).a);
  frontColor  = colors[fg + bold * 8];
#endif

  vec2 coords[6] = vec2[](tex_square.sq, tex_square.tq, tex_square.tp,
                          tex_square.sq, tex_square.tp, tex_square.sp);
  texCoords = coords[gl_VertexID % 6];
 
  gl_Position = gl_Vertex;
  backColor   = colors[bg];
}


edit3:
Movies look strange (something to do with bold)