Batman: Arkham Knight

Today, we’re looking at Batman: Arkham Knight on the PS4 and Potato Masher!

Normally, I’d be showing comparison footage of the PS4 and PC versions of the game, and talking about the relative strengths and weaknesses of each platform and how they do. But, this video will be a little abnormal. Arkham Knight was a huge disappointment when it originally released on the PC earlier this year. There were so many technical errors that the game was almost unplayable for most people. The PC port was rushed and clearly unfinished, so much so that the game was removed from stores for several months so it could be fixed. Well, the fixed version is out now, and it is unfortunately still quite broken. Most prevalent is a memory leak that causes stutters and crashes for computers with average or low amounts of system memory. Of course, the Potato Masher falls into this category. It has 4GB of RAM, which has been fine for almost every game we’ve tested. The only games that haven’t worked are Battlefield 4, which also had a bad memory leak, Arkham Knight, and one more game that you will see very soon. So, how does Arkham Knight run? Well, up until now in the video, you’ve been watching PS4 footage. Anyone who has been following the sad story of Arkham Knight on the PC won’t be surprised, but the game flat-out does not work on the Potato Masher. It stutters and freezes so poorly that it’s like watching a slideshow. I didn’t want to just give up there though. Like I mentioned earlier, the Potato Masher doesn’t mean the minimum RAM requirements for the game, so I can’t really blame it if it doesn’t run, right? Well, not exactly. The minimum requirement is 6 gigs. I threw another 4 gigs of memory into the Potato Masher and started the game again. For some reason, I couldn’t get the performance overlay to pop up again, so I’ll just tab out so you can see that it does indeed have 8GB of RAM. The game worked fine for a few minutes, but then the stuttering started again. It was definitely not nearly as bad as before, but the game doesn’t work with 2GB more RAM than the minimum requirement. Just to make sure that the RAM was the only problem, I added another 8GB, so the Potato Masher was running with 16GB. The game worked much better! On low, maintaining 30fps at 1080p was very easy on the Potato Masher. I didn’t do extensive graphics testing, but Very High caused quite a few dips below 30, so Medium or High is probably where the best experience can be had. That’s still a little disappointing, but the game did actually work. Low seemed to be close or a little worse than the PS4 version, so I assume that if the game wasn’t broken, the two versions would be pretty close. The memory usage barely went above 8GB, so it’s possible that 8GB of RAM might work for some people, or with some modification to the game’s .ini file. I have strong doubts that 6GB would work for anybody.

So what can we learn from all of this? I have every confidence that if the memory leaks were fixed, the Potato Masher is powerful enough to play the game very well. Since that’s not the case right now and WB doesn’t seem to have any plans to finish the game, I can’t test it further. Obviously, if you want to play the game and you don’t have 16GB of RAM, get the PS4 version. It runs great and the game is well worth playing. I’d probably get the PS4 version no matter what, to help send the message to developers that terrible PC ports are unacceptable and not worth paying for.

I know this video is different from normal, but the Potato Masher is an experiment, and I think it’s important to highlight when it isn’t capable of playing a game properly. In this case, the game is the issue, not the computer, but to the consumer, all that means is that they can’t play it. There are a few more special videos coming out in the next few days that will go into more detail on this, but for now, thanks for watching and have a great day!