Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[penguinofhonor]

So we argued about whether or not this would happen, and the answer is yes.

I get 13 FPS with the increased screen size and 20 FPS with the default.

[Toady One]

Where is this, and what settings did you use?  How do they compare on the title screen?  I'm hitting the default caps on the title screen and during play using 160x50, but it's all going to depend on the drivers and so on.

[avari]

I got a major FPS drop too and I think something strange is going on. The game seems to run during play as if the FPS cap was at 50, regardless of what is in the init file.

A fort in the previous version ran at 100 FPS (capped). The same fort in the new version gets 50 FPS flat. The grid size seems to have no discernible effect, as I tried from 80:25 to 105:65 and got the exact same FPS. Also paused/unpaused both run at the same 50 FPS. Or to be more specific, the FPS varies rapidly between 49 and 50, exactly as if 50 was the cap.

The title screen, however, gets full FPS and respects the init FPS cap.

[penguinofhonor]

Where is this, and what settings did you use?  How do they compare on the title screen?  I'm hitting the default caps on the title screen and during play using 160x50, but it's all going to depend on the drivers and so on.

At
[WINDOWED:YES]
[GRID:80:25]
[WINDOWEDX:640]
[WINDOWEDY:200]
[FONT:customsmall.bmp] (an 8x8 tileset)

I get 102 FPS on the title screen even though my FPS cap is 100.

At
[WINDOWED:YES]
[GRID:110:50]
[WINDOWEDX:880]
[WINDOWEDY:400]
[FONT:customsmall.bmp]
I get 17 FPS on the title screen, which is definitely a problem.

[returntonull]

Looks like it's using the G_FPS_CAP here whether it's in graphical mode or not now. Although that doesn't explain penguin getting the 13 and 20.

[avari]

Looks like it's using the G_FPS_CAP here whether it's in graphical mode or not now. Although that doesn't explain penguin getting the 13 and 20.

You are absolutely correct. I thought I tested the G_FPS, but apparently didn't as it works perfectly. Now with the correct cap I see that there is indeed a significant FPS drop (starting at the title screen) when larger views are used.

It seems that for some reason, the FPS drop is more severe for windowed mode than fullscreen mode.. at least for me.

Edit: Actually, it might not be more severe for windowed after all. I was confused because with larger views the FPS starts greatly reduced but jumps back up when I move the window (??). After that it seems to work ok, although using about 40% cpu compared to 1-5% with the default size

[Cavalcadeofcats]

Went to test after seeing this thread. World generation is definitely dramatically slower at larger window sizes, though I don't have numbers for that; after generation though, I got ~50 fps in a fresh fortress with

[WINDOWED:YES]
[GRID:80:25]
[WINDOWEDX:640]
[WINDOWEDY:300]
[FONT:curses_640x300.bmp]

and capped FPS at the menu screen. (GFPS was not capped at 50, returntonull; I'd capped both it and FPS at 80 to eliminate that factor.) On the other hand, with

[WINDOWED:YES]
[GRID:200:80]
[WINDOWEDX:1600]
[WINDOWEDY:960]
[FONT:curses_640x300.bmp]

I got 30 FPS at the menu screen, and ~15 in that same new fort. (Man, seeing such a huge chunk of the map at once is incredible.

I did the testing in a fresh, unmodded 39f install. Hopefully that's helpful.

[penguinofhonor]

Yeah, I have no mods, although I don't think mods matter with this.

Also, I was going to check the FPS in the old version to see whether or not I got higher FPS in the old version, but it appears 39f saves are not 39e compatible.

[Toady One]

I jacked myself up to 200x150 and started noticing some problems during play that I think come from the map printing routine (rather than opengl).  Lags at the title screen are likely opengl related...  and that'll come down to drivers or the card, I think, though I can't be sure.  My laptop didn't have a great graphics card when I got it ~three years ago, but I filled a 200x150 grid and a 1280x800 window with random characters and am still getting 100FPS.  That's not to say that the opengl code can't be improved, but it isn't a catastrophe, anyway.  During play itself, in the main play screen, viewing the map at the same settings, I get 16FPS, but 30 when I go underground, which points to the pre-ogl stuff.

[The-Moon]

I have a FPS drop also, from about 150 to 10FPS.

However, the game is not running slow, its still running at the same speed as normal, its just the FPS counter is displaying 10 rather then the real FPS.

Because the games definitely not running at 10FPS, at least 100.

I'm using 80x66 screen size on a 1280x1048 screen size.

Games still running smooth and fast but its just displaying the wrong FPS.

Even when i pause the game its still at 10FPS, when i have a cap of 200.

My G_FPS_CAP is set to 10, maybe its displaying this for some reason?

[Tormy]

My windowed size is doubled now in the new version, I used to have buttload of FPS, now I got 50 after embarking? What the hell just happened? 

[penguinofhonor]

Oh, yeah, another thing to point out is that I definitely had more than 20 FPS in the normal sized screen. My G_FPS is 20, so I think we're seeing a trend here.

[Eiba]

For one thing, it seems that the top corner is always refering to your GFPS now, which is by default 50, but should really be 10-20 to optimize performance.


Anyway, here's a really weird bug relating to screen size and FPS.

At 80:25 on the title screen, my FPS is at the cap, 100. At 80:50, it's down to 37 for some reason (this is already Very Wrong). As an experiment I upped my FPS cap to 1000, and tried again. At 80:25 I got about 750 FPS, which was fine, but the really weird bit is that at 80:50 I got around 250 FPS.

In other words, raising the cap raised the FPS on the title screen, when it didn't reach the cap before.

Just eyeballing it, it doesn't look like there's any difference in Fortress Mode (it's much slower at 80:50 than 80:25, but the same slowness despite my FPS cap). Of course I can't quantify this with the FPS indicator as it is.

...

On closer inspection this weird behavior is probobly just a problem with the FPS display on the title screen, as I just upped the FPS cap to 10,000 and at 80:25 the FPS was around 5000. (At 80:50 it was at 1000).


So the real issue here is that doubling the screen size for me reduces the FPS to about a third of what it used to be. This does seem to carry over to Fortress Mode.

[Hyndis]

I got a definite FPS drop myself, and I left the window size as default. Temperature and weather also turned off, just like in 39e, and I'm at 45-50 FPS rather than the 90-100 FPS I was getting yesterday on this very same saved game.

[Davion]

[WINDOWED:YES]
[GRID:150:80]
[WINDOWEDX:1200]
[WINDOWEDY:960]
[FONT:curses_640x300.bmp]

100 FPS on the main screen.

As soon as I hit Fortress Mode it starts at 40-50 paused, and around 35 unpaused, and that's just with the starting seven.

Also getting a big jump in CPU usage, usually it's around 10-20% while playing at the default size, but with the expanded grid/window it's about 50+%, maybe that's just the way it is with so much more visible.

[WINDOWED:YES]
[GRID:80:25]
[WINDOWEDX:600]
[WINDOWEDY:300]
[FONT:curses_640x300.bmp]

With default window/grid sizes it's 100 FPS at main screen.

50 FPS in Fortress Mode with starting seven.