Rocket League

Hilariously simple pick-up-and-play games are great fun. I'm a massive fan of the Katamari franchise for that reason — passing start on a controller and rolling around, picking up things to get bigger, is extremely simple. Until we get a PC version of Katamari that I can benchmark, we'll focus on Rocket League.

Rocket League combines the elements of pick-up-and-play, allowing users to jump into a game with other people (or bots) to play football with cars with zero rules. The title is built on Unreal Engine 3, which is somewhat old at this point, but it allows users to run the game on super-low-end systems while still taxing the big ones. Since the release in 2015, it has sold over 5 million copies and seems to be a fixture at LANs and game shows. Users who train get very serious, playing in teams and leagues with very few settings to configure, and everyone is on the same level. Rocket League is quickly becoming one of the favored titles for e-sports tournaments, especially when e-sports contests can be viewed directly from the game interface.

Based on these factors, plus the fact that it is an extremely fun title to load and play, we set out to find the best way to benchmark it. Unfortunately for the most part automatic benchmark modes for games are few and far between. Partly because of this, but also on the basis that it is built on the Unreal 3 engine, Rocket League does not have a benchmark mode. In this case, we have to develop a consistent run and record the frame rate.

Read our initial analysis on our Rocket League benchmark on low-end graphics here.

With Rocket League, there is no benchmark mode, so we have to perform a series of automated actions, similar to a racing game having a fixed number of laps. We take the following approach: Using Fraps to record the time taken to show each frame (and the overall frame rates), we use an automation tool to set up a consistent no-bot match on easy, with the system applying a series of inputs throughout the run, such as switching camera angles and driving around.

It turns out that this method is nicely indicative of a real match, driving up walls, boosting and even putting in the odd assist, save and/or goal, as weird as that sounds for an automated set of commands. To maintain consistency, the commands we apply are not random but time-fixed, and we also keep the map the same (Aquadome, known to be a tough map for GPUs due to water/transparency) and the car customization constant. We start recording just after a match starts, and record for 4 minutes of game time (think 5 laps of a DIRT: Rally benchmark), with average frame rates, 99th percentile and frame times all provided.

The graphics settings for Rocket League come in four broad, generic settings: Low, Medium, High and High FXAA. There are advanced settings in place for shadows and details; however, for these tests, we keep to the generic settings. For both 1920x1080 and 4K resolutions, we test at the High preset with an unlimited frame cap.

All of our benchmark results can also be found in our benchmark engine, Bench.

MSI GTX 1080 Gaming 8G Performance


1080p

4K

Gaming Performance: Rise of the Tomb Raider Gaming Performance: Grand Theft Auto V
Comments Locked

545 Comments

View All Comments

  • RafaelHerschel - Thursday, April 19, 2018 - link

    Hardware unboxed certainly did. It's a bit odd that you automatically assume that only Anandtech knows how to test.
  • aliquis - Thursday, April 19, 2018 - link

    If they don't rerun the tests with up to date software then they are useless.

    What I assume has happened here is some software, driver or firmware being "off" in the Anandtech review somehow.
  • RafaelHerschel - Thursday, April 19, 2018 - link

    @Ryan Smith That is an excellent response.
  • krumme - Thursday, April 19, 2018 - link

    AT run bm at Jdec specs. 2666 for 8700k 2933 for 2700x. That and the security patches.
  • Hifihedgehog - Thursday, April 19, 2018 - link

    I was also totally misled. I came here first, only to find out after having misleading people online that this site’s results are completely off. I am a big AMD fan but these results need to be audited and corrected.
  • Ryan Smith - Thursday, April 19, 2018 - link

    "these results need to be audited and corrected."

    Validating right now.=)
  • stefanve - Thursday, April 19, 2018 - link

    Clearly someone didn't apply his meltdown patch ....
  • casperes1996 - Thursday, April 19, 2018 - link

    Advice for the future:

    Don't be a prick.
    Ian isn't lying to you. He's sharing the data his benchmarking showed. It being different to other reviewers is something he'll gladly look into, and is in fact looking into, but you ought to show yourself as a respectful individual when you point it out, otherwise you won't be listened to.
  • MadManMark - Thursday, April 19, 2018 - link

    Hear, hear!
  • bfoster68 - Thursday, April 19, 2018 - link

    Chris113q,

    I did one for you since you seemed to be having issues.
    If you read below they use a different methodology for estimating fps vs what AnandTech did in their review. the result is nearly the same. solid gains for AMD on a incremental upgrade. Was that so hard?

    https://www.tomshardware.com/reviews/amd-ryzen-7-2...

Log in

Don't have an account? Sign up now