11/11/2022 0 Comments Quantum break pc port![]() ![]() Relying on pure instinct, I press buttons that I know will guide me to the right side of the room and, lo and behold, after the stuttering is finished, I’ve successfully evaded his attack straight from muscle memory. The room goes red and my framerate starts to tank, but I’m not worried. After one more bad-ass time-dash into an enemy and one satisfying punch later, I was ready for the big boss’s screen-shattering attack. I blast the first teleporting enemy with a time bomb, freezing him in place as I dash my way over to bad guy number two, punching him straight to hell before warping backwards and slowing time to a crawl, firing off a series of shots at the frozen dude and a third scrub right next to him. The big boss sends his goons but no amount of AI baddies in the world can stop me at this point. I blast through the intro cutscene, making quick work of the bad guys that stood between me and the arrival of the final boss. So I booted up the game and delved into the abyss of Windows 10 gaming once more. Very, very frustrating, after having waded through a murky six hours of the ugliest, most poorly optimized game I’d ever played, during round two of an unimpressive boss fight. Thanks to UWP (Universal Windows Platform), my game decided that alt-tabbing meant I was done playing and TURNED OFF THE PROGRAM MID-PAUSE. The second time I lost the fight was because I paused the game, alt-tabbed to see if anyone else had gotten texture-caught during the fight. Round two is where the tech errors really began cropping up. That was simply the game’s cluttered design at work, nothing technical… yet. The first time I lost the boss fight was because my character’s foot got caught in a web of suspended scaffolding, a simple obstacle hit-box error on the part of the designers who created the map. ![]() See, the final boss uses screen-cluttering effects the size and scope of which the game hadn’t had to render in real-time prior, meaning my rig was unprepared for a fresh new wave of paralyzing code to strike. No amount of stutters, framerate drops or freezes could stop me. I’d made it to the final battle, the big ol’ boss fight at the bitter end. Strap in, ladies and gents, it’s story time. Against all odds, it somehow found a way to get even worse. Even at the lowest settings with a GTX960 and 8GB of RAM, I was suffering memory leaks and a framerate that could barely cling to a consistent bar of just below 30. After about thirty minutes of any given gameplay session, memory leaking would begin. So no funny business should be happening in that department, right? Wrong. Now, I’ve got 8GB of RAM, the acceptable bar for this title. Yet here I was, just thankful to be able to play the game in some fashion even though it looked like a first-wave Xbox 360 title. Keep in mind my rig’s above the minimum specs a GTX 960 shouldn’t be chugging because of this shit. As such, this experimentation went on for a good hour until I did the unthinkable: I lowered every setting to its lowest possible level, and only then did the game become (barely) playable (25-ish frames consistently). These elements were helping, but nowhere near enough to make the gameplay, well, playable. Turning off the framerate cap? A more steady framerate. Turning textures from medium to ultra? Less stuttering. During this tech-support mission I discovered that the most random changes would boost my framerate for a few brief, blissful seconds. So after a minute of the choppiest, most broken third-person action I’d ever experienced, I paused and began tinkering with settings. Boatloads of stuttering and framerate drops began during the very first instance of interactive gameplay, an indicator that I was in for a bad time. The issues started early on, in an unprecedentedly severe fashion. I know the developers issued a big update to remedy (unintentional developer pun) some of the original port problems, but the game must’ve been unable to load fucking menus at that point if this is how bad it is post-“fix.” Make no mistake, this is by far the worst port I’ve ever encountered. Quantum Break should be re-titled Hardware Break on PC, as it’s a mess. Across years of PC gaming, I’ve stumbled upon a few bad ports, sure. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |