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

[peterix]

Apply magma to thaw the brook from the level below. If you have magma that is.
Make sure you punch fortifications into the map edge so that the magma can reach the space under the brook water source.

edit: /me is being redundant

[xaque]

I've got a crash bug where the game consistently crashes when you look at a dwarf's personality while the screen is maximized (in windowed mode). My resolution is 1680x1050. I haven't really touched the init, so everything is pretty much running at default settings. I can upload my DF folder if you can't reproduce it for some reason.

[Keldor]

As far as profiling, try out Code Analyst.  It's powerful, it works without having to modify your code (just make sure you build in debug mode so it exports symbols), and most importantly, it's free.

[Baughn]

Ah, thanks for the tip. That should do nicely, as soon as I get it working on Arch. ^^;

[virus_found]

Also, yes, that message implies frame-buffer mode isn't working, and it's falling back to standard mode. You might try partial instead, which wouldn't be affected.

That's what I wanted to know I use ATI Radeon x1950 (AGP 4x) with xf86-video-radeonhd 1.2.5 from Arch User Repository.
I've run a test to determine, what messages are in what modes:
I get this message with all but ACCUM_BUFFER modes (w and w/o single buffer):

Code: [Select]

Using OpenGL output path with client-side arrays
Ideal catalog size: 409x390
GPU does not support non-power-of-two textures, using 512x512 catalog.This message is only for ACCUM_BUFFER mode (w and w/o single buffer as well):

Code: [Select]

Using OpenGL output path with client-side arrays
 and accumulation buffer
Ideal catalog size: 409x390
GPU does not support non-power-of-two textures, using 512x512 catalog.And what do those mean? My card supports only accum buffer?
Btw, I switched to it for now, but didn't notice any fps changes.

[Baughn]

It means your card doesn't support frame-buffer, yes. I should probably be clearer on this.

So you know, frame-buffer and accum-buffer are both (more or less) hacks to make partial printing work better. PARTIAL:0 is likely to be faster than either.. if it works, which chances are it doesn't.

frame-buffer falls back to standard mode if the card refuses, though; accum-buffer doesn't, as that's a required feature. Slow one, usually, but required.

 I'll make it frame-buffer print a message to the effect if that happens.

[soupcan]

These are the errors that I receive when I try to run Dwarf Fortress on 64 bit Arch Linux.
Native client, v. d12:

Code: [Select]

Using OpenGL output path with client-side arrays
Ideal catalog size: 277x267
GPU does not support non-power-of-two textures, using 512x512 catalog.
Using OpenGL output path with client-side arrays
Ideal catalog size: 277x267
GPU does not support non-power-of-two textures, using 512x512 catalog.
The program 'dwarfort.exe' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 59 error_code 1 request_code 153 minor_code 179)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'dwarfort.exe' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 60 error_code 1 request_code 153 minor_code 179)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)


This is the error when I attempt to run the same version through Wine:

Code: [Select]

fixme:keyboard:X11DRV_LoadKeyboardLayout L"00000409", 0080: stub!
fixme:keyboard:X11DRV_LoadKeyboardLayout L"00000409", 0001: stub!
err:ole:CoGetClassObject class {bcde0395-e52f-467c-8e3d-c4579291692e} not registered
err:ole:CoGetClassObject class {bcde0395-e52f-467c-8e3d-c4579291692e} not registered
err:ole:create_server class {bcde0395-e52f-467c-8e3d-c4579291692e} not registered
err:ole:CoGetClassObject no class object {bcde0395-e52f-467c-8e3d-c4579291692e} could be created for context 0x7
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x1fc2d0,0x1fc1d0): stub
fixme:wgl:X11DRV_wglChoosePixelFormatARB unused pfAttribFList
Using OpenGL output path with client-side arrays
Ideal catalog size: 248x248
GPU does not support non-power-of-two textures, using 256x256 catalog.
X Error of failed request:  BadRequest (invalid request code or no such operation)
  Major opcode of failed request:  153 (GLX)
  Minor opcode of failed request:  179 ()
  Serial number of failed request:  788
  Current serial number in output stream:  809
wine: Unhandled page fault on read access to 0x00000000 at address 0x7e4f0da8 (thread 0009), starting debugger...
wine: Unhandled page fault on read access to 0x00000028 at address 0x7ebc93b3 (thread 0015), starting debugger...
wine: Unhandled page fault on read access to 0x00000028 at address 0x7ebbd3b3 (thread 0017), starting debugger...

My computer has the Intel GM965/GL960 Integrated Graphics chipset, and the same errors occur with Compositing disabled, and with both the most recent and legacy drivers. I have all of the proper lib32 packages installed.

[Q-Lok]

...Mmmkay, jaybud4 seems to have the right idea on this.  "All keybinding hell," indeed.  I'm on a laptop with no numpad functionality and I am now entirely unsure of how to rebind the SECONDSCROLL commands to -=[].  Any pointers?

If the problems in this version are really as bad as the last several posts are leading me to believe, I think I might just go back to 40d11.  Hmm.

[Rexor]

Apply magma to thaw the brook from the level below. If you have magma that is.
Make sure you punch fortifications into the map edge so that the magma can reach the space under the brook water source.

edit: /me is being redundant

No magma, so I'll try another location. Thanks for the suggestions, guys. Yeah, it's only natural the brook dried out, but I wonder how it got there to begin with. A rapid climate shift freezing a part of the brook would explain the situation.

[Baughn]

These are the errors that I receive when I try to run Dwarf Fortress on 64 bit Arch Linux.
Native client, v. d12:

Code: [Select]

Using OpenGL output path with client-side arrays
Ideal catalog size: 277x267
GPU does not support non-power-of-two textures, using 512x512 catalog.
Using OpenGL output path with client-side arrays
Ideal catalog size: 277x267
GPU does not support non-power-of-two textures, using 512x512 catalog.
The program 'dwarfort.exe' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 59 error_code 1 request_code 153 minor_code 179)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'dwarfort.exe' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 60 error_code 1 request_code 153 minor_code 179)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)


This is the error when I attempt to run the same version through Wine:

Code: [Select]

fixme:keyboard:X11DRV_LoadKeyboardLayout L"00000409", 0080: stub!
fixme:keyboard:X11DRV_LoadKeyboardLayout L"00000409", 0001: stub!
err:ole:CoGetClassObject class {bcde0395-e52f-467c-8e3d-c4579291692e} not registered
err:ole:CoGetClassObject class {bcde0395-e52f-467c-8e3d-c4579291692e} not registered
err:ole:create_server class {bcde0395-e52f-467c-8e3d-c4579291692e} not registered
err:ole:CoGetClassObject no class object {bcde0395-e52f-467c-8e3d-c4579291692e} could be created for context 0x7
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x1fc2d0,0x1fc1d0): stub
fixme:wgl:X11DRV_wglChoosePixelFormatARB unused pfAttribFList
Using OpenGL output path with client-side arrays
Ideal catalog size: 248x248
GPU does not support non-power-of-two textures, using 256x256 catalog.
X Error of failed request:  BadRequest (invalid request code or no such operation)
  Major opcode of failed request:  153 (GLX)
  Minor opcode of failed request:  179 ()
  Serial number of failed request:  788
  Current serial number in output stream:  809
wine: Unhandled page fault on read access to 0x00000000 at address 0x7e4f0da8 (thread 0009), starting debugger...
wine: Unhandled page fault on read access to 0x00000028 at address 0x7ebc93b3 (thread 0015), starting debugger...
wine: Unhandled page fault on read access to 0x00000028 at address 0x7ebbd3b3 (thread 0017), starting debugger...


Those are glMatrixMode calls.

That you're getting this error means two things - first, that DF is using indirect rendering; second, that your driver doesn't support glMatrixMode.. which was part of opengl 1.0. In other words, it doesn't support 3d rendering, period.

Do any other opengl applications work?

Also, paste your glxinfo output, please.

[Starver]

Yeah, it's only natural the brook dried out, but I wonder how it got there to begin with. A rapid climate shift freezing a part of the brook would explain the situation.

Hmmm.  How many smelters/wood furnaces/etc do you need to build to alter the carbon cycle enough (CO₂ or soot covering everything) to create significant climatic change? 

[soupcan]

These are the errors that I receive when I try to run Dwarf Fortress on 64 bit Arch Linux.
Native client, v. d12:

Code: [Select]

Using OpenGL output path with client-side arrays
Ideal catalog size: 277x267
GPU does not support non-power-of-two textures, using 512x512 catalog.
Using OpenGL output path with client-side arrays
Ideal catalog size: 277x267
GPU does not support non-power-of-two textures, using 512x512 catalog.
The program 'dwarfort.exe' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 59 error_code 1 request_code 153 minor_code 179)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'dwarfort.exe' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 60 error_code 1 request_code 153 minor_code 179)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)


This is the error when I attempt to run the same version through Wine:

Code: [Select]

fixme:keyboard:X11DRV_LoadKeyboardLayout L"00000409", 0080: stub!
fixme:keyboard:X11DRV_LoadKeyboardLayout L"00000409", 0001: stub!
err:ole:CoGetClassObject class {bcde0395-e52f-467c-8e3d-c4579291692e} not registered
err:ole:CoGetClassObject class {bcde0395-e52f-467c-8e3d-c4579291692e} not registered
err:ole:create_server class {bcde0395-e52f-467c-8e3d-c4579291692e} not registered
err:ole:CoGetClassObject no class object {bcde0395-e52f-467c-8e3d-c4579291692e} could be created for context 0x7
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x1fc2d0,0x1fc1d0): stub
fixme:wgl:X11DRV_wglChoosePixelFormatARB unused pfAttribFList
Using OpenGL output path with client-side arrays
Ideal catalog size: 248x248
GPU does not support non-power-of-two textures, using 256x256 catalog.
X Error of failed request:  BadRequest (invalid request code or no such operation)
  Major opcode of failed request:  153 (GLX)
  Minor opcode of failed request:  179 ()
  Serial number of failed request:  788
  Current serial number in output stream:  809
wine: Unhandled page fault on read access to 0x00000000 at address 0x7e4f0da8 (thread 0009), starting debugger...
wine: Unhandled page fault on read access to 0x00000028 at address 0x7ebc93b3 (thread 0015), starting debugger...
wine: Unhandled page fault on read access to 0x00000028 at address 0x7ebbd3b3 (thread 0017), starting debugger...


Those are glMatrixMode calls.

That you're getting this error means two things - first, that DF is using indirect rendering; second, that your driver doesn't support glMatrixMode.. which was part of opengl 1.0. In other words, it doesn't support 3d rendering, period.

Do any other opengl applications work?

Also, paste your glxinfo output, please.

I'm currently at work, so I can't run glxinfo till tonight. I'm not sure if I've tried to run any other opengl apps before. I believe that the card should support direct rendering... I wonder if some of my xorg.conf settings are causing trouble. Anyway, I know that DF runs under 64 bit Vista on the same computer.

[Random832]

What direction is the keyboard code going in, generally? I think that in order to keep the kind of configurability it needs to be able to handle non-US keyboards properly, you really need to stick with the existing concept of a VK-based config file on windows, have a separate keysym-based config file for linux, and something different for mac.

[ghostwheel]

I think this is probably already fixed....

I'm trying the OSX version, on 10.5.6. The screen comes up very nice and sharp. Sometimes, after zooming, I can not get back to the original "sharp" state. Even when I zoom all the way in (i.e. the size displayed is already smaller than the window), the font seems to be still scaled. It doesn't seem to happen every time.
I think it happens when I change the window size while zoomed.

[Baughn]

Right. There's a button to reset the zoom; on plain 40d12, I think it's just the middle mouse button.

Um. I suppose this might be a problem for you, but there it is.

In 40d13 it'll be f12, which is.. eh, also not so good on macs. And the middle button switch zooming modes. 

Well, eventually it'll be configurable.