AMD Catalyst 13.11 Beta Driver for Windows

HardOCP News

[H] News
Joined
Dec 31, 1969
Messages
0
AMD sends word that the brand new Catalyst 13.11 Beta driver for Windows has just been released. Feature highlights of the AMD Catalyst 13.11 Beta9.5 driver for Windows:

  • Includes all Feature Highlights of The AMD Catalyst 13.11 Beta9.4 Driver
  • Resolves the issue of AMD Overdrive missing in the AMD Catalyst Control Center for the AMD Radeon™ R9 290 Series graphics cards
  • Resolves intermittent flickering seen on some AMD Radeon R9 270x graphics cards
  • Resolves graphics corruption seen in Starcraft®
  • Improves frace pacing results in AMD Quad CrossFire™ configurations for the following: Hitman: Absolution, and Total War™: Rome 2
 
let's see if they are any better than the last ones that gave me massive audio corruption, graphical corruption, and about 10% of normal performance I should have had on a crossfire pair of R9 290's

I will also say again what I've been saying for a while, all this time after the official release of the R9 series and we are still using beta drivers? I'm not asking for WHQL, I'm just asking for something AMD would be willing to stand behind vs "it's beta deal with it" song and dance.
 
let's see if they are any better than the last ones that gave me massive audio corruption, graphical corruption, and about 10% of normal performance I should have had on a crossfire pair of R9 290's

I will also say again what I've been saying for a while, all this time after the official release of the R9 series and we are still using beta drivers? I'm not asking for WHQL, I'm just asking for something AMD would be willing to stand behind vs "it's beta deal with it" song and dance.

Its either Beta or WHQL, so saying that your not asking for WHQL but dont want the beta label is a contradiction.
 
has there been a whql drive for the 290's? its only been out a month.
 
Improves frace pacing results in AMD Quad CrossFire™ configurations for the following: Hitman: Absolution, and Total War™: Rome 2

Wow, frace pacing improvements!
I think they should have worked on frame pacing improvements instead. :p
 
Does AMD ever release non-beta drivers? Here's to seeing the new (non-beta) driver released 4 months after the previous release.
 
As has been said many times by amd: They will release WHQL when they feel like its ready, no set schedule.
 
As has been said many times by amd: They will release WHQL when they feel like its ready, no set schedule.

does it really matter if its a beta driver or official driver? when chances are people playing the latest games will be using a beta driver any way because they usually have tweaks or crossfire profiles for the new games.
 
they sure are taking long to release a driver for AC4. my 2nd 290 has 0% usage in that game. no crossfire profile.
 
does it really matter if its a beta driver or official driver? when chances are people playing the latest games will be using a beta driver any way because they usually have tweaks or crossfire profiles for the new games.

i would agree, but there isnt a whql driver for the 290's. really, they have been out a month. how do you launch a gpu without a whql driver?
 
Just got rid of my 290x that gave me nothing but problems.

Sorry AMD, I gave you guys a chance but you failed me HARD.
 
for fraks sake amd release a whql driver im tired of weekly beta updates
 
You buy a new release piece of hardware an expect it to work?

Grow up, you are early adopters, yeah their will be issues.

Every piece of hardware has issue at the start, remember when Intel had to do a recall on the sandy bridge chipset as it was faulty?
 
You buy a new release piece of hardware an expect it to work?

Grow up, you are early adopters, yeah their will be issues.

Every piece of hardware has issue at the start, remember when Intel had to do a recall on the sandy bridge chipset as it was faulty?

well in fairness a portion of the price we are paying is going towards QA/QC. my 290X has been trouble-free but if i paid $550 for something and it caused nothing but problems, i'd be miffed too.
 
You buy a new release piece of hardware an expect it to work?

Grow up, you are early adopters, yeah their will be issues.

Every piece of hardware has issue at the start, remember when Intel had to do a recall on the sandy bridge chipset as it was faulty?

Nvidia apparently does not have these "launch" issues....AMD should not have launch issues either. Buying a product an "expecting" issues is ludicrous, I can't even figure out if you're serious right now.
 
Nvidia apparently does not have these "launch" issues....AMD should not have launch issues either. Buying a product an "expecting" issues is ludicrous, I can't even figure out if you're serious right now.

Yes NV has no problem having WHQL drivers that kills GPUs 196.75 WHQL, 320.18 WHQL and specifically 267.71 WHQL on the 590 if you overclocked because there was a driver error to which overload safety feature was not triggered.

Yes NV has no problem having WHQL drivers that caused Vsync and Dynamic Vsync issues for many users with the 6 series launch.

Yes NV has no problem having WHQL drivers that did not work for many users with the 7 series launch and users had to use modified install inf 6 series drivers to get them to work.
But hey at least they were WHQL because the name is more important than the functionality to some people.

And many 4 and 5 series users have had a nightmare for the last nine months beta and WHQL.


https://forums.geforce.com/default/...driver-feedback-thread-released-11-19-13-/44/

https://forums.geforce.com/default/board/33/
 
Last edited:
So are these new drivers worth installing? Mostly playing BF4/FFXIV ARR. And doing some streaming on twitch.
 
flickering textures, sluggish performance in bf4 and about 10 fps lower than before.

Rolling back drivers.
 
I didn't even bother to try them since the notes stated improvements to the 290/270 series. I treat my 280x like the bastard child it is. Still waiting on the frame pacing driver too... Yes, 290s already have it, rub it in!

Beta 8 was a good driver, 9.2 was horrible for me, but 9.4 seems to be the best for my setup so far.
 
Yes NV has no problem having WHQL drivers that kills GPUs 196.75 WHQL, 320.18 WHQL and specifically 267.71 WHQL on the 590 if you overclocked because there was a driver error to which overload safety feature was not triggered.

Yes NV has no problem having WHQL drivers that caused Vsync and Dynamic Vsync issues for many users with the 6 series launch.

Yes NV has no problem having WHQL drivers that did not work for many users with the 7 series launch and users had to use modified install inf 6 series drivers to get them to work.
But hey at least they were WHQL because the name is more important than the functionality to some people.

And many 4 and 5 series users have had a nightmare for the last nine months beta and WHQL.


https://forums.geforce.com/default/...driver-feedback-thread-released-11-19-13-/44/

https://forums.geforce.com/default/board/33/

how's quadfire on your 5970's?
 
they sure are taking long to release a driver for AC4. my 2nd 290 has 0% usage in that game. no crossfire profile.

What happens when you create a custom profile in the driver for the AC4 executable and choose "AFR-friendly" or "1x1 Optimized" for the Crossfire mode? After all, that's why they included those options in the driver, so you could use a generic Crossfire profile and make use of your 2nd card while waiting for them to create a more optimized profile.
 
Nvidia apparently does not have these "launch" issues....AMD should not have launch issues either. Buying a product an "expecting" issues is ludicrous, I can't even figure out if you're serious right now.

NVIDIA do have these issues, I help managed several peoples rigs and NVIDIA most certainly do release bad drivers.
 
I love how much we talk about nVidia drivers in these AMD threads... Anyway, with the latest 13.11 beta (9.5) I am still forced to disable frame pacing in BF4 if I want to use vsync.

System: W8.1, 3960x, 7970s CFX'd

Does frame pacing even benefit the end-user when vsync is being used? If rendering capability is above the refresh rate, doesn't vsync force the frames to be drawn in a consistent synchronized manner?
 
not really, vsync chokes the input to the pipeline, not the output.

The latecy is still there, its just covered up
 
thoeretically, yes.

however, choking the input may have unforeseen consequences on the pacing output. I dont know exactly how they are pacing the output, so maybe the pacing code sees the choked input as additional latency and tries to compensate hosing the whole thing up.

People have reported using both vsync and pacing simultaniously in certain games produces less than optimal performance.
 
Back
Top