PuppetMaster
Member
I just love that Ryan is still getting shit about this sound bite!
to be fair to polygon (cant believe im saying this) the reviewer can only comment on the performance they experience, it doesnt matter if in this case the ps4 is "too good". If the game judders it judders and that is no bueno.
Instead of spending $600 for your PC just lower graphical effect settings.
So the rumors where true porting cod took like 3 weeks and running at 90 fps or something like that?
Why are people shocked? Every game that is aimed at 60hz, is running over 60hz most of the time.
Forza probably runs at 100fps many times, like many CoD on Xbox 360, Wipeout on PS3 or GT 5/6.
The difference is, that they are locked at 60, but frames are rendered faster than in 16.6ms
Why are people shocked? Every game that is aimed at 60hz, is running over 60hz most of the time.
Forza probably runs at 100fps many times, like many CoD on Xbox 360, Wipeout on PS3 or GT 5/6.
The difference is, that they are locked at 60, but frames are rendered faster than in 16.6ms
Why are people shocked? Every game that is aimed at 60hz, is running over 60hz most of the time.
Forza probably runs at 100fps many times, like many CoD on Xbox 360, Wipeout on PS3 or GT 5/6.
The difference is, that they are locked at 60, but frames are rendered faster than in 16.6ms
So polygon gives the PS4 version a lower score because it has a higher framerate? That's hilarious
But isn't IW at fault for this, not the PS4?
So why the hell didnt they vsync lock it at 60?
Polygon: PS4 COD runs 1080p at over 60 fps: 0.5 points lower.
How could that not have been fixed yet?
[settings]
MaxFramerate = 60
done.
But isn't IW at fault for this, not the PS4?
I really hope they change it, if not people will go nuts.
Expecting a Polygon article on how this proves lower frame rate and resolution is best.
Oh and lol@IW , how the fuck does this make it through QA when something as simple as vsync could have made it a non issue
Yes, it's their fault, and Gies and all the rest who wanted to use a lower framerate in CoD on PS4 to dismiss its power advantage will have to go find another straw to grasp at.
There's some seriously interesting (and admittedly expected) technological implications for this, but I don't like that people are acting as though the frame-rate issues (in terms of judder from inconsistent rates) are a good thing in terms of user experience. This is a bug that should have been addressed. It could be that this sort of oversight applies to the problems in other versions as well.
If your energies are focused on the credibility of a hardware platform, then this is good news. If you care about the gameplay experience, then this is still a bad thing until it's patched (which should thankfully be within days rather than weeks, based on the nature of the problem).
To me it sounds like IW was more focused on optimizing the xbone version for launch to notice this hiccup.
Something is off here...you shouldn't be able to run at a framerate higher than 60fps with vsync enabled...it doesn't swap the frame into the buffer until a monitor poll. That being said, a single torn frame means there's something weird going on here.
In any case, the issue here appears to be an uneven frame latency, not a framerate issue.
Something is off here...you shouldn't be able to run at a framerate higher than 60fps with vsync enabled...it doesn't swap the frame into the buffer until a monitor poll. That being said, a single torn frame means there's something weird going on here.
https://twitter.com/shahidkamal/status/400013318309814273
Wrong!! Shaking my head Shahid, get your shit together!
No, they shouldn't change anything based on this news. I've been playing the PS4 version, and I definitely think the game doesn't run at smoothly as it should. This doesn't change that fact. All that's different now is the explanation for why it's not as smooth as it should be.
It's probably not quite as simple as just enabling vsync, and for the record the game rarely tears frames in multiplayer. In fact, I believe I've only see it happen on one specific map, and one specific area of that map. Haven't touch the campaign yet.
Vsync is NOT enabled. I have seen tearing, albeit extremely rarely, but it does happen on a specific map in a specific area of that map.
OK, so if we have a 240hz TV, what would be wicked awesome, would be to have the option to optimize the FPS for your own TV for SP. I know that would be a logistical nightmare for online play and would create clear unbalanced gameplay.
So the solution would be to limit the maximum amount of frames per second? lol
Wait so it's not fair to post this when a game fails to meet those because indies but it's fair to post this when a AAA game meets those?
I'm confused.
I wonder at what point did MS realize they were beat in the hardware spec dept?
Shahid's gonna get misquoted for the rest of the gen isn't he?https://twitter.com/shahidkamal/status/400013318309814273
Wrong!! Shaking my head Shahid, get your shit together!
It SHOULD be as simple as enabling vsync. And if they do, they do need to change their review. It would be hypocritical if they did not.
It SHOULD be as simple as enabling vsync. And if they do, they do need to change their review. It would be hypocritical if they did not.
That's actually a major part of how display functions like v-sync work. If a game appears to be running tear-free at a framerate like 30 or 60, it's not that the hardware is only capable of running that many frames. It has a greater "budget" of processing power, but it's limited to solve problems like the exact one we're seeing in this version of CoD.
Nofunalloved.jpg![]()
I've seen this gif thousands of times but I still don't know who it is, could someone end my suffering please. It cracks me up every time.![]()
This just keeps getting better and better. Oh lawd!
I've seen this gif thousands of times but I still don't know who it is, could someone end my suffering please. It cracks me up every time.