AMD Catalyst 13.11 BETA 9.4 (13.250.18.00 November 22)

you are really interesting person. Sometimes people are unfortunate enough to step on such on street and then cleaning smelly shoe.

I apparently can read and I do so around too. And believe it or not, I had same issue as you with 13.11b3/7/8 (13.11b1 was ok).
I did not cry about it because I already knew solution for more than year.
But with 13.11b8 I decided to do manual cleaning I suggested to you and now I do not even need frequency override.

If you don't like it here, you are free not to be here. If you do not want anyone to give suggestions for solution, then don't cry that you have problem.
If your only reason for crying about it is crying itself.
Well I do not know any forum which purpose is to gather cry rivers, rage outburst, ...
So I am afraid I can no longer help you.

 

Is screen tearing still a problem with these?

 

Nope! I'm happy as can be.
DDR2 powa!

EDIT:
Firestrike Extreme:
CAT 13.11 beta 6
p3305

CAT 13.11 Beta 7
P3307

CAT 13.11 Beta 8
P3398

CAT 13.11 Beta 9.2
P3398

CAT 13.11 Beta 9.4
P3398

3DMark11:
CAT 13.10 beta 2
P7738

CAT 13.11 beta 1
P7986

CAT 13.11 beta 8
P8073

CAT 13.11 Beta 9.4
P8075

 

Issue seems to be related to this :



To demonstrate the problem (or what i think is the cause) :

1) I opened a MKV 1080p for 20 seconds : As you can see it causes the gpu memory & core clocks to rise for a half second then back to normal & repeat again & again. It goes from 300 to 501 for the core & from 150 to 1500 for the memory.

2) Then I launched a simple avi 640X480 for 30 seconds : No problems at all & surprise : No clock switching

For me it's clearly that switching between clocks which is responsible :banana:

 

I'm affraid by the responses given to me, that i give the impression of big raging and insulting people where i'm not at all, good lord !
I don't see anything of insulting & whining on the message i answered to you for christ sake !
All i did is : "Do you read everything" which was legit regarding the answer ; 'I'm staying with 13.10 waiting for amd fix" & "This is not bad driver cleaning" "Thanks for movie concerns " and i receive "cry cry cry" & "If you dont like the help given to you go away" :3eyes:

 

Because mkv uses hardware acceleration.

 

Thanks for the answer, i just launched a 640X480 mkv to try, and no problem at all as with the Avi,
Anyway, i may be wrong but the hardware acceleration is purely CPU not GPU on my MPCHC i disabled the gpu acceleration for movies

 

If it's disabled why did your gpu clocks ramp up?

 

AC4 plays great with vsync disabled, and @ 120hz the tearing is not an issue.

 

So still no across the board dx9 frame pacing fix/GCN memory re-write in this beta set? (was'nt this "coming soon" over 10 months ago....)

I think AMD have there dicks in too many pipes atm (XBone Ps4 WiiU) and are fast starting to piss off their core PC market with the slackness in driver updates and fixes

Good job i have a backlog of games to play that they've sofar managed to cherry pick for tuning because im guessing it will be months (again) before we see any real progress with fixes for current titles....

 

That's what i dont understand :deflate: ; and that's why i'm getting display jumping (well i suppose)
What I'm sure, is the display jumping/flickering disappear when 3D performances are fully loaded (like games etc... no problems at all)
It only appears on light apps like videos, firefox browsing etc...

 

UVD clocks...not much you can do about that unfortunately.

**Actually there is, you can edit the clocks with vbios editor from TPU site.

 

UVD Clocks ? Don't understand UVD :giggle2:

 

AMD will not solve it for you. So expect to sit on 13.10 for months to come.
If it's caused by same thing as for me it's actually not related to 13.11b driver packages, but to your variables which are persistent between installations of new drivers and are no longer compatible or out of new specs.

 

The memory rewrite was introduced in 13.3 Betas but it didn't have as much a profound impact as expected.

I wonder though, why exactly do you want a memory rewrite? Because everybody keeps talking about it with every new driver?

And how is frame pacing related to the memory rewrite exactly? Because stutter?

 

Universal Video Decoder.


http://www.slideshare.net/AMD/uvd3-whitepaper-13414220

 

I did not understand what you mean with "variable", i'm not english so there are some words/technical stuff i dont understand sometimes :eyes:

But you scare me when i see "amd will not solve it"
You mean they introduced new things in 13.11 beta with new GPUs that conflicts with ancient ?
I'm a little bit lost

 

Thanks so it's present for ages. Not the problem so
My problem appeared only since 13.11

 

Here ya go

http://www.legitreviews.com/amd-to-...eries-graphics-cards-with-driver-update_14814

http://www.techpowerup.com/178129/amd-to-fix-gcn-latency-issues-with-driver-updates.html

Mem manager rewrite should (so they say) effect stuttering/pacing and texture corruption/flashing across the board

(waiting for the "its your hardware that's faulty" posters to show up before i point them to the many skyrim corruption/flashing threads that show it was a driver issue that took AMD about a year to fix)

I wonder if AMD are still using the older pre-GCN memory management driver code with the cherry picked fixes on the newest 290 series? as we've seen no announcement about an across the board fix i guess it must be so :banana:

 

this driver increased image quality in BF4 for me. 9.2 I had some flicker errors when in killcam, and here it's all nice and dandy. Overall game looks very good with r9 290 in 1440p