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

[Baughn]

Oh, and I've mentioned this before, but it bears repeating:

Do not, under any circumstances, set G_FPS higher than your monitor refresh rate. All sorts of things will break, and your framerate will probably end up locked to your refresh rate, or twice that.

[Savok]

The logic is fine, but the current timer logic has a hard clamp of 20 frames per graphical update. I've suggested that that should be increased.

If I'm reading that right, setting GFPS at 5 prevents FPS from going above 100. Am I reading that right?

[Inari]

I'm using the Maytag tileset, and DF is crashing A LOT (I assume from the above that the tileset is the problem, since yes, in d2 it was flicking to the curses quite a bit).

I guess I'll be using d2 until it's fixed.

[Fleeb]

D3 crashing when I hold two keys at once (shift key plus arrow key). Reproducible.

[Baughn]

Oh, now that's troublesome.

40d4 just got uploaded. The same bug is in BC, so I can fix it in a snap, but there won't be a new release until tomorrow at earliest.

[Mel_Vixen]

Cant you upload the fix on the DFMA until its on the mainpage tomorow?

D3 crashing when I hold two keys at once (shift key plus arrow key). Reproducible.
 

Happens for me too on embark whenever i want to resize my embarkrectangel

[Baughn]

Basically, no. The fix this time requires changing DF's code.. well, BC's code, so it's something I can do, but still code changes.

[Fleeb]

40d4 same bug, but you know that already, just confirming it.

[Veroule]

Well that clamp value is very troublesome.  The entire reason for being able to set the G_FPS independent of the FPS was so that people with crappy old graphics cards could squeeze a little more speed out.  The clamp ratio value should be calculated during loading of the init.txt by a division of FPS/G_FPS that the user supplied.

Also regarding the issues with setting the G_FPS too high please read the info here: http://www.gamedev.net/reference/articles/article1009.asp

This shows how to get all potential display modes in Windows, this should also be used when making a full screen mode change.  You can use this information to set a proper G_FPS limit when the user has set it incorrectly.  I will leave it up to you to figure out the correct Linux and Mac equivalents.

[Baughn]

You're perfectly right, of course. I'll admit, when I picked that value it didn't occur to me that it'd mess up my fps-per-gfps calculations.

Well, patch sent and all, and really, how often do you get over 200FPS on a computer that only manages 10GFPS?

[Inquisitor Saturn]

Trying both 40d and 40d4, 40d4 seems to in fact have a small DECREASE in framerate. I am using the same save, init file, and art file for both. I had to actually increase the GFPS cap to get it to run as smoothly as the normal version. That's very strange.

[Baughn]

Did you turn on partial printing?

Also, the changed timer logic means it's unable to get quite as close to the framerate cap as it used to be, but there should be no issues once the game starts getting loaded. Just increase the cap a little.

EDIT: I'd like to point out that this thread now has over nine thousand views.

[Xgamer4]

I'm suffering from the "Shift makes everything die" glitch, but you seem to have already known about that little bug. Other then that, it seems to work fine.

[Baughn]

Also, yes, there's the max 20x GFPS-FPS multiplier thing. I've sent a patch for that too, making it dynamic.

[Peewee]

Lol, you people are keeping toady away from his end-of-month break!
Granted, all he has to do is confirm that the updates you send him work, then make them available for download, but still!