Template talk:Config: Difference between revisions

Jump to navigation Jump to search
Line 60: Line 60:
::Two options are needed as they are separate options, one specifies the framelimit to set (Off,Auto,10-120) the other specifies to use FPS for limiting rather than the games internal frame rate. In theory, since I don't think "framelimit" will ever be relevant to compatibility, it could be dropped, but it's probably best to not get into such fine grained analysis of this (i.e. it would likely be painful to work out which settings are compatibility related vs not). [[User:Kolano|Kolano]] 22:27, 15 August 2011 (CEST)
::Two options are needed as they are separate options, one specifies the framelimit to set (Off,Auto,10-120) the other specifies to use FPS for limiting rather than the games internal frame rate. In theory, since I don't think "framelimit" will ever be relevant to compatibility, it could be dropped, but it's probably best to not get into such fine grained analysis of this (i.e. it would likely be painful to work out which settings are compatibility related vs not). [[User:Kolano|Kolano]] 22:27, 15 August 2011 (CEST)
:::Okay, then there's the confusion.  There are THREE options.  framelimit, limitbyfps, and fpsforlimit.  I totally agree that framelimit and limitbyfps need to stay.  I think that fpsforlimit overlaps with framelimit.  framelimit should be used to indicate Off, Auto, or 10-120.  fpsforlimit should be deprecated.  --[[User:Keller999|Keller999]]
:::Okay, then there's the confusion.  There are THREE options.  framelimit, limitbyfps, and fpsforlimit.  I totally agree that framelimit and limitbyfps need to stay.  I think that fpsforlimit overlaps with framelimit.  framelimit should be used to indicate Off, Auto, or 10-120.  fpsforlimit should be deprecated.  --[[User:Keller999|Keller999]]
:::Ah, now I see and agree. fpsforlimit should be deprecated, and limitbyfps preserved. [[User:Kolano|Kolano]] 22:45, 15 August 2011 (CEST)

Navigation menu