Announcement

Collapse
No announcement yet.

Performance Analysis: Borderlands: The Handsome Collection revisited

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Performance Analysis: Borderlands: The Handsome Collection revisited

    The idea behind Borderlands: The Handsome Collection was enticing: billed as the definitive console editions of Borderlands 2 and The Pre-Sequel, the remaster promised full HD visuals and a smooth 60fps update on both PS4 and Xbox One. Unfortunately, the launch code felt distinctly uneven and lacking in polish, with a wildly variable frame-rate and intrusive screen-tear. Last week, Gearbox Software released patch 1.02 to tackle these performance issues in addition to squashing a number of bugs. Weighing in at around 9GB on both consoles (around 7GB for The Pre-Sequel and 2GB for Borderlands 2 on Xbox One), the update is remarkable, a genuine game-changer. The developer has finally handed in something closely resembling the experience we were hoping for - 1080p60 gameplay on both PS4 and Xbox One.
    An initial look at the PS4 patch reveals substantial upgrades in performance, with demanding scenes operating at far higher frame-rates than the day one code. An early gunfight in a large control room initially suffered from regular bouts of screen-tear and heavy frame-rate drops, creating judder and highly variable controller response. By comparison, after the latest 1.02 patch is installed, frame-rates stick closely to the desired 60fps refresh with only a few minor dips in smoothness that manifest as occasional brief pauses, which are short and rare enough not to cause offence.
    The same level of optimisation is found in throughout the game: small fire-fights play out without a a hitch, while locations sporting long draw distances mostly retain the target 60fps - something that definitely wasn't the case previously. Tearing remains present but far, far less of an issue than it was previously, with only a few odd torn frames sneaking in when the engine can't quite hit its target 16ms frame-time.
    Read more…


    More...
Working...
X