Surprise, this isn’t a graphical bug! It’s an inflatable decoy, and its name is Jim. It’s probable that this specific issue will be fixed prior to launch with a GPU driver update, but it’s also possible that it won’t, and someone has to be able to say I told you so if the latter is the case. I’m not alone, and judging by the amount of threads on the title’s Steam page about the beta’s technical performance, there’s also a lot of issues with screen flickering/tearing. Although it does look good, and there’s a lot of cool new animations that are undoubtedly sucking up GPU bandwidth, I found it difficult to get a stable 60FPS on my computer that’s been able to run every CoD game in history at a solid 100FPS. The biggest one is, for some reason, that the title just doesn’t seem to run very well on PC. However, Call of Duty: Modern Warfare II’s beta wouldn’t be a Call of Duty beta if there weren’t a couple of minor problems to passively offset the good of its core gameplay and new gimmicks. Much like in the previous Infinity War-developed fish simulator, which included gems like Realism and night maps, these new additions were how I spent the bulk of the past 72 hours and will hopefully be how I procrastinate figuring my life out come October. In addition to the standard slew of modes that every Call of Duty game has, the beta included a few genuinely unique war crime simulations including “Invasion”, a Battlefield-esque mode with AI, players and vehicles, and a third-person playlist for TDM/Domination/Hardpoint. That’s also true because the gimmicky game modes in the beta were, again unlike in Vanguard or Black Ops: Cold War, a ton of fun. In hindsight, taking cover behind a box of chickpeas wasn’t the best idea…
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |