0007504: G_FPS Capped at 50 - Dwarf Fortress Bug Tracker

(0028155)
MaximumZero (reporter)
2014-08-02 12:36
edited on: 2014-08-02 12:40

Updated to a clean install of 40.05. Only changes made were in init.txt. Changes made were to have the FPS counter show, to uncap both FPS and G_FPS by setting them to 0, to turn off the intro, and to load the game fullscreen. FPS appears to be uncapped, but even in menus, the G_FPS is stuck at 50 or lower.

Setting FPS and G_FPS to high numbers leads to both FPS and G_FPS respecting the cap, but G_FPS:0 still caps out at 50.

(0028507)
MaximumZero (reporter)
2014-08-06 23:08

Issue continues into 40.06.

(0029272)
lethosor (manager)
2014-08-18 17:16

What platform are you using? Does setting G_FPS_CAP to a specific number (e.g. 60) work? If so, I suspect this is the intended default - init.txt only mentions 0 as a valid setting for FPS_CAP, so G_FPS_CAP probably defaults to 50 if it's out of range.

(0029275)
Quietust (reporter)
2014-08-18 18:25
edited on: 2014-08-18 18:25

init.txt only documents FPS_CAP as being "uncapped" when you set it to 0; G_FPS_CAP has no such note.

If I explicitly set G_FPS_CAP to a large value, then it appears to take effect properly - with [FPS_CAP:1000] and [G_FPS_CAP:500] on Windows 7 x64 with a GTX 760, I'm able to attain "FPS: 1000 (498)" as long as I don't enable VSYNC.

(0029276)
MaximumZero (reporter)
2014-08-18 18:28

Well, since I didn't realize that G_FPS_CAP couldn't be uncapped, this appears to be a PEBKAC error. My apologies, all.

(0029279)
lethosor (manager)
2014-08-18 19:52
edited on: 2014-08-18 19:53

All right. The suggestions forum (http://www.bay12forums.com/smf/index.php?board=5.0 [^]) is a good place to discuss improvements like this (although it should be possible to set G_FPS_CAP to a high enough number that it appears to be uncapped for now).

Issue History
Date Modified	Username	Field	Change
2014-07-19 21:43	MaximumZero	New Issue
2014-08-02 12:33	MaximumZero	Issue Monitored: MaximumZero
2014-08-02 12:36	MaximumZero	Note Added: 0028155
2014-08-02 12:40	MaximumZero	Note Edited: 0028155	View Revisions
2014-08-06 23:08	MaximumZero	Note Added: 0028507
2014-08-18 17:16	lethosor	Note Added: 0029272
2014-08-18 17:16	lethosor	Assigned To	=> lethosor
2014-08-18 17:16	lethosor	Status	new => needs feedback
2014-08-18 17:20	lethosor	Product Version	=> 0.40.04
2014-08-18 18:25	Quietust	Note Added: 0029275
2014-08-18 18:25	Quietust	Note Edited: 0029275	View Revisions
2014-08-18 18:28	MaximumZero	Note Added: 0029276
2014-08-18 18:28	MaximumZero	Status	needs feedback => assigned
2014-08-18 19:52	lethosor	Note Added: 0029279
2014-08-18 19:52	lethosor	Status	assigned => resolved
2014-08-18 19:52	lethosor	Resolution	open => no change required
2014-08-18 19:53	lethosor	Note Edited: 0029279	View Revisions

Notes
(0028155) MaximumZero (reporter) 2014-08-02 12:36 edited on: 2014-08-02 12:40	Updated to a clean install of 40.05. Only changes made were in init.txt. Changes made were to have the FPS counter show, to uncap both FPS and G_FPS by setting them to 0, to turn off the intro, and to load the game fullscreen. FPS appears to be uncapped, but even in menus, the G_FPS is stuck at 50 or lower. Setting FPS and G_FPS to high numbers leads to both FPS and G_FPS respecting the cap, but G_FPS:0 still caps out at 50.

(0028507) MaximumZero (reporter) 2014-08-06 23:08	Issue continues into 40.06.

(0029272) lethosor (manager) 2014-08-18 17:16	What platform are you using? Does setting G_FPS_CAP to a specific number (e.g. 60) work? If so, I suspect this is the intended default - init.txt only mentions 0 as a valid setting for FPS_CAP, so G_FPS_CAP probably defaults to 50 if it's out of range.

(0029275) Quietust (reporter) 2014-08-18 18:25 edited on: 2014-08-18 18:25	init.txt only documents FPS_CAP as being "uncapped" when you set it to 0; G_FPS_CAP has no such note. If I explicitly set G_FPS_CAP to a large value, then it appears to take effect properly - with [FPS_CAP:1000] and [G_FPS_CAP:500] on Windows 7 x64 with a GTX 760, I'm able to attain "FPS: 1000 (498)" as long as I don't enable VSYNC.

(0029276) MaximumZero (reporter) 2014-08-18 18:28	Well, since I didn't realize that G_FPS_CAP couldn't be uncapped, this appears to be a PEBKAC error. My apologies, all.

(0029279) lethosor (manager) 2014-08-18 19:52 edited on: 2014-08-18 19:53	All right. The suggestions forum (http://www.bay12forums.com/smf/index.php?board=5.0 [^]) is a good place to discuss improvements like this (although it should be possible to set G_FPS_CAP to a high enough number that it appears to be uncapped for now).

Relationships