• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

13.2 Beta Drivers Leaked :)

http://techreport.com/review/24218/a-driver-update-to-reduce-radeon-frame-times

it's the only review out there, though you wouldn't have known that unless you'd looked. it's pretty interesting, though as i say it seems like 13.2 is a hotfix for a few games only.

This is a great test outcome for ATI users, I read the first test when they didnt do so well just as I was buying my HD7950 and im glad I stuck with it, this is coming from a long line of Nvidia cards.
 
I only skimmed through it but would AMD have provided the new beta drivers to fix it in that case?

Our report on this driver was delayed by a couple of factors, including our attendance at CES and an apparent incompatibility between this beta driver and our Sapphire 7950 card.

We still haven't figured out the problem with the Sapphire card, but we ultimately switched to a different 7950, the MSI R7950 OC, which allowed us to test the new driver. The results on the following pages come from the MSI card.

http://techreport.com/review/24218/a-driver-update-to-reduce-radeon-frame-times

Discussion elsewhere about it

http://www.overclock.net/t/1350380/13-2b-drivers-solve-frame-latency-problems/10#post_19083338

Don't know how much truth there is in it, but there you go.
 
Are they 'completely' unbiased though? I tested Skyrim myself, largely because my own experience didn't match the video TR posted, and it was fine;

skyrimframetimes.png


So what's the explanation for that? I'm finding it more and more difficult to trust any of these 'tech' sites as continually my own experience (and what I see other users reporting in forums) with hardware is not what they are reporting. Still, the response from AMD suggests they still found an issue so that can only be a good thing.

It also raises more questions for me. Like where is the TR article looking at the messy frame times in BF3 (potentially other games too?) on Nvidia (specifically a 660ti) that we've seen users post? And how come they think the 7950 goes up against a 660ti anyway, when there's people around posting stuff that shows the 7870 is the card that competes very favorably with the 660ti? :confused:

AMD's biggest problem for me is it's PR machine, it's clearly no where near as effective, or possibly aggressive, as Nvidia's.
 
See above Wolvers, there are rumours going around that TR's 7950 was faulty.

This is what I was trying to point out to captain clueless the other day (weehamish) when he was making silly claims again about how TR have proven him right.

Some people just won't accept that TR's findings aren't absolute and happen for everyone.
 
Wolvers, that looks far from fine to me (not having a dig). Spikes of over 150ms and even over 200ms in one place shows it isn't.

If I have misunderstood your post and that isn't your chart, my apologies.
 
That looks to be what you'd expect on average Greg. The vast majority of the frames are rendered very similar intervals.

A few large spikes like his won't be very noticeable if at all and don't indicate that there is an issue.

Frame spikes like that can happen due things loading into memory and so on.

If you compare his graph to the TR ones you'll see a massive difference.
 
Last edited:
That looks to be what you'd expect on average Greg. The vast majority of the frames are rendered very similar intervals.

A few large spikes like his won't be very noticeable if at all and don't indicate that they're is an issue.

Frame spikes like that can happen due things loading into memory and so on.

If you compare his graph to the TR ones you'll see a massive difference.

Its a good point actually, things popping up on screen like mission objectives and stuff cause spikes like that, ive noticed that myself on several different games through my own testing.
 
That looks to be what you'd expect on average Greg. The vast majority of the frames are rendered very similar intervals.

A few large spikes like his won't be very noticeable if at all and don't indicate that they're is an issue.

Frame spikes like that can happen due things loading into memory and so on.

If you compare his graph to the TR ones you'll see a massive difference.

Fair enough. I need to do some frame times with these 310.90 drivers to see if I get the same. They feel horrid to me in BF3 and Far Cry 3, so possibly Nvidia are prone to this frame latency issue.

I will run a game I consider smooth and compare to a game I don't and compare.
 
Its a good point actually, things popping up on screen like mission objectives and stuff cause spikes like that, ive noticed that myself on several different games through my own testing.

Yep, it's reasons like this that reviews often do three runs per benchmark and then take the average, because spikes/dips like that are impossible to completely predict and control.

Fair enough. I need to do some frame times with these 310.90 drivers to see if I get the same. They feel horrid to me in BF3 and Far Cry 3, so possibly Nvidia are prone to this frame latency issue.

I will run a game I consider smooth and compare to a game I don't and compare.

Well take Farcry as an example as I know you've been having smoothness issues with it .

If you did a frame time graph, those sort of spikes would much more frequent and would show a spike every second or so.

Basically with frame times, the closer to a straight line the graph is on average, the smoother or more consistent the frames rendered. So in a completely ideal situation, a game running at 60hz with vsync would be a perfect straight line.
 
I'm going to be playing Max Payne 3 and Farcry 3 for a good amount of time today, ill record some long sessions (1 hour plus) and will record the frame times.
 
Recorded 5 mins of frame times with fraps but a little confused on what I am looking at.

Frame, Time (ms)
1, 0.000
2, 9.295
3, 21.256
4, 32.637
5, 43.977
6, 53.840
7, 62.980
8, 71.485
9, 82.962
10, 91.938
11, 101.128
12, 111.264

Any help please?
 
Back
Top Bottom