It’s hard to explain, so I’ve captured this video of the issue: You see, Warfighter has a very particular issue that is found in very rare cases of terrible coding when aiming, the crosshair jumps from blocks of pixels to the next, rather than smoothly panning across the screen. It looks and sounds great, but aiming itself can only be described as horrific. Feedback from firing is helped no end by the destructible environments delivered by the Frostbite 2.0 engine, though not quite to the same level of Battlefield 3. I’m totally fine with that though, as that’s what gamers have been groomed to expect. Sound effects are inspired by the Hollywood weapons range, with the realistic cap-gun pops and cracks of a real-life weapon replaced by booming Howitzer explosions for even the smallest 9mm handgun. Warfighter gets a few things right, and one thing spectacularly wrong. The most concerning is the act of firing the weapons, the most fundamental element of any decent shooter. This is why Warfighter is so baffling – rather than learn from the mistakes of the last game, the latest entry makes an entirely new bunch of SNAFUs that we’d expect from an FNG rather than a combat veteran. After all, based on the many sequels I’ve played over the years, it’s become pretty standard to expect the follow-up to improve on the last game in every way.
With that in mind I had relatively high hopes for Warfighter. Most gamers like a bit of dumb fun that doesn’t require Mensa-levels of intellect to penetrate, and I was one of the few critics who found the last MoH a decent first-person romp. Walk into any real-life carnival or fairground and you’ll see the most popular attractions are the rollercoaster and shooting gallery, and I think a lot of us find the same enjoyment in blockbusters like Call of Duty or Battlefield. If it’s not being used for a sandbox experiment in emergent gameplay, as seen most recently in Dishonored, the first-person perspective found in rollercoaster shooting galleries is deemed unworthy of gamer attention. Continued abuse of our services will cause your IP address to be blocked indefinitely.Over the last couple of years it’s become rather trendy for gaming critics to slag off linear first-person shooters. Please fill out the CAPTCHA below and then click the button to indicate that you agree to these terms. If you wish to be unblocked, you must agree that you will take immediate steps to rectify this issue. If you do not understand what is causing this behavior, please contact us here.
If you promise to stop (by clicking the Agree button below), we'll unblock your connection for now, but we will immediately re-block it if we detect additional bad behavior. Overusing our search engine with a very large number of searches in a very short amount of time.Using a badly configured (or badly written) browser add-on for blocking content.Running a "scraper" or "downloader" program that either does not identify itself or uses fake headers to elude detection.Using a script or add-on that scans GameFAQs for box and screen images (such as an emulator front-end), while overloading our search engine.There is no official GameFAQs app, and we do not support nor have any contact with the makers of these unofficial apps. Continued use of these apps may cause your IP to be blocked indefinitely. This triggers our anti-spambot measures, which are designed to stop automated systems from flooding the site with traffic. Some unofficial phone apps appear to be using GameFAQs as a back-end, but they do not behave like a real web browser does.Using GameFAQs regularly with these browsers can cause temporary and even permanent IP blocks due to these additional requests. If you are using Maxthon or Brave as a browser, or have installed the Ghostery add-on, you should know that these programs send extra traffic to our servers for every page on the site that you browse.The most common causes of this issue are: Your IP address has been temporarily blocked due to a large number of HTTP requests.