News - Cheating The Cod Warzone 2 Benchmark Is Insanely Easy
This will officially be my 100th article on the channel, plus or minus the two articles that I removed or unlisted for various reasons, but it is a fun topic nonetheless, so I've recently been told by some people on Discord that indeed it is extremely easy to cheat the Modern Warfare 3 benchmark. Yes, the Call of Duty Modern Warfare 3 benchmark is actually broken, and it's really easy to get fake CPU results on it.
The GPU results are not really that bad due to the consistency of the GPU throughout the entire benchmark, but the CPU results are extremely fake. What you're looking at right here is a legitimate result with no cheating involved, where I scored a 673 average with 41%, lows with a 405, average with a resizable bar disabled in Call of Duty.
Now why am I showing you this first screenshot? This screenshot was taken a couple days ago, or like two days ago or something like that, where I did a legitimate test, and only today have I found out that you can cheat. Now you may be asking how you can cheat. The benchmark, sadly, is extremely easy.
I'm going to try to explain it as well as possible, but first let me show you my settings just so you know what settings I'm using for the results that I'm getting, and it's my usual config file settings that are blatantly low settings, fully optimized for maximum fps to sum it up at 1440p. Native, now the way we're going to cheat is simple: we're going to start the benchmark, and we're going to basically leave zone two.
I'm going to give a couple more details on why zone two exists, but let me quickly show you the sort of gains you can get by simply leaving the benchmark early, which I know sounds completely absurd, but all you have to do is hit Escape. Confirm, and that ends the benchmark instantly. And what will generally happen is that it's going to give the FPS that it got up until that point on the CPU.
On the GPU, it'll do the same, but because it's so much more consistent on the GPU, it won't really affect the results much, but on the CPU, it'll be absolutely massive gains. Now, right at the end of Zone 2, right here, we are going to basically leave, and right here we confirm, and now we wait for the benchmark to show our results.
And as you'll see, yes, this is also my first try, by the way, so I'm hoping it's going to be as good as I think it is, but there you go. I gained over 50 FPS in the averages. 30 FPS in the 1% lows, and what did I do? I just left the benchmark early. Nothing else looks out of the ordinary; you could not tell at a glance that I cheated.
Here's the thing: look over here in the middle, where it says overview. There's also a zone details page you're going to want to click on, and this brings up a whole different page that basically shows the specific zone FPS. As you may notice. Zone 2 gets a stupendously high FPS amount in the averages for the CPU specifically, which means that you basically want to just avoid the other zones and use Zone 2 as the one where you leave theoretically, and that's why we don't use Zone 4 and 5 for the testing and we leave early because the results are significantly better on the CPU.
This way, people basically just do this and show you the overview, and boom, Shakalaka, look how good my FPS is now, theoretically. This is very sad. You can cheat on this page too, because Call of Duty is so stupid. If you first run a normal benchmark and complete it all the way through, it's going to show all of your zones FPS.
If you run the benchmark again and quit Zone 2, it is going to show you on the overview that you got the average FPS of the Zone 2 run. But then you go to the zone details, and it remembers Zone 3, 4, and 5 FPS, meaning that people can fully fake both the Zone Details page and the overview page within the Modern Warfare 3 benchmark.
I just ran a test, which, by the way, happens to be my best 1% low test yet, but that doesn't even really matter, so this is a full-run legitimate test. If you go to Zone Details, you can see that it completed every zone, and these are different numbers than last time, so I finished all five zones with a full test.
This is a legitimate benchmark. Now watch this, so I'm going to click Start, and I'm going to start another benchmark. So what I'm going to do now is, as zone two ends, I'm going to leave. The usual exploit that we do is confirm and leave. Now we wait for this again, and I'm going to quickly show you how gullible the zone details are too, so there's no good way about this.
Basically, look how good my results are! Yet again, we go to the zone details. And yes, you guessed it because we did the initial run fully. It still shows Zone 3, Zone 4, and Zone 5 from the previous run, but then Zone 2 is the final result difference. Zones one and two are the final results. So it just completely disregards Zones 4 and 5, which are still showing in the zone details, but uses Zones One and Two from the run we just did as the average FPS.
This benchmark is heavily scuffed. Like so scuffed if you guys really want a good comparison for something, jump into Almaza. Start up the 1% lows and begin testing. It is the best way to actually test a real-life scenario that is hard to cheat, because what is harder to cheat than virtually anything in CPU-bound scenarios in an actual gaming scenario?
Basically, the benchmark is fake, but in-game results are much harder to fake because DLSS isn't going to help you if you're CPU-bound. So, yeah, I don't know what to tell you guys. I just want to let you know that the benchmark is kind of scuffed, and I wouldn't really pay attention to the benchmark because, as you've seen, people can do whatever they want to get a higher FPS, and there's no way to hold them accountable.
But yeah, the entire point of the article was to bring awareness to the fact that the benchmark isn't particularly trustworthy due to how easy it is to cheat. Of course, if you're showing the benchmark to people you trust, it's perfectly fine, but if it's coming from a stranger and it looks too good to be true, definitely question them about it, ask for proof, and ask for a way to show that it is legit because, look, some people will see these fake benchmarks and set unrealistic expectations of their system not only that when they're inevitably unable to reach that exact performance that the cheater use to reach those stupidly High CPU FPS numbers they're going to feel bad about their system and they're not going to like their system anymore cuz apparently they're doing something wrong when they're not and look for those sad pieces out there that are actually actively cheating.
