Gaming Hardware Why PC Game System Requirements Are Often Misleading Sebastian Castellanos • at EDT Add on Google PC system requirements should be simple. You look at the minimum, recommended, and potentially higher-tier specs, compare them to your rig, and get a solid idea of what to expect. Easy enough, right? Well, not anymore, sadly. Over the last decade or so, PC game system requirements (or PC specs) have become incredibly messy, inconsistent, and sometimes borderline useless. We are dealing with vague targets, aggressive temporal upscaling hidden behind an inconspicuous “1080p” or “4K” label, and "60 FPS" targets that incredibly rely on frame generation, which is absolutely not the same thing as actually rendering 60 full game frames per second. Heck, now and then, publishers even list hardware that doesn’t actually exist! Related Story CONTROL Resonant Skates By on Modest PC Specs Despite Path Tracing and DLSS 4.5 AmbitionsTo be clear, this isn't just a lazy rant about games getting harder to run. Some titles genuinely push visuals, simulation, geometric complexity, and lighting fidelity hard enough to justify heavy specs. Remedy's Alan Wake 2, for example, is an incredibly ambitious game visually, and it is completely fair for a game like that to ask more from your GPU than a less visually impressive title. The real problems in our view are proper communication and accuracy. If a game needs temporal upscaling, then its specs sheet should say so clearly. If you, as a game developer, are unsure about a certain piece of hardware, then make sure it actually exists before slapping it into a PC specs infographic for your game. Right now, a lot of PC system requirements feel less like tested and useful guidance and more like vibes with a hardware list attached. “Minimum” And “Recommended” Specs Often Don’t Mean Much Without Proper Context The oldest problem with PC system requirements is also the simplest one: minimum and recommended specs are not standardized across the industry. One developer’s “minimum” might mean 720p@30 FPS on the absolute lowest settings. Another’s might mean a decent “1080p@60 FPS on medium settings” experience. And for some, it basically means "the game boots and technically runs, good luck". "Recommended" is not much better. It could mean 1080p@60 FPS, 1440p@60 FPS, 4K@30 FPS, High settings, Medium settings, ray tracing enabled, upscaling disabled, or some obscure, internal test scenario that is never actually disclosed to the player. That is a major issue, because a CPU/GPU list by itself does not tell you what the game will actually feel like. A requirement sheet should answer a few basic questions: What resolution is this targeting? What graphics preset? What average FPS? What about 1% lows and shader compilation stutters? Was the benchmark done in a quiet corridor, a busy city hub, or a worst-case scenario combat sequence? Most PC game requirements sheets still leave us guessing, and when they do include extra notes, those notes sometimes make the whole thing look worse, not better. The recently announced CONTROL Resonant PC requirements perfectly showcase the problem of system requirements without proper context. Temporal Upscaling Is Fine, But Not So Much At Lower Resolutions The biggest modern offender is probably temporal upscaling, which the overwhelming majority of modern AAA games rely on to achieve their visuals and performance targets, especially on game consoles. Let's be fair here: temporal upscaling itself is not bad. NVIDIA DLSS Super Resolution, AMD FSR upscaling, and Intel XeSS Super Resolution can be genuinely excellent performance-enhancing tools when implemented properly and used correctly. In many modern PC games, DLSS 4/4.5 SR and FSR 4/4.1 upscaling in Quality mode at 1440p and 4K oftentimes look cleaner and sharper than native resolution rendering with your average temporal anti-aliasing (TAA) implementation. Nobody serious is pretending that the use of temporal reconstruction technologies is automatically a bad thing. The issue is when system requirements use the output resolution as the big headline while hiding the internal rendering resolution in the fine print. Star Wars Outlaws did something similar across its whole PC specs chart. Ubisoft listed almost every tier with the temporal upscaler set to "Quality" mode, which would correspond to an internal rendering resolution of 720p for NVIDIA DLSS SR and AMD FSR upscaling (with XeSS SR Ultra Quality mode being the equivalent mode for Intel Arc GPUs). Here's the thing: upscaling from 1440p to 4K will look great with modern temporal upscaling technologies, but upscaling from 720p (or worse, 540p AKA “Performance mode” upscaling) to 1080p is incredibly fragile. It often leads to heavy visual artifacting, blurry visuals, and shimmering edges, yet it's increasingly becoming normalized as baseline specs. While the Star Wars Outlaws PC specs are actually very decent and detailed by modern standards, the heavy reliance on temporal upscaling — even at a relatively low resolution of 1080p — is a sore point that we feel is worth calling out. Frame Generation Should Never Be Used To Define A Baseline FPS Target Frame generation is even more problematic than temporal upscaling when used in PC game system requirements. Again, the technology can work really well in the right scenario and the right game. If you are already running at a solid base frame rate (at least 50-60 FPS is recommended by most GPU vendors) in a game that’s not overly sensitive to input latency (like story-heavy single-player games, for example), then it can make a game look dramatically smoother, at the cost of higher input latency and some potentially visible visual artifacts. But generated frames are not the same as rendered frames. NVIDIA’s own documentation makes this clear: frame generation inserts interpolated frames between game-rendered ones. That means the game is not actually simulating, rendering, and responding to your input at that displayed FPS number. It looks smoother, but the underlying base frame rate still dictates your input latency, animation cadence, and overall responsiveness. That is why using frame generation to advertise a 60 FPS recommended target simply feels wrong. Monster Hunter Wilds, unfortunately, pioneered this trend, targeting 1080p@60 FPS at Medium settings but noting that this target requires frame generation. In plain English, that system isn't running a true 60 FPS baseline; it's a 30 FPS baseline with interpolated frames that are inserted between the rendered ones. Frame generation works best when performance is already high. As such, if the baseline performance is poor or stuttery, then generating extra frames just puts lipstick on a pig — the FPS counter would look nicer, but the game would still feel sluggish, unresponsive, and look highly artifact-ridden. The Monster Hunter Wilds PC specs started the highly unfortunate trend of game developers relying on frame generation technologies to achieve playable framerates. Higher Resolutions Do Not Automatically Justify Much Faster CPUs Another weird habit on these charts is scaling CPU requirements in ways that do not make technical sense. Generally speaking, raising your resolution increases GPU load far more than CPU load. Going from 1080p to 1440p or 4K makes the graphics card work harder because it has to shade more pixels, which places more strain on its compute and memory bandwidth resources. The CPU still matters for simulation, physics, and streaming/decompressing assets, but resolution itself is a wholly GPU-side burden. That is why some PC game requirements charts look bizarre when the CPU tier rises sharply alongside resolution, without any change to the framerate target or game complexity. There are valid exceptions, like a higher framerate target, heavier NPC density, expensive physics simulations, or more complex ray tracing BVHs (bounding volume h...