Bay 12 Games Forum

Please login or register.

Login with username, password and session length
Advanced search  

Poll

After experimenting with the options, how is 40d13? Problems only count if the defaults don't work.

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


Pages: [1] 2 3 ... 147

Author Topic: FotF: Help test the output code for the next version of DF (40d13)  (Read 360007 times)

Baughn

  • Noble Phantasm
  • The Haruhiist
  • Hiss
    • View Profile

As you may be aware, Dwarf Fortress' approach to OpenGL leaves something to be desired. To the point of my writing terrible hacks like DF Accelerator, even..

At any rate, Toady has decided to do something about that, and did it by releasing the relevant source code in the form of Battle Champs for others to fix.

This has been done: The code has been converted to use SDL by Bernard Helyer, and the OpenGL code has been rewritten by yours truly. It is almost complete. However, for Toady to accept the code into the next version of DF, your assistance is required: It must be tested. For this, you are required.

Download links
Windows: http://www.bay12games.com/dwarves/df_28_181_40d13_win.zip
Linux: http://www.bay12games.com/dwarves/df_28_181_40d13_linux.tar.bz2
OS X: http://www.bay12games.com/dwarves/df_28_181_40d13_osx.tar.bz2
For linux users, the following link contains a tarball with the newest fixes, which will be officially released in 40d14. It must be unpacked on top of the 40d13 tarball.
Linux 40d13 HEAD: http://brage.info/~svein/df-40d13-head.tar.bz2

For users on Linux and OS X, run the df script, don't run the dwarfort.exe executable directly.

New features in 40d13 (vs. 40d)
- Translucent tilesets are supported, using PNG.
- The DF window can be resized on the fly.
- The DF window can be zoomed on the fly using the mouse wheel. There are two modes, it defaults to mode 1. Pressing mouse wheel switches modes. Pressing F12 resets mode 1, not 2. In mode 1, the zoom from mode 2 is not visible. (And yes, you can use both at once)
- The keyboard input system has been totally rewritten:
* You can bind multiple keys to one command
* You can create keyboard macros
* Input bindings are divided into sections
- Lots of bugfixes and performance improvements.
Upcoming features in 40d14 or 40d13 HEAD
Grid size autogenerated
Fullscreen resolution autogenerated

Please download it, run it, and test with all the different tilesets and grid sizes your hearts desire. Graphics sets, too.

Bug-tracker
There should be a list of known bugs at http://github.com/Baughn/Dwarf-Fortress--libgraphics-/issues. Feel free to add yours there when you report it.
- Tiles may show black borders when zooming. Fixed, d14/d13-head
- The mouse buttons get stuck when designating. Fixed, d14/d13-head
- Various keyboard issues. Fixed, d14/d13-head

Tips and tricks
- Make sure you test all the combinations for buffers/partial printing that Toady suggests in init.txt.
- Make sure to try the debug version (not up yet) before posting about problems, if you run linux. If you don't run linux, try running linux.

Source code
For the perennially curious, or programmers, the source code (that is still under active development) can be found at git://github.com/Baughn/Dwarf-Fortress--libgraphics-.git. It uses the git version-control system, and can also be seen in a browser at http://github.com/Baughn/Dwarf-Fortress--libgraphics-/tree/master.

Compiling this code gives a functional DF, but it can only be compiled on Linux.
« Last Edit: July 24, 2009, 06:10:44 pm by Baughn »
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

Duke 2.0

  • Bay Watcher
  • [CONQUISTADOR:BIRD]
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #1 on: December 20, 2008, 01:50:45 pm »

 So what does this provide that the normal DF does not? Just a speed up?

 Link to relevant page?

 Despite these questions, I have a creeping sense of awesomeness in the back of my mind. Like something grand will happen to DF soon. Like 500 dwarf fortresses and 12x12 areas. I know nothing drastic like that will happen...

 Will it?

 Edit:

 ...

...

 Wha... You...

 Alright, time to take off the 100 fps cap...

 Edit 2:

 Alright, it is now hovering around 110 FPS with ALL of the speed-lowering things on. With the highest grid size for a 9x9 tileset on a 1024 X 768 monitor.

 I... I may be a man, but I wish to have your babies. That is how staggeringly awesome this is.
« Last Edit: December 20, 2008, 02:01:23 pm by Duke 2.0 »
Logged
Buck up friendo, we're all on the level here.
I would bet money Andrew has edited things retroactively, except I can't prove anything because it was edited retroactively.
MIERDO MILLAS DE VIBORAS FURIOSAS PARA ESTRANGULARTE MUERTO

Baughn

  • Noble Phantasm
  • The Haruhiist
  • Hiss
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #2 on: December 20, 2008, 01:52:08 pm »

Just a speed-up, but for some people it's a *large* speed-up.

Especially if you want to use a 200x200 grid. ;)
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

Baughn

  • Noble Phantasm
  • The Haruhiist
  • Hiss
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #3 on: December 20, 2008, 01:52:28 pm »

Well, and a Linux version, and a properly functioning OS X version
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

Davion

  • Bay Watcher
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #4 on: December 20, 2008, 03:54:01 pm »

Pretty big improvement. Several weird anomalies that many people have been getting, including myself, seem to have been fixed with this; chiefly minimizing doesn't make everything in the window disappear, and if you move the window around it doesn't "bleed". That's with partial print on, at least.

Also getting quite a big FPS boost and it's mostly even across partial print on/off, which I can't say the same for the original Battle Champs. Maxed FPS at 10,000 just to see how far it could go:

Optimized Battle Champs:
Partial Print Off at menus: FPS 800 or around there.
Partial Print Off at battles: FPS 2000-7000 or around there.
Partial Print On at menus: FPS is same as above mostly.
Partial Print On at battles: FPS is same as above mostly.

Original Battle Champs with the same init file and settings as above:
Partial Print Off at menus: FPS 260 or around there.
Partial Print Off at battles: FPS 1800 or around there haven't seen it even hit 2000.
Partial Print On at menus: FPS 900-1000 or around there.
Partial Print On at battles: FPS 900-1300 or around there.
Logged

Greiger

  • Bay Watcher
  • Reptilian Illuminati member. Keep it secret.
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #5 on: December 20, 2008, 04:23:36 pm »

Unfortunately it crashes on startup for me.

Microsoft Windows XP Professional Service pack 3
Intel Celeron 2.4Ghz CPU
Radeon 9250 PCI card (running Omega drivers version 3.8.252)
1.5 GB SDRAM

Drivers and direct x are as recent as I can get the omega driver is the most recent that supports my graphics card.

Fails to run under windowed or fullscreen, partial print on or off.

Is there any other info I could give you that would be helpful?  DF would benefit greatly from a speed increase, but I would like to be able to run it too ;)


« Last Edit: December 20, 2008, 04:31:08 pm by Greiger »
Logged
Disclaimer: Not responsible for dwarven deaths from the use or misuse of this post.
Quote
I don't need friends!! I've got knives!!!

Baughn

  • Noble Phantasm
  • The Haruhiist
  • Hiss
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #6 on: December 20, 2008, 04:56:00 pm »

As a matter of fact, there is.

Visit http://www.realtech-vr.com/glview/, install and run the viewer, then click on report. Copy all the text in the report to a post here - preferably in a spoiler.

(The same program does allow me to see supported extensions for /some/ radeon 9250, but those are not necessarily identical to yours.)
« Last Edit: December 20, 2008, 04:58:47 pm by Baughn »
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

Baughn

  • Noble Phantasm
  • The Haruhiist
  • Hiss
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #7 on: December 20, 2008, 05:00:42 pm »

Oh yes. Also run the rendering test, and tell me the results, please.
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

Greiger

  • Bay Watcher
  • Reptilian Illuminati member. Keep it secret.
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #8 on: December 20, 2008, 05:04:26 pm »

Ok doing so now.  I'll post an edit with results soon.

Here we go.  This is the report.
Spoiler (click to show/hide)
Not an expert on open GL but that didn't look promising.

And the render.
Errors occured during the tests.
Spoiler (click to show/hide)

Test results show as everything passing.  With 0 FPS.  That doesn't seem right to me, but that's what it shows.
« Last Edit: December 20, 2008, 05:33:03 pm by Greiger »
Logged
Disclaimer: Not responsible for dwarven deaths from the use or misuse of this post.
Quote
I don't need friends!! I've got knives!!!

savanik

  • Bay Watcher
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #9 on: December 20, 2008, 05:53:49 pm »

Pretty big improvement.

<snip>

Optimized Battle Champs:
Partial Print Off at menus: FPS 800 or around there.
Partial Print Off at battles: FPS 2000-7000 or around there.
Partial Print On at menus: FPS is same as above mostly.
Partial Print On at battles: FPS is same as above mostly.

I never ran the original, but I'm getting around 8000 fps during battles with partial-print ON, about 4000 with it OFF.

I also have a glitch in this version - running under Linux, if you use 'WINDOWED:NO', the window does not maximize properly, but flickers black breifly before it remains in a window using the Fullscreen resolution. I also got occasional black flickering, as if it were attempting to go fullscreen again but was failing.

If you use 'WINDOWED:PROMPT' and select fullscreen, then you get fullscreen working properly.

This is under Ubuntu 8.10, using an NVidia 8800 GTX with the properitary NVidia drivers loaded. (Not sure if those make a difference, but thought I'd mention.)

Also, take this with a grain of salt, because I'm running in dual-screen and took some heavy-handedness to xorg.conf to achieve this. The program itself runs beautifully (SO much faster than Wine!)... and I don't use fullscreen much, so don't mind it much. :)

Savanik
Logged

Baughn

  • Noble Phantasm
  • The Haruhiist
  • Hiss
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #10 on: December 20, 2008, 06:40:58 pm »

Going fullscreen, it'll actually try to change the screen resolution. If that fails.. something like what you're seeing might happen; I haven't checked that code.

Make sure you've edited init.txt to set the /right/ fullscreen resolution.


EDIT: Hm, actually it just segfaults. I'll have to look at that.
« Last Edit: December 20, 2008, 06:44:07 pm by Baughn »
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

Baughn

  • Noble Phantasm
  • The Haruhiist
  • Hiss
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #11 on: December 20, 2008, 06:49:57 pm »

Ok doing so now.  I'll post an edit with results soon.

*snip*

Test results show as everything passing.  With 0 FPS.  That doesn't seem right to me, but that's what it shows.

Your card is probably fine, but it seems that your drivers are buggy. Considering how large the chance of fixing them is..

I was considering adding a software fallback, but it'd be slow as a dead turtle on that hardware, so not really much point of that either. Sorry.

There is one other option. Linux has an open-source driver for the 9000-series radeons that, miracle of miracles, supports 3D rendering. You should try that.

EDIT: Actually, one last test..
If you run bc.exe from a terminal window (cmd.exe), you should get some debugging output. Does it mention VBOs or arrays?
« Last Edit: December 20, 2008, 06:55:12 pm by Baughn »
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

Thndr

  • Bay Watcher
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #12 on: December 20, 2008, 07:02:21 pm »

Tried this out, got a max of around 4000 breifly, more commonly between 1300 and 2100 depending on size of battle. For some odd reason the slower moving attacks with lesser units go take up framerate, but the initial speedy attack goes the fastest.

With mouse moving//on screen, framerate drops to 600-700
Logged

Christes

  • Bay Watcher
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #13 on: December 20, 2008, 07:17:34 pm »

It's ... so ... fast
Logged

userpay

  • Bay Watcher
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #14 on: December 20, 2008, 07:42:45 pm »

Hmm I guess I'm getting aroun 1500-2000 during battles but its difficult to tell which side is winning.
Logged
Pages: [1] 2 3 ... 147