View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005849 | Dwarf Fortress | Init Options | public | 2012-04-29 10:03 | 2012-05-14 09:12 |
| Reporter | Deathworks | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| OS | Windows XP Professional | OS Version | SP 3 | ||
| Product Version | 0.34.07 | ||||
| Summary | 0005849: FPS_CAP also limits G_FPS_CAP causing problems with the UI at low caps | ||||
| Description | I had set FPS_CAP to 1 so as to play Fortress Mode in secure Single-Step-Mode and I noticed major problems with the graphics and the interface. While the game was paused, graphical FPS, the cap of which I had set to 25 as usual, were also around 1 or 0, causing blinking of traffic designation markers to either become static on or static off. In addition, the game responded extremely sluggishly to keyboard commands. Setting FPS_CAP to 25 allowed the graphical FPS to also reach their cap making blinking designations work properly and also allowing the controls to function properly. Judging from the description in the init-file, the FPS_CAP should basically limit in-game FPS and not meta-game FPS like the graphical refresh rate... | ||||
| Steps To Reproduce | Just set FPS_CAP to 1 and G_FPS_CAP to something sensible, like 25, and start fortress mode, designating traffic areas and the like in pause mode | ||||
| Tags | fps, framerate, Intentional/Expected? | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-04-29 10:03 | Deathworks | New Issue | |
| 2012-04-29 10:04 | Deathworks | Tag Attached: fps | |
| 2012-04-29 10:04 | Deathworks | Tag Attached: framerate | |
| 2012-05-14 09:12 |
|
Tag Attached: Intentional/Expected? |
