Probably not the best thread title but essentially what I am looking to do is put forward my view on how PC FPS games should be configured on a functional level, but in particular focussing on areas that should be fairly easy to achieve. It would be easy to say stuff like 'all PC games should be fully optimised', 'all PC games should have full control over all graphics options' but they are very ambiguous statements that may actually be quite difficult to implement and vary from game to game. So the purpose of this is to list out what are really quite mundane features I would like to see all PC FPS games have; essentially these options are the inverse of some pet hates I have come across over the years with many games:
- All actions rebindable to any key, including the ability to split context-sensitive actions that may have a shared button on console (it's really annoying having games where things like Melee attack or take cover is paired with something else so you stand there swinging your rifle butt at thin air while an enemy stands there trying not to laugh whilst emptying an entire clip into your lumbering corpse)
- On a related note, tutorial/hints/QTE etc should display the key the function is bound to, not the default key (or even worse in the case of some games, an XBOX button :/)
- Skills / inventory items etc individually mappable rather than using a wheel select or whatever
- Adjustable FOV
- Ability to pick any resolution and refresh rate supported by the display driver (to be fair, most games are pretty good with this now)
- Mouse sensitivity adjustable within an infinite range (I've played games that don't let you set it low enough if using high DPI)
- Skippable / pausable cutscenes (it's annoying in story-rich games when the phone rings during a crucial one!)
- Uncappable framerate
- Ideally manual saving with a multiple rolling quicksave (i.e. Quicksave doesn't always overwrite the last save but instead cycles through say 3 save points) but at the very least for the love of god no checkpoints immediately prior to a cutscene
- Ideally some sort of repeatable benchmark/timedemo function to help with optimising settlings for performance on a variety of hardware
- Ideally a customisable HUD (scaling at the very least to accommodate different resolutions)