Saturday, March 16th 2013

AMD Posts Catalyst 13.3 Beta 2 Driver

AMD posted a performance-enhancing beta version of its Catalyst driver suite, version 13.3 Beta 2. The driver provides across the board performance improvements of up to 5 percent in Far Cry 3, up to 16 percent in Sim City 5, reduces frame-time latencies noted in Tomb Raider (2013), and Hitman Absolution; and corrects a slight display corruption issue noted with TressFX enabled in Tomb Raider (2013), on both CrossFire and single-GPU setups.

DOWNLOAD: AMD Catalyst 13.3 Beta 2
Add your own comment

21 Comments on AMD Posts Catalyst 13.3 Beta 2 Driver

#1
Widjaja
Going to download it and see how it performs without looking at the release notes.
Posted on Reply
#3
Aleksander
After I updated to this driver, it doesn't come out any sound from the monitor, but from the mobo it comes.
Any ideas on how to fix this?

I already know that uninstalling this and installing older one will work.
Posted on Reply
#4
H82LUZ73
1,Device Manager
2,select sound and audio
3,right click "update driver"
4,I will select from drive
5,point to your AMD driver install folder select WDM and then the audio driver.
6,Click ok and wait for it to install reboot after it installs.


Hope that helps you out and make sure you select the AMD driver to Default.

Well I had too re-install the 13.1 driver to run BF3 ,I was using 13.2-7 betas and it would black screen ,Any of that with these for you guys using them?
Posted on Reply
#6
95Viper
by: Aleksander
After I updated to this driver, it doesn't come out any sound from the monitor, but from the mobo it comes.
Any ideas on how to fix this?

I already know that uninstalling this and installing older one will work.
If you a speaking of HDMI sound... I had a little quirk happen.
The HDMI AMD card option in playback device had disappeared after install of these drivers (even though it was the same driver installed from the previous driver, just a re-install).

What I did was go to device manager, uninstall the AMD HDMI device under sound; then, did a scan for new devices and the OS found and re-install it.
I went to the playback devices and selected the HDMI sound.
It was back to it's old self, again.

Everything else is fine. I have seen no problems in the couple of games I play or any of the apps I use.
Posted on Reply
#7
Aleksander
The beta drivers are the problem for outputting sound, but no big deal since it is a beta.
Anyway thanks
Posted on Reply
#8
Super XP
My L4D2 game always starts out dark and lasts about 30sec to 5min. To the point where it's difficult to see on screen. I installed these new Beta drivers and now it seems my screen doesn't stay dark as long. This issue is actually quite annoying, not to mention other weird behaviors with this game.
Posted on Reply
#9
erocker
by: Super XP
My L4D2 game always starts out dark and lasts about 30sec to 5min. To the point where it's difficult to see on screen. I installed these new Beta drivers and now it seems my screen doesn't stay dark as long. This issue is actually quite annoying, not to mention other weird behaviors with this game.
I remember having this issue a long time ago with some drivers when the 5 series was new. Might just want to keep trying different drivers until it's fixed.
Posted on Reply
#10
Widjaja
There seems to be issue with people who have older generation cards while using these drivers.
Unless there is a reason for needing to have the latest drivers for an older card, I would stay with the older drivers.

Besides AMD are currently working on or struggling with coding for GCN architecture at the moment so GCN is currently their primary focus which may leave out the older gen DX11 cards.
Posted on Reply
#11
SonDa5
Unable to run OpenGL benchmarks of OpenCL benchmarks but the drivers work awesome for UT3.

:D
Posted on Reply
#13
Ferrum Master
by: SonDa5
Unable to run OpenGL benchmarks of OpenCL benchmarks but the drivers work awesome for UT3.

:D
Wasn't UT3 a DX based?
Posted on Reply
#14
1Kurgan1
The Knife in your Back
by: Frogger
^^Simply download atio6axx.dll (from 13.2 Beta 7) below, and copy and paste it into windows system 32 directory. Should fix any openGL related problems
http://www.mediafire.com/?0t2atow116wngg3
Thanks, was trying to figure out why Adobe Premiere was crashing at launch. I was looking for crashes related to that file earlier, but found nothing, suppose there would be none since the issue is from a brand new beta of drivers.
Posted on Reply
#15
PopcornMachine
Yesterday I tried this driver and then 13.1, but both resulted in the shredding and tearing of my screen when scrolling.

On a whim last night I installed the new afterburner 3.0.0 beta 7.

So this morning I installed 13.1 again and had no problem. Found out from unwinder on guru3d that he and wizard had modified afterburner and trixx to reset display on each config change as a workaround. Guess I missed that news.

They did this since AMD showed no interest in even looking into the issue that they created. Never had a big problem with AMD until this, and unfortunate the other guys had to come up with some sort of solution. I will be very more than open minded about my next GPU purchase.

So I then tried 13.2. and it works Only problem is it doesn't seem to be using my profile for ME3 automatically, but if I use those settings as the system default it works and see lower frame times. This indicates AMD really did do something about their frame latency issues.
Posted on Reply
#16
cdawall
where the hell are my stars
downloaded hopefully it helps with the 7950 and Crysis 3 some...
Posted on Reply
#17
SonDa5
by: Ferrum Master
Wasn't UT3 a DX based?
DX9 but the problem is with OpenGL and OpenCL.
Posted on Reply
#18
SonDa5
by: Frogger
^^Simply download atio6axx.dll (from 13.2 Beta 7) below, and copy and paste it into windows system 32 directory. Should fix any openGL related problems
http://www.mediafire.com/?0t2atow116wngg3
Thanks but that didn't work for me. :twitch:
Posted on Reply
#19
kn00tcn
that's cuz atio6axx is 64bit, you want atioglxx for 32bit (which most benchmark, app, & game usually are), note that the 32bit system folder is SysWOW64

personally i put dlls into the game/app folder instead of the system

so just extract the dll from the driver that you know works

btw this driver shows a glimpse of a halo 3 profile inside the CAP

1
False



Halo3
Posted on Reply
#20
Widjaja
Hm...I think DX9 has gone backwards again.
Noticed rare artifacting in Skyrim again.
For me it is a smatter of coloured polys in the center of the screen for one frame within hours of gameplay.
But on the upside I do not seem to have random CTDs anymore.
Posted on Reply
#21
blackdragon
Help black screen!!!

So I went to update my catalyst to the most recent update. Went to http://support.amd.com/us/gpudownload/Pages/index.aspx and followed the steps for my computer specs. Well when it was done I went on ahead and ran the program I just got. (the beta 13.3 for catalyst) It did its thing I clicked install and then it went to the installer. Clicked express and let it do its thing. I come back about an hour later and my whole computer screen is black and nothing is happening.......I don't know what I did wrong? :/ I did the exact thing for previous version and they worked just fine..... someone help? I'm afraid if I turn it off something bad will happen and I will end up breaking my computer.
Posted on Reply
Add your own comment