- v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
- Use this page to report any issues related to the migration.
Difference between revisions of "v0.31:Maximizing framerate"
m |
|||
| Line 1: | Line 1: | ||
{{AV}} | {{AV}} | ||
| + | {{elven}} | ||
| − | + | Using fewer rows appears to speed framerate (i.e. setting the minimum grid value of [GRID:80:25] in init.txt). Sadly, that's like playing through a periscope. | |
| Line 7: | Line 8: | ||
Please note that this is intended solely as a stopgap until the 40d-graphics merge, so if it doesn't work, don't use it. Baughn has stated that he will not devote time to bugtesting it. | Please note that this is intended solely as a stopgap until the 40d-graphics merge, so if it doesn't work, don't use it. Baughn has stated that he will not devote time to bugtesting it. | ||
| + | |||
| + | Changing [PARTIAL_PRINT:NO:2] to [PARTIAL_PRINT:YES:2] often dramatically improves performance. | ||
Revision as of 03:34, 11 April 2010
Using fewer rows appears to speed framerate (i.e. setting the minimum grid value of [GRID:80:25] in init.txt). Sadly, that's like playing through a periscope.
An alternate measure is the use of Baughn's Accelerator program. This was written for the old 40d stuff before most of the recent graphics updates. It is generally reported to increase performance in both windows and WINE emulated DF games, though there have been some reports of a blue tinge and instability arising from the accelerator. See the Bay12 thread here.
Please note that this is intended solely as a stopgap until the 40d-graphics merge, so if it doesn't work, don't use it. Baughn has stated that he will not devote time to bugtesting it.
Changing [PARTIAL_PRINT:NO:2] to [PARTIAL_PRINT:YES:2] often dramatically improves performance.