can I get a biased summary?
@drlostrib: Contains all PS4 Pro enhancements, with more shadow detail, running between 1800-2160p, at a perfectly locked 30-fps (indicating GPU overhead availability, clearly unused)
can I get a biased summary?
I would but you know how lems hate that.
@drlostrib: Contains all PS4 Pro enhancements, with more shadow detail, running between 1800-2160p, at a perfectly locked 30-fps (indicating GPU overhead availability, clearly unused)
I wonder if we might see another patch?
Also the Pro is getting another patch which makes me wonder why these games keep getting patches after being out for so long.
I think I'm going to use the 4k option for my next play-through... just looks so nice. And the framerate is more stable.
But overall, seems like CDPR did a good job. X is the superior version, as it should be.
@kuu2: Sharp observation. Seems like pure optimization for the X is mostly only done right by first party developers for the X.
@Pedro: df running stock 970, he also mentioned he lowered shadows and hairworks off, so not exactly far fetched
Hairworks is off in the video and they are using a stronger CPU for a game that is CPU bound in many locations.
CPU bound on high fps yes, my old 2600k would be a bottleneck with my old 980ti on 1080p, not at 1440p. I have no doubt 3570k is enough to keep 60fps
You can check this for reference: http://www.eurogamer.net/articles/digitalfoundry-2016-is-it-finally-time-to-upgrade-your-core-i5-2500k
2500k with stock clock and 1600mhz ram dips slightly below 60fps in few occasions in the novigrad stress test
They are using a Titan X in the link you provided not a 970. The original poster said he was getting 60FPS flawlessly with the specs listed. I find that claim highly unlikely.
I should clarify that the CPU and GPU were heavily overclocked (4.6 Ghz, +230 core, +550 mem) and I think foliage might have been down a setting too. Either way, it ran very well on modest hardware with just a few minor compromises made for a solid 60FPS.
Please Log In to post.
Log in to comment