>>715613824 (OP)
this happens with every single console release
and every time before the release console peasants are like >this time it's gonna run shit at 60fps
>>715616454
That shit was so bad that I only bothered to finish the game once I hacked my PS4 and downloaded the 60FPS mod. And even then I regret not just waiting for emulation because FUCK those load times
Won't make the same mistake with DK, enjoy beta testing tendies
>>715616454 >B-but sony
the difference being everyone agrees that bloodborne performance is shit. Unlike with the toddlers that will always defend every terrible decision from their corpo daddy.
>>715613824 (OP)
This was the first game in a while that I was interested in buying on release but the performance has soured me on it. At this point I'm thinking I'll wait to see if it gets patched soon.
>AIIIEEEEE MY GAME DROPPED CROM 60 TO 30 FOR .564 SECONDS. SAVE ME MARK CERNY
I’d love to have the game at a locked 60 but this all seems like a nothingburger to me
Nintendo has this weird infatuation with triple buffer vsync. Their games go from 60 to 30 at the slightest drop. This makes sense if your game has the framerate all over the place, but I wouldn't be surprised if this game drops to 50 at most under normal circumstances and 40 in extreme situations for half a second. It makes no sense why they go with that shit.
>>715619372
I think VRR only works on handheld, and for some reason the game runs the screen at 60hz so VRR doesn't work correctly. I can only imagine this game was finished long ago, before the hardware was ready.
