Again there seems to be some confusion.
A slight spike in the green GPU line doesn't mean its stuttering....at all, it means the rendered frame is being delivered slower then the previous, which depending on refresh and frame rate it occoured at may be completely unnoticeable. You need to look at the relative graph scale too, a big spike might only represent 3ms uplift in turn meaning a drop 10fps or so? That won't cause stutter at the frame rates Greg is at. Mantle remains flat as each frame is at a consistent rate where as DX on both sides of the fence have more variable frame rates, in turn a less then perfectly flat line.
Frame times are used to find runt frames, a frame being rendered at the correct speed but being delivered late, a 16.6ms frame being delivered at 33ms for example. THIS is what causes stutter and what kicked off the whole frame time argument. You will get frame reduction stutter, like dropping from 60 to 20, there would be a spike in the graph but it wouldn't represent a frame time causing the issue, it would merely be the reduction in rate
A slight spike in the green GPU line doesn't mean its stuttering....at all, it means the rendered frame is being delivered slower then the previous, which depending on refresh and frame rate it occoured at may be completely unnoticeable. You need to look at the relative graph scale too, a big spike might only represent 3ms uplift in turn meaning a drop 10fps or so? That won't cause stutter at the frame rates Greg is at. Mantle remains flat as each frame is at a consistent rate where as DX on both sides of the fence have more variable frame rates, in turn a less then perfectly flat line.
Frame times are used to find runt frames, a frame being rendered at the correct speed but being delivered late, a 16.6ms frame being delivered at 33ms for example. THIS is what causes stutter and what kicked off the whole frame time argument. You will get frame reduction stutter, like dropping from 60 to 20, there would be a spike in the graph but it wouldn't represent a frame time causing the issue, it would merely be the reduction in rate
Last edited: