Guest Share Posted October 20, 2015 How should they be handled on the wiki? Link to comment Share on other sites More sharing options...
Marioysikax 89 Share Posted October 20, 2015 I would assume that exactly the same way that 144Hz. That means on game articles stating 60 FPS and 120+ FPS support and noting possible frame rate caps and anomalies (like game changing monitors refresh rate, physics going haywire, things being sped up or game speed being tied to frame rate). Having that info with vsync information also helps with G-Sync/Freesync monitor owners, because to take advantage of those displays vsync needs to be disabled and game not being capped at 60 FPS. Also I'm certain this has been discussed many times before already and I'm still in favor of FPS cap field instead, but right now current system works fine enough and people can more easily contribute as not everyone have machine to test does the games frame rate cap at 300 FPS or at infinity. Mirh 1 Link to comment Share on other sites More sharing options...
Garrett 214 Share Posted October 20, 2015 165 Hz, like 144 Hz, is still very close to 120 FPS (and most 120 FPS-capable games will be able to run at 144/165 FPS as well). There are currently no displays supporting a 240 Hz input (as far as I know)--displays marketed with this refresh rate are actually using interpolation from a lower input (120 Hz or similar). Once actual 240 Hz displays exist it would be time to consider introducing another field. Link to comment Share on other sites More sharing options...
Mirh 103 Share Posted October 22, 2015 Once actual 240 Hz displays exist it would be time to consider introducing another field. Hell, please. We should stop this. We can't increase and increase with no clue the limit every time. And whatever the choice we are going to make anyway (which subtly refer to the way table is presented, aka a single row vs two separated), I can't see any without the cap field idea. ps: please, there's no argument like "but there are many things that could be limited after all (gameplay/FMV/animations)", because we are already making a -implicit- choice in the current state of things Link to comment Share on other sites More sharing options...
Garrett 214 Share Posted October 22, 2015 As covered in the previous discussion, I'm not sure what advantage a dedicated FPS cap field would have over continuing to use the existing 120+ FPS notes section. The 60 FPS split enabled querying within the wiki and increased feature visibility through search engines. A further split to meet an FPS expectation in the future would be for the same reasons. Link to comment Share on other sites More sharing options...
Mirh 103 Share Posted October 24, 2015 The 60 FPS split enabled querying within the wiki and increased feature visibility through search engines. Oh..... Well, if it's about that I see practical purposes can be considered superior to "philosophical issues".. Though I just checked piwik for the most used keywords inside and to the website this month.. and I couldn't find any framerate related query above 2. Albeit that could only account for 4% of all search engines accesses Link to comment Share on other sites More sharing options...
Mirh 103 Share Posted November 9, 2016 https://www.asus.com/Monitors/ROG-SWIFT-PG258Q/ http://www.benq.com/product/gaminggears/xl2540 Link to comment Share on other sites More sharing options...
Recommended Posts