Search the Community

Could there be a section added under "Video settings" in game wikis for recommended dual gpu setup settings?

Now that quite a few games are out with HDR support, and more planning to come soon, and there's monitors now out with HDR support, and not just TVS, could we add HDR int he Video Settings now? I can't edit it in because the page to do that is protected, so would an admin be able to do it? Here's all the games I could find with HDR currently supported: Resident Evil 7 Shadow Warrior 2 Deus Ex: Mankind Divided Hitman (2016) Mass Effect: Andromada Paragon Obduction Redout: Enhanced Edition And here's some games with upcoming support I could find: Star Wars: Battlefront 2 Need For speed: Payback The Witness The Talos Principle Lawbreakers Rise of the Tomb Raider

Hey all. So I was reading this thread over on reddit that was asking about which games are known to support high frame rates and I thought "I know who has a giant list of games with this kind of info, I'll bet there's a category for this!". Unfortunately upon arriving at the Borderlands 2 page, I was disappointed to see that categories for game properties/attributes have not been implemented. That should be fixed! When I was working on Project STEP's Wiki we wanted the same functionality: sort and categorize pages based on the properties defined in infoboxes and templates. This can be done rather easily thanks to ParserFunction's #if and #ifeq functions. I see a lot of the templates already use these functions so this may be obvious, but as an example, let's implement Category:High framerate support. Framerate support is cataloged using Template:Video settings's "high frame rate" argument. At the moment "high frame rate" is only being used to toggle the checkbox's display. We can add the following text to also categorize the game based on this argument: {{#if: {{{high frame rate|}}} | [[Category:High framerate support]] | [[Category:Limited framerate]] }} Obviously this statement can be expanded to include any number of potential values, although it looks like you're currently only using a Boolean to represent true/false. Anyways, I think this rather simple addition (if applied to most game properties) provides a lot of benefit when it comes to organizing game features, improving discoverability for users, and potentially providing some interesting statistics to ponder thoughtfully over. Thanks for reading, I'd be glad to help flesh out and implement this feature if desired.