Grand Theft Auto 6 is just about to launch and I've seen a lot of discussion about how the game targets just 30fps on the consoles. As usual, when this topic comes up, I hear a lot of interesting justifications as to why 30 FPS is actually fine, and that's what I want to talk about in this video. Some people point to things like graphics quality or gameplay as reasons to why 30 FPS is acceptable. But I think these arguments actually get it wrong or at least fail to properly consider all aspects. You see, 30fps gaming actually reduces visual quality and hurts gameplay, at least in some ways. And I think this is just completely overlooked in most frame rate discussions. I also want to get into why the game runs at 30fps because I think gamers who are a bit less familiar with the hardware side of things don't really understand why a title like GTA 6 is limited to a low frame rate and why certain consoles can't deliver better performance. We can also use this information to predict in some ways how the game will run on PC, which at the very least will be interesting to revisit once it launches officially.
Now, I want to preface this discussion by saying that this video isn't meant to suggest that you can't enjoy GTA 6 because it runs at 30 FPS or that anyone who will play and love the game at 30fps is a big dumb idiot. This is meant more as a technical discussion on low frame rate gaming, the constraints involved, and the trade-offs that come with targeting 30fps. I would have loved to see a 60fps mode for this title. It wasn't to be. And you absolutely can still enjoy this game the way it has shipped. If you're playing it and loving it, don't let this video get in the way of your fun.
The first thing I want to tackle is the relationship between 30fps and visual quality because I think this is the most common point made to try and justify 30fps. The idea is that if the game runs at a lower frame rate, this will deliver a straight up visual improvement because the graphics can be turned up. Pretty simple idea behind this one and at a surface level, it makes sense. Lower the performance, increase the visual quality. This reason is being used in particular with GTA 6 because the title has excellent visual quality given the console hardware it's running on, at least from all the footage that we've seen so far. A lot of gamers were blown away with Rockstar's gameplay trailer, marveling at how GTA 6 looks like a true next-gen title visually. Naturally, the thought is this level of visual quality wouldn't be possible at anything other than 30fps, especially on base consoles like the PlayStation 5.
This part of the visual quality equation is absolutely true. Running games at lower frame rates means you have longer to render each frame. At 60fps, you have 16.7 milliseconds to render the frame, whereas at 30fps, you have 33.3 milliseconds to render the frame. That additional 16 milliseconds at 30fps can be used to crank up the visuals massively. The GPU has a lot more time to slug away rendering more effects, higher quality lighting, and so on. Conversely, if a developer designs a bunch of graphical features around 30fps on a certain hardware spec, those features would need to be cut back significantly to run at 60fps, usually by turning lighting effects off or lowering the resolution. This is often portrayed as a direct relationship. Lower frame rates always equals better visual quality because the in-game graphics are better. But what this omits is that lower frame rates actually hurt visual quality in some areas, particularly when it comes to motion clarity and blur. This makes lower frame rate gaming more of a trade-off situation visually with pros and cons rather than a straight swap of frame rate performance for better visual quality.
30fps gaming is blurry, which hurts visuals. The blur you experience when playing games at 30fps isn't simply due to the motion blur graphics setting being enabled, although that certainly contributes to things. It's also due to the way your display works. The vast majority of modern displays use a technique called sample and hold, where the current frame is held on screen for the entire refresh cycle before being updated at the next refresh cycle. This creates a problem when your eyes are tracking objects in the game that are in motion. Your eyes move continuously when tracking. They don't pause or jitter. It's a smooth biological motion. But the position of the object on the screen is not moving continuously. It's held in one position, then jumps forward to another position in discrete motion. This creates a disconnect between your eye movement and the game's movement. Your eyes will continue to track the approximate location of the object on screen, even when that object is not moving, held there due to sample and hold operation. This smears the image across your retina, which creates blur.
You can check for yourself how this works with any object. Here, I've got about $1.5 million worth of RAM to do this with. So basically, if you move the object in front of your eyes and you sort of track how it's moving like this, you'll see that the object appears nice and sharp. But then if you don't move your eyes and you just move the object in front of them, they will appear blurry because that object is being smeared across your retina. This is what happens on a sample and hold display between refreshes.
This persistence blur increases at lower frame rates because the refresh rate is lower and frames are held on screen for longer. During these tracking movements, your eye will move a long way while the object remains stationary, which maximizes the amount of blur. Higher frame rates and refresh rates reduce the distance your eye travels while an object is stationary, which reduces blur. At very high refresh rates, updates are occurring often enough and fast enough that persistence blur largely disappears, making objects appear very clear in motion. That's a key benefit to very high refresh rate gaming. Now, you can't really eliminate display motion blur even when gaming at 60fps because the refresh rate isn't high enough, but it's a lot better than 30fps. Display motion blur is a key reason why 30fps looks blurry and why it looks blurrier than 60fps. And this blur hurts visual quality. It makes it harder to resolve fine detail in motion. It smears graphical effects and turns a lot of those high-quality shadows, reflections, and so on into a soup.
The degree to which display motion blur hurts visual quality does depend on the amount of motion. Large motions are catastrophically blurry at low frame rates where they wouldn't be at higher frame rates, but relatively small movements can avoid blur to some degree. In fast-paced games like racing games and competitive shooters, you rarely see them configured for 30fps because the amount of fast motion makes 30fps so blurry it's unplayable. GTA 6 being a slower paced single player title combined with Rockstar's classic deliberate animation style means you are less likely to perform fast large movements that trigger insane blur at 30fps. This means it won't be unplayable at 30fps like some shooters would be. But of course, there are still lots of situations where you might be whipping around in a fast car or aircraft. Regardless of the actual type of game though, the fact that 30fps is inherently blurrier than 60fps on modern displays means that lower frame rates can and do reduce visual quality.
And this is where there's a trade-off. Developers creating a game on limited, relatively slow console hardware have to find the right balance in the visual presentation. If you increase the graphical fidelity and make the game more visually impressive when stationary, the game will run at a lower frame rate and become blurrier in motion, obscuring a lot of that visual fidelity. Depending on how the game plays, there does become a point where adding better graphics is pointless, because it won't be visible through the blur. That's partially why developers of faster paced games don't blow the budget on graphics and instead target 60 or even 120fps. With GTA 6, Rockstar Games clearly feel the balance is better if graphical fidelity is increased at the expense of motion and display blur. Some gamers will disagree, of course, but that's the way the developers see it.
Related to this is how 30 FPS affects gameplay. One of the comments I've seen related to 30 FPS in GTA 6 is how this frame rate was necessary to integrate all the gameplay systems Rockstar wanted, from high NPC density and long draw distances to all the complexities in animation physics and more. Again, the thinking here is that it's a direct relationship. Lower frame rate means more gameplay systems, therefore better gameplay. But again, 30fps actually hurts gameplay in one key area, and that's input latency. Gameplay, of course, refers to how players interact with the game. So that includes everything from interacting with copious in-game systems and mechanics to how the game feels to play at a fundamental level. How fast and responsive it is to move the character and interact with the world. Lowering the frame rate may enable the developer to increase the amount of systems within the world, but this comes at the cost of game feel and responsiveness. GTA 6 will feel slower and more sluggish to play than titles targeting 60fps or higher, even normalizing for slower animation styles.
The maths behind this is simple in some ways, right? 60fps, 16.7 milliseconds between frames. 30fps, 33.3 milliseconds between frames. Therefore, it takes at least an additional 16.7 milliseconds for any input you make to be rendered out and shown on screen. Now, some of you may see these numbers and go, okay, well, 17 milliseconds of additional lag doesn't sound too bad, and a potential total lag of under 35 milliseconds sounds quite playable. So, what's the big deal there? Well, 33.3 milliseconds of total lag when gaming at 30fps is completely unrealistic, unfortunately. Firstly, there is a display side component to input latency related to the scan out, which typically increases at lower refresh rates. For a scan out that takes as long as the entire refresh cycle to complete, a worst case scenario, this increases input latency by half the frame time on average. So, would add an extra 16.7 milliseconds of lag at 30fps on top of the lag due to rendering the game.
And then you have to consider that games may buffer or queue frames in the pipeline to improve stability and also may not fetch inputs immediately before rendering the frame. Adding multiple frames of delay is devastating when the game is running at 30fps. With two queued frames, the latency difference between 30 and 60fps increases to 33 milliseconds and could exceed plus 40 milliseconds when factoring in display lag and other aspects of the pipeline. That's additional latency on top of whatever the base latency would be at 60fps. So, you can easily see how 30fps gaming ends up with actual latency of 80 to 100 milliseconds. Higher latency makes the game feel worse to play, inputs take longer. And with 30 FPS having around that 80 to 100 milliseconds of latency, the level of latency is high enough that most players, at least in my opinion, can feel it to some degree, even if they're not convinced that the game feels sluggish to play because of 30 FPS. I think a lot of people do subconsciously at least feel this effect.
And this is a gameplay issue. 30 FPS hurts gameplay in this way on top of reducing visual quality through increased display blur. Like with the motion blur discussion, it's a trade-off though. Rockstar clearly feel that the additional systems they've built into GTA 6 that require the game running at 30fps improve the gameplay to a greater extent than having a more responsive game running at a higher frame rate. Whether or not that's true depends on the quality of game. Of course, Rockstar are probably the only developers that integrate enough systems and complexity into their titles to get away with it. And even then, that decision won't please everyone, especially the latency purists.
So, as I've said, running a game at 30fps compared to a higher frame rate like 60fps does hurt both image quality and gameplay in some areas. It also allows the developers to improve the game and do more in other areas. So, it's a classic trade-off situation. In this console generation, it seems that most developers have felt that running at 30fps is too significant of a trade-off that isn't balanced out through better mechanics or fidelity, and so offer 60fps modes. Rockstar games think otherwise. But it's important to remember that hurting the experience through increased display blur and higher latency has allowed Rockstar to create a game that otherwise appears more next generation than other titles. This isn't purely down to just their insane development resources or optimization. It's also because of that technical decision and the trade-offs that come with it. We don't know how next generation other games would have looked or played had they also been built around 30fps as most developers didn't go down that path.
Why does GTA 6 run at 30fps? And why wasn't a 60fps mode possible? It seems to be due to a CPU limit. I want to be careful here though because I don't think it's entirely a CPU limit. I suspect the game pushes both the CPU and GPU in the consoles to their respective limits. Even if the game cut back on CPU heavy features, the graphical fidelity they've targeted would likely still limit the game to 30 FPS. To hit 40 or 60 FPS, both CPU features and graphics would need to be reduced. But the GPU heaviness is more a result of the CPU heaviness. Once you're CPU limited, it's essentially free to raise graphics settings up to the frame budget that the CPU allows. If the CPU can only throughput frames at 30fps, you may as well spend all of that 33.3 milliseconds of time per frame maxing out the GPU as well, doing super cool and impressive rendering.
The reason why you can't take a CPU limited 30fps game and easily make it run at 60fps is that CPU limits are heavily tied into the core systems and mechanics in the game. We see this a lot on PC games where there's usually not a lot of CPU scalability in the settings. How the game runs on the CPU is how the game runs no matter what. Outside of minor tweaks here and there for GTA 6 to run faster on the CPU, core elements to gameplay and the experience would have to be stripped out. Less AI, fewer NPCs, fewer mechanics, less complexity, worse object density, shorter draw distances with more pop-in, those sorts of things. In a title like GTA 6, cutting out deep systems and mechanics fundamentally alters the game. So, it's not something you can just scale from 30 to 60fps through the usual modes.
When not CPU limited, it's much easier to scale performance on the GPU side, as GPU processing is more related to visual fidelity. Running the game at lower resolutions, running individual effects at a lower resolution, turning off some visual flare and so on can all significantly improve GPU performance without altering the core systems of the game and with a much lower impact on gameplay. This is how most developers are able to offer 30 and 60fps modes on consoles. The 60fps mode just reduces the graphics without touching gameplay systems. All of the current generation consoles have effectively the same CPU, an 8 core Zen 2 design clocked around 3.5 to 3.8 GHz. The PlayStation 5 is clocked at 3.5 GHz, the Xbox Series S at 3.4 to 3.6 GHz depending on whether SMT is enabled, the Series X 3.7 to 3.8 GHz, and the PlayStation 5 Pro at 3.85 GHz.
This means there is a maximum variance in CPU performance of just 10% between the PS5 and PS5 Pro or 13% between the Series S with SMT on and PS5 Pro. That difference is small enough you may as well call them identical in their performance capabilities. An extra 10% will not overcome any major CPU bottlenecks. For example, if the CPU was being maxed out to only deliver 30fps of throughput on the PS5, you'd expect the PS5 Pro to deliver 32 to 33 FPS with its additional clock speed headroom. That's not even close to 60 FPS or even 40 FPS. So, despite the PS5 Pro including a much faster GPU, around 60% faster by all reports, that doesn't amount to much when games are CPU limited. Only in situations that are GPU limited would it be possible to have significantly different performance outputs between PS5 and PS5 Pro. But even then, as GPU performance is reasonably scalable, in most situations, it's possible to configure both consoles to the same frame rate. That's what most games do with their quality and performance modes, simply reducing settings for the PS5 version.
What does this all mean for the potential performance of GTA 6 on PC? This is where things get interesting. So, let's assume that GTA 6 absolutely smashes the CPU on the PlayStation 5, an 8 core Zen 2 design at up to 3.5 GHz. We also know the CPU features just 8MB of L3 cache, but the same 512KB of L2 cache per core as Zen 2. Memory support is of course different to desktop parts as well as the PS5 combined APU connects directly to GDDR6 over a 256-bit interface with 448 GB per second of bandwidth, much higher than you get with DDR4 to standard Zen 2 desktop CPUs. I've often seen the Ryzen 7 3700X described as the desktop CPU equivalent to the PS5, but the 3700X is actually quite a bit faster. It's clocked up to 25% higher with a 4.4 GHz boost frequency and features 32MB of L3 cache instead of 8MB, which is critical for gaming performance, at least on PC.
The closest match is an underclocked Ryzen 7 4700G or the AMD 4700S desktop bundle that is effectively the PS5 APU with cut down specs. Tom's Hardware tested the 4750G Pro version a while ago, finding that in games it was about 10% slower than the Ryzen 7 3700X. That puts it somewhere between the Ryzen 7 1800X and Ryzen 7 2700X in performance out of the known Ryzen CPUs you might be the most familiar with. In other words, the PS5 CPU is very slow by modern standards. In our testing, we found earlier this year that the Ryzen 7 5800X3D is roughly 60% faster than the Ryzen 7 3800X when CPU limited. This would make it somewhere around 80 to 90% faster than our estimated PS5 CPU performance level. And we also know that the Ryzen 7 9800X3D, so the current gaming flagship, is about 40% more powerful than the 5800X3D in CPU limited gaming. This would make it approximately 170% faster than the PS5 CPU.
So, if we assume GTA 6 is fully CPU limited on the PS5, and that's the main limiting factor in why it runs at 30 FPS, I would expect the popular Ryzen 7 5800X3D to run the game when ported to PC at just shy of 60fps. That's depending on how much CPU scalability is available in the settings and a bunch of other factors, but like for like, that is roughly what I would expect to occur. The Ryzen 7 9800X3D would therefore deliver around 80 FPS, which would make GTA 6 one of the most demanding games on the CPU that we've ever seen. Performance might be a little higher than that if the 9800X3D really flexes its muscles. It can be over 50% faster than the 5800X3D. So, it just depends on how things shake out.
At the same time, those numbers aren't outrageous when compared to some extremely CPU demanding games of late that have struggled to reach 60fps on the consoles. The Blood of Dawnwalker, for example, a title from this year, runs at just 63 FPS on the 5800X3D, according to PC Games Hardware, with extreme high-end processors required for anything above 100 FPS. GTA 6 is almost certainly even heavier than that game, given it doesn't even offer a 40 FPS configuration. In short, if you have an older gaming PC and you want to wait for GTA 6 on PC to specifically play at 60fps or higher, you might want to start thinking about a CPU upgrade. Whenever we have seen games that smash the console CPUs, these titles usually have serious CPU bottlenecks on PC as well, at least with hardware from the AM4 era.
So anyway, that's it for my thoughts on GTA 6 running at 30 FPS. The game does come out shortly. I am excited to play it despite the fact it runs at 30 FPS. I'll be firing up my PlayStation 5 and I'm sure I'll be enjoying the game like a lot of you guys will be enjoying it. But I just thought, you know, I test a lot of displays. I'm familiar with things like display persistence blur and things like that, input latency and obviously the PC hardware specs and stuff like that. So, I thought, you know what, maybe you guys can learn some things if we start talking about some of these things that aren't often talked about, especially when it comes to 30fps visual quality. I am a strong believer that the lower the frame rate is in your gaming experience on a sample and hold display, the worse the visual quality actually is. It becomes very blurry, as I said. And that's why in PC it is so enjoyable to get games running at 120fps, 240fps, and even using things like frame generation can improve blur.
Oh, and actually something I didn't even mention in this video and isn't in this script. Why didn't something like GTA 6 use frame generation to achieve 60fps? Well, frame generation has a performance overhead, so it would have dug into the performance budget for other things even further. It uses more memory, that sort of thing. So yeah, frame generation isn't always the best solution, and I've just opted for the usual 30fps thing. So anyway, that'll do it for this video. If you want to support us, as always, Hardware Unboxed is on Patreon. Links to that's in the description below. You get access to all the usual benefits: Discord community, monthly live streams, BTS content, plenty of good stuff. So, thanks for watching. Go enjoy GTA 6 at least in a few hours if you're in Australia. Check out the reviews. I think they're dropping soon as well. Anyway, that'll do it. Thanks for watching. We'll see you in the next one.