Overkill Intends to Take Full Advantage of the PS4 for PayDay 2 Crimewave Edition

Console parity has been a controversial topic since the release of the PlayStation 4 and Xbox One. Many developers have been scrutinized for not taking full advantage of Sony’s console, but PayDay 2 Crimewave Edition developer Overkill Software has said that if it can squeeze more out of the PS4, it’ll go for it. 

In an interview with Videogamer, producer Almir Listo said that if PayDay 2 can be made slightly better on the PS4, there’s no reason Overkill wouldn’t do that.

They [PS4 and Xbox One] are both going to be… I don’t know if I’m able to say ‘identical’, but basically we’re going to cram in as much as we can. It would be unfair of me to say that they’re going to be identical, because if hypothetically speaking we can make the PS4 make better stuff than the Xbox One does, then why wouldn’t we do that? If we can take it up a notch, improve the frame rate a bit or whatever, why wouldn’t we do that?

In the same interview, Listo also said that while PayDay 2 will be 1080p on both consoles, it probably won’t be 60fps. Overkill wants to achieve at least at least 35/40fps. 

We’re pushing it as high as we possibly can. Say hypothetically Payday 2 was 30fps roughly – between 25fps and 30fps on [Xbox 360 and PS3] – then I would say at least 35/40fps [on PS4 and Xbox One]. But I would rather have our community be surprised by the improved fps than disappointed by us saying, ‘Yeah, it’s going to be 65fps’.

Listo further said that technically, the developer could shoot for 60fps, but that would result in some changes that PayDay 2 isn’t about. For instance, aiming for 60fps might mean that the game “could only show four enemies at a time on-screen.”

It’s still refreshing to note that Overkill wants to make the most out of the PS4, no?

[Source: Videogamer(1)(2)]

TRENDING
PlayStationLifeStyle.net is currently undergoing server maintenance. The GamingLifeStyle forums are closed and will return under the PlayStationLifeStyle banner.  Please bear…
Exit mobile version