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 [4] 5 6 ... 147

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

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 #45 on: December 21, 2008, 11:16:03 am »

Not yet. If you'll tell me what the console output is, I'll have a much better shot at /making/ it work.

It should be noted, if I can't make it work on ATI cards, then it won't go into DF.
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

Orkel

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

Not yet. If you'll tell me what the console output is, I'll have a much better shot at /making/ it work.

It should be noted, if I can't make it work on ATI cards, then it won't go into DF.


The console says:

Spoiler (click to show/hide)
Logged
Quote from: madjoe5
Dwarf Fortress: The game in which people place abducted children in a furnace to see what happens.

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 #47 on: December 21, 2008, 01:16:30 pm »

Ah.. I'm afraid that version is outdated, and won't help me. Could you re-download and try again?

Oh, and you /are/ on windows, right?
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

Orkel

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

Ah.. I'm afraid that version is outdated, and won't help me. Could you re-download and try again?

Oh, and you /are/ on windows, right?

Yeah, I am. Windows XP.

I redownloaded, this time it says:

Spoiler (click to show/hide)

The 1791 changed into a 1709. But otherwise the same thing.
Logged
Quote from: madjoe5
Dwarf Fortress: The game in which people place abducted children in a furnace to see what happens.

KaelGotDwarves

  • Bay Watcher
  • [CREATURE:FIRE_ELF]
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #49 on: December 21, 2008, 01:44:55 pm »

No. You can expect an improvement, assuming I manage to fix the dreaded red-screen bug, but not *that* much of one.

BC's cpu budget is basically all spent rendering. That's what I've been improving.

DF does a significant amount of other stuff.

If you want an idea of how much it might improve things, run DF with partial-print off and watch how much CPU time it uses on the main menu (for one core only, mind). That's the maximum improvement that can happen - eg. if it uses 50%, a doubling in speed is possible; 11%, only a 10% increase.
Just a note but when I run DF on my laptop it does eat up 50%.

Anyhow, interesting stuff. Keep at it.

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 #50 on: December 21, 2008, 02:16:16 pm »

Yeah, but the line number tells me exactly /what/ failed, which is.. uh... the hell?

..okay.

I'd written the code to check for non-power-of-two textures a bit badly, which I've fixed now (you may want to try again, again), but it should work. *Should*. It doesn't, so.. I'm about out of ideas.

Just one more time, then.
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 #51 on: December 21, 2008, 02:57:55 pm »

All right, I've figured it out.

For some reason it's picking the software renderer for some of you, despite my specific request for it not to. Let's see if I can't fix that.
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

Soldats

  • Bay Watcher
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #52 on: December 21, 2008, 03:05:18 pm »

well if ati cards really do become a big problem for you I have an old abused Ati 9800 pro (agp x8)I might be able to send you if shipping is not too much (dont know where you live but im in philadelphia) It should still work but i havent used it in years though
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 #53 on: December 21, 2008, 03:27:24 pm »

I may have fixed the problem.

As it turns out, if you ask ATI cards for hardware acceleration, they specifically refuse to give you any. If you don't, they'll give. So I removed the request.

This is insane, but there you go. Please test.


EDIT: On balance, I expect the explanation is that ATI cards are female. nVidia cards work, so obviously they're male. I wonder what their offspring would be like...
« Last Edit: December 21, 2008, 03:29:53 pm by Baughn »
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

Soldats

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

Ok! New problem! I can now actually see some things but no matter what I do it is always stuck at 43 FPS (tried adjusting various inti options with no success) I would understand if it was 42 fps........
EDIT: On balance, I expect the explanation is that ATI cards are female. nVidia cards work, so obviously they're male. I wonder what their offspring would be like...
Lies!!!! Ati cards just like to be asked politely
also I wouldnt try that ati+nvidia=? experiment I already put an ati card on a nvidia motherboard IRQL errors ahoy!

EDIT: Also i get a crap ton of text in the command window
Spoiler (click to show/hide)
« Last Edit: December 21, 2008, 03:53:48 pm by Soldats »
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 #55 on: December 21, 2008, 03:55:33 pm »

Right now vsync is locked to on, which goes some way to explaining the issues. I knew I forgot something.

..try now.

Oh. Also, you should never set G_FPS_CAP higher than your monitor refresh rate. Lower is fine; try 20 or 25.
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

Orkel

  • Bay Watcher
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #56 on: December 21, 2008, 03:57:04 pm »

I may have fixed the problem.

As it turns out, if you ask ATI cards for hardware acceleration, they specifically refuse to give you any. If you don't, they'll give. So I removed the request.

This is insane, but there you go. Please test.


EDIT: On balance, I expect the explanation is that ATI cards are female. nVidia cards work, so obviously they're male. I wonder what their offspring would be like...

Works now :)

Logged
Quote from: madjoe5
Dwarf Fortress: The game in which people place abducted children in a furnace to see what happens.

Soldats

  • Bay Watcher
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #57 on: December 21, 2008, 04:36:06 pm »

Ok here are my findings on my 4870

All Standard Settings no tweaks
fps=43........:P

Standard settings with 20 g_fps cap
Fps=100

Standard plus 1000 fps cap, 20 g_fps cap
fps=831 Very stiff fps too it almost never fluctuates 

Standard plus 1000 fps cap, 30 g_fps cap
fps=731 Very stiff fps too it almost never fluctuates

Standard plus 5000 fps cap, 20 g_fps cap
fps=859 Very stiff fps too it almost never fluctuates

Standard plus 1000 fps cap, 20 g_fps cap, double grid size 160:50
fps=817 Very stiff fps too it almost never fluctuates plus the screen is super small but that is to be expected

Standard plus 1000 fps cap, 20 g fps cap, double gride 160:50,double res 1280x600
fps=817 Very stiff fps too it almost never fluctuates

partial print had no effect on performance what so ever so i kept it off (to be expected I guess since nothing is staying still for too long?)
seems to me that some form of vsync is still interfering, also my refersh rate of monitor is 60hz

Going to redownload again and try standard and some of the other tests to see anything changes will edit in the results

EDIT:Redownloaded with a cleared Browser cache
All Standard
no change

Standard plus Fps 1000 cap
fps=43

*NEW TEST*
Standard plus g_fps 49 cap
fps=43

I kept moving the g fps number to see when it would stop limiting my fps turns out if g fps is 43 or lower it would revert to the above numbers other wise no change in any other test
« Last Edit: December 21, 2008, 04:52:16 pm by Soldats »
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 #58 on: December 21, 2008, 05:43:55 pm »

Oh-kay.

I did a (highly questionable) change that may help with that. Try it again?

EDIT: Basically, Windows is *unable* to sleep for less than ten milliseconds, so instead I'm having it busy-loop. This should ensure that you get the maximum possible framerate, unless there are still vsync-issues; it should also cause your CPU to stick at 100% no matter what.

Also, if you have a really weak GPU, then setting G_FPS_CAP too high can cause the program to try pushing frames faster than the GPU can handle, in which case it will block waiting for the GPU to catch up. This is murder on your FPS, as you've noticed.
« Last Edit: December 21, 2008, 05:48:58 pm by Baughn »
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

Xgamer4

  • Bay Watcher
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #59 on: December 21, 2008, 06:50:08 pm »

I tried running it on my laptop. ATI Radeon X1100, I believe. It's running the Omega drivers. It pops up the BC screen and shows a bit of red text, as if it's trying to display something, and then the screen goes black. The console output is this:
Spoiler (click to show/hide)

What were the other things you wanted me to run?
Logged
insert something mind-blowing/witty here*
Pages: 1 2 3 [4] 5 6 ... 147