The Framerate Analysis Thread part 2

Would PS360's software measure a higher than 60 framerate? In other words can we rule out hotcooler's scenario for this game?
 
Rangers No way to measure above 60fps, and that's not software problem. Consoles does no support more than 60hz output. You can confirm or deny if it's more that 60fps by looking frame by frame (do the next frame have a part of previous one or not)
 
Thanks pretty impressive the engine never dips below 30fps

Its much better than that. I only noticed the 360 version ever drop frames (and only a couple at that) during gameplay when enabling the "climax" move, which slows everything down anyway and only happens very rarely anyway. Its pretty much a perfect 60fps in gameplay really.
 
Its much better than that. I only noticed the 360 version ever drop frames (and only a couple at that) during gameplay when enabling the "climax" move, which slows everything down anyway and only happens very rarely anyway. Its pretty much a perfect 60fps in gameplay really.

he is talking about GOW3.............
 
I looked at Skate. From what I can see it's 60fps with 100% tearing in the top few lines. Basically soft v-sync, with the game probably running *slightly* faster than 60fps internally. Very curious!

I can only imagine that the set-up confused ps360's tool because you can look at the game frame-by-frame and see the tearing, and that it's on every frame. There's a bug on Blackmagic Intensity which makes analysis of the top-line "difficult" but I'm seeing the same on my hardware which bears no relation to the Intensity whatsoever.

As the tearing would only be seen in the overscan area, I would basically say that it is irrelevant to the overall gameplay experience, similar to Just Cause 2.
 
As the tearing would only be seen in the overscan area, I would basically say that it is irrelevant to the overall gameplay experience, similar to Just Cause 2.

I think you meant to say another game and not Just Cause 2, since I would say this is pretty relevant to the overall gaming experience:
screenshot20100429at125.png
 
Last edited by a moderator:
Didn't Digitalfoundry article once mentioned that all the tearing in BFBC2 PS3 happened in the overscan area ? If so then I don't think it was entirely true cause I do see tearing happening in the top half of the screen quite often.
 
The article didn't say it was all in the overscan area...

http://www.eurogamer.net/articles/digitalfoundry-faceoff-battlefield-bad-company-2?page=2

Where things are more of an issue is in the level of screen-tear, and it's here that rolling out statistics such as percentage of torn frames doesn't really work. It seems to be the case that DICE has invoked some kind of soft v-sync on PS3. Every other frame is torn, but the tear is mostly in the first few lines of the framebuffer up at the top of the screen, virtually unnoticeable.

Bad Company 2 isn't the first game to do this (WipEout HD, Uncharted: Drake's Fortune, and a bunch of Unreal Engine games including DICE's own Mirror's Edge do the same), and it's not going to be the last. Our solution? Disregard the first five lines from the scan. By doing this, we get a result that seems more in line with the gameplay experience: Xbox 360 comes in at nine per cent torn frames, PS3 closer to 16 per cent. In short, while performance is equivalent most of the time, when the engine is really under stress, it's the PS3 version that has more noticeable screen-tear.
 
I think you meant to say another game and not Just Cause 2, since I would say this is pretty relevant to the overall gaming experience:[/img]

It is... on Xbox 360. Tearing on PS3 is only on the top couple of lines so I removed it as it is not relevant.

With BF:BC2 there is 16% tearing or thereabouts, even after the top five lines have been disregarded from the analysis.
 
Back
Top