How much RAM are you folks using for RDR2? I see it recommends 32 GB for the high end, but I'm guessing most of us "only" have 16 GB.
16GB ram + a 1070 with 8GB, neither comes really close to being used to the max. The CPU (i5 7500) frequently jumps to 100% with stutters and freezes.How much RAM are you folks using for RDR2? I see it recommends 32 GB for the high end, but I'm guessing most of us "only" have 16 GB.
No, it's not. It's just really badly optimized.So RDR2 is CPU bound? Huh...
While GN did mention the issue, I think the cap was said to be around 150 fps, way beyond of what you would aim for with the graphics settings.No, it's not. It's just really badly optimized.
Watch Gamers Nexus' or Hardware Unboxed's videos about CPUs in RDR2.
What happens is that the game throws a 100% load on the CPU to a point where it hits the Engine FPS cap (I think it's something like 128FPS or so - yes, it's not the most well-written engine in the world) when it hits the cap, it simply stops and throttles the CPU to 0%, hence the stutter. Then it repeats the process. It only does that with certain CPUs.
The workaround is to max out the graphics beyond the point you'd normally do for your particular GPU and bind the game by GPU really hard and it kind of stops doing that.
It's also the reason why the game runs (seemingly) better on mid tier GPUs than on high-end.
Though this workaround doesn't always work - the engine FPS are not the rendered FPS, it's the FPS CPU sends to GPU to render.
IMO they're going to have to work on this. Owners of 2080Tis will probably not be happy with running the game (however graphically good it looks) at 60-70FPS with stutter dips to 20 (and with some CPUs downright freezes to 0FPS)
TL/DR It's a crap port. Wait with the purchase.
Again - Engine FPS is not the same FPS you see on the monitor. The CPU renders hundreds of frames and sends them to the GPU, which then renders as many of them as it can at as regular intervals as it can. Usually these two components talk to each other and optimize the frames, but RDR2 engine doesn't do that. Instead, when it hits its artificial cap it simply stops rendering frames and waits for "something" to start rendering again.While GN did mention the issue, I think the cap was said to be around 150 fps, way beyond of what you would aim for with the graphics settings.
However, CPUs with 6 or fewer threads do suffer from brutal stutters, like freezing for seconds.
Thank goodness I never had any of that...frustrating to say the least. All I did was allow an exception in my firewall settings. The game runs in either Vulkan or DX12 with no perceptible difference between the two.
It may be a heresy, using adblocker + staying on the light web (no torrents, pirating, etc.) keeps me safe enough. Never had any issues, and by the way I don't store sensitive info on my rig.I was just about the say that - if any program tries to convince you to turn the antivirus off, I'd be very suspicious.