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 ... 35 36 [37] 38 39 ... 147

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

Savok

  • Bay Watcher
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #540 on: January 02, 2009, 10:20:14 am »

NNN:
Ubuntu: 1000fps menu/pause
325fps (oh god) unpaused
Windows XP: 250fps menu/pause
125fps (not bad, but... heh) unpaused

YYN:
Ubuntu: 3fps menu/pause
3fps unpaused
Windows XP: 0fps menu/pause
0fps unpaused

So, DF is mega muchos faster on Linux, but partial print is broken for me. I must admit that at this point I don't really care; it's working way too well for me to mind the lack.
« Last Edit: January 02, 2009, 10:39:47 am by Savok »
Logged
So sayeth the Wiki Loremaster!

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 #541 on: January 02, 2009, 10:27:25 am »

The slowness bug has been identified - I'd set one variable to "unsigned int", when it needed to be signed. Only affects windows, by the way.

Between that, and other differences between my code and Toady's, I never saw it coming. Heh. Still, things are settling down.


Savok: Don't you care because you've seen too much death and destruction, dwarf-like, or because it's working well enough for you now?

EDIT: Oh, good.
« Last Edit: January 02, 2009, 10:43:20 am 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 #542 on: January 02, 2009, 10:34:55 am »

Mind you, you still won't get over 2000 fps in the main menu. The timer isn't accurate enough for that. The difference is, you'll get 2000fps at a few percent of cpu use, at most, instead of at 100% cpu use.

You also won't be able to get over 2000fps in-game; though you should get *more* fps, that's somewhat of a hard cap. If this is a problem for anyone, feel free to let me know.


For the curious: What was actually happening was the the (unsigned) graphical frames pending-counter was underflowing and becoming vastly positive, which means you get g_fps equal to fps, all the time. Well, more or less; there's some subtlety to that, but the point is that it was doing way too much work.
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 #543 on: January 02, 2009, 10:42:41 am »

By closer examination, what you actually get is 100x the g_fps framerate as a max. If this is a problem for anyone, please tell me; meanwhile, I'm trying to fix it on general principle.
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 #544 on: January 02, 2009, 11:02:18 am »

Aand.. fixed.

EDIT: Kind of. Now it's doing more frames per second than the FPS counter is willing to actually show. *shrug*
« Last Edit: January 02, 2009, 11:14:06 am by Baughn »
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

chewd

  • Bay Watcher
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #545 on: January 02, 2009, 12:24:19 pm »

I tried it with a few of my high-population forts 120 - 160 pop.

No noticeable improvement on my machine... i tried dozens of different settings.
Logged

PTTG??

  • Bay Watcher
  • Kringrus! Babak crulurg tingra!
    • View Profile
    • http://www.nowherepublishing.com
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #546 on: January 02, 2009, 12:51:33 pm »

So far, so good, even with my modded raws and inits. I've even loaded a save of a mature fort at am getting almost twice the frame rate.
Logged
A thousand million pool balls made from precious metals, covered in beef stock.

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 #547 on: January 02, 2009, 01:15:12 pm »

Those of you who are getting disappointing framerates (chowd, I'm looking at you) should try the linux version of DF, as that edition dodged the slowing-down bug in 40d6.

Or you could wait for d7.

That said, http://wubi-installer.org/ is a very easy, utterly foolproof way to install linux.
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

Ampersand

  • Bay Watcher
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #548 on: January 02, 2009, 03:10:30 pm »

The only problem with using the Wubi installer is that it will automatically install the AMD64 version of Linux if you have a 64 bit processor, which includes the Intel Core2 line, which is fairly common around now, and I'm not sure if Dwarf Fortress will work in it. I can't get it to function in Ubuntu at the moment, but I have a feeling it's dependency issues more than anything else.
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 #549 on: January 02, 2009, 03:13:50 pm »

It's compiled in 32-bit mode, but should work fine in 64-bit Ubuntu; it works fine in 64-bit Gentoo here. You just need the 32-bit compatibility libs, including the SDL ones.

(Anyone actually running Ubuntu, feel free to chime in with the package names)
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

Andir

  • Bay Watcher
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #550 on: January 02, 2009, 03:37:33 pm »

It's compiled in 32-bit mode, but should work fine in 64-bit Ubuntu; it works fine in 64-bit Gentoo here. You just need the 32-bit compatibility libs, including the SDL ones.

(Anyone actually running Ubuntu, feel free to chime in with the package names)
It would be (pretty much) the same as my 64-bit Debian Lenny install.  Make sure you have ia32-libs.  I think Ubuntu actually has ia32-SDL libs as well.  I don't remember what they are called though.  Searching through Synaptic should find them.  Also: "ldd -v dwarfort.exe" should give a list of library dependencies.
Logged
"Having faith" that the bridge will not fall, implies that the bridge itself isn't that trustworthy. It's not that different from "I pray that the bridge will hold my weight."

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 #551 on: January 02, 2009, 04:04:48 pm »

Adding the -v gives perhaps *too* much information, and note that it's a recursive search - you get the libraries' dependencies as well - so the dependencies on your system do not neccessarily match the dependencies on another's.

Also, some of the dependencies are bundled with DF, in the libs/ directory. The df script sets the neccessary environment variables to have it search there.
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

aliosha

  • Bay Watcher
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #552 on: January 02, 2009, 04:07:32 pm »

Mine ran at 6 fps! What's wrong?

Here's the output of ./df:
ME@MY_COMPUTER:~/DF/df_linux$ ./df

Code: [Select]
(dwarfort.exe:17952): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer

(dwarfort.exe:17952): GLib-GObject-CRITICAL **: g_signal_handlers_destroy: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(dwarfort.exe:17952): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer

(dwarfort.exe:17952): GLib-GObject-CRITICAL **: g_signal_handlers_destroy: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Using OpenGL output path with client-side arrays
Ideal catalog size: 260x260

And here's the output of glxinfo | grep rendering
Code: [Select]
ME@MY_COMPUTER:~/DF/df_linux$ glxinfo | grep rendering
direct rendering: Yes


Can anyone help?
Logged

Savok

  • Bay Watcher
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #553 on: January 02, 2009, 05:31:32 pm »

What is your graphics card? Is partial printing on?

My graphics card is rather old and partial printing ruins my fps in both Linux and Windows.
Logged
So sayeth the Wiki Loremaster!

The13thRonin

  • Bay Watcher
  • Profession: Handsome Rogue
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #554 on: January 02, 2009, 07:14:52 pm »

6x6 Embark screen with running river and 500-700 FPS...

Amazing  :).
Logged
I'm Digging Deeper... AGAIN... You Should Too!

Dig Deeper DIAMOND - 750+ items of new content including; new plants, new creatures, new metals, new woods, new gems, new stones, new crafts and much, much more.
Pages: 1 ... 35 36 [37] 38 39 ... 147