The AMD Driver Thread

shankly1985 · 4 Jul 2015 at 23:36

Mei said:
news just in!!
shankly defends AMD making ppl cry!!!

TBH I find it completely something silly to cry over.. Sorry if its harsh but black bars around a screen worth crying over?

If it was my son I would explain the reason why they is a black bar around the screen and then show him how to fix it!

@Dad
Instead spitting his dummy out! I have heard it all, am Changing my GPU because my HDMI has black bar around screen lol

Am sure if he fully understood the reason why AMD do this on the HDMI port he would appreciate the fact they allow the change.

Confused Stu · 4 Jul 2015 at 23:39

Agreed that the overscan on HDMI is a good setting to include in the drivers (my old Philips TV needed a little to fit the output to the screen), but I don't understand why AMD set it midway by default. Why not set it to zero by default, or are they concerned people won't be able to open CCC if they can't see the Start button on the screen?

shankly1985 · 4 Jul 2015 at 23:41

Confused Stu said:
Agreed that the overscan on HDMI is a good setting to include in the drivers (my old Philips TV needed a little to fit the output to the screen), but I don't understand why AMD set it midway by default. Why not set it to zero by default, or are they concerned people won't be able to open CCC if they can't see the Start button on the screen?

Yeah I think its more a safety first, better to have more view then have it off screen.. All TVs and even some monitors display HDMI different, Mostly TVs and old ones also..

Mei · 4 Jul 2015 at 23:53

but...but... *cry*
i cant find the button where to change it!
*sob*
that was me

Finners · 5 Jul 2015 at 00:23

LoadsaMoney said:
Thanks, might give em a try then (still on the 15.4 BETAs, GTA V ones), what about those 1040s, any faffing about for those, or is the video player fix for Win 10 ?

I think the 1040's are the ones that have video play back issues unfortunately.

LoadsaMoney · 5 Jul 2015 at 00:28

Finners said:
I think the 1040's are the ones that have video play back issues unfortunately.

Thanks, i'll give those a miss then, just popped these 1023s on, nice boost in FS, went from 10785, to this :-

Seem fine, will give em a proper testing tomorrow

deuse · 5 Jul 2015 at 07:02

Superpatsy said:
I've done plenty of builds with AMD cards for friends and myself and I've never once come across this issue.

If you use HDMI you'll always get it.
For some stupid reason they forget about it and release a fix later. Stupid AMD are stupid.

deuse · 5 Jul 2015 at 07:11

Mei said:
news just in!!
shankly defends AMD making ppl cry!!!

shankly1985 said:
TBH I find it completely something silly to cry over.. Sorry if its harsh but black bars around a screen worth crying over?

If it was my son I would explain the reason why they is a black bar around the screen and then show him how to fix it!

@Dad
Instead spitting his dummy out! I have heard it all, am Changing my GPU because my HDMI has black bar around screen lol

Am sure if he fully understood the reason why AMD do this on the HDMI port he would appreciate the fact they allow the change.

You do know the child is autistic?

It's because amd forget but then release a fix later.
At least NVidia knows what kind of display it's working with

I've seen fan boys before, but you sir are the worse kind.

Final8y · 5 Jul 2015 at 08:10

deuse said:
You do know the child is autistic?

It's because amd forget but then release a fix later.
At least NVidia knows what kind of display it's working with

arknor Installed the drivers not the child and the AMD overscan is doing exactly as AMD intended whether you like it or not, at the end of the day its user error.

deuse · 5 Jul 2015 at 08:30

Final8y said:
arknor Installed the drivers not the child and the AMD overscan is doing exactly as AMD intended whether you like it or not, at the end of the day its user error.

So why do amd release a fix? when amd released the Omega drivers they had to release a fix a week later.
If it wasn't part of the driver they wouldn't release a fix.

http://support.amd.com/en-us/kb-articles/Pages/GPU-5001.aspx

"This AMD Catalyst HDMI Hotfix driver does not downscale the image, therefore, on most HDMI displays image will be displayed in proper size."

They forgot about adding the fix for the last 6 months. Even AMDMatt thanked people for pointing their mistake out.

Final8y · 5 Jul 2015 at 08:41

deuse said:
So why do amd release a fix? when amd released the Omega drivers they had to release a fix a week later.
If it wasn't part of the driver they wouldn't release a fix.

http://support.amd.com/en-us/kb-articles/Pages/GPU-5001.aspx

"This AMD Catalyst HDMI Hotfix driver does not downscale the image, therefore, on most HDMI displays image will be displayed in proper size."

They forgot about adding the fix for the last 6 months. Even AMDMatt thanked people for pointing their mistake out.

August 2012

If you have an AMD/ATI Radeon GPU or graphics card connected to a TV, then you have probably been surprised by the black borders that appear around the screen. When I first attached my TV, I thought that it was the fault of the TV and that I needed to get a new one, because I could find no setting to correct the problem on the TV. Actually, it is the default setting of the Catalyst Control Center (CCC) to have 10% underscan when a TV is detected.

What is surprising is that many monitors are now sold at 1920x1080 resolution (1080p) and are erroneously detected as TVs and have the black border added. This has occurred in the last several monitors that I have either bought for myself or that I have installed at work.

The first solution to try is the obvious one of opening CCC and navigating to the My Digital Flat-Panels / Scaling Options tab in the advanced menu. Set overscan to 0%. There is also a check box that says Use the scaling values instead of the customized settings [...]. As far as I can tell, this box has no effect.

Its been doing it for years, its no big deal moving a slider.

Mei · 5 Jul 2015 at 09:10

ye tho 1st you got to find the slider

but feel i need to defend shankly a little here i dont think he meant it as bad as it looked lol
was some skim reading going on mebe

thats how i took it anyway

deuse · 5 Jul 2015 at 09:14

Final8y said:
Its been doing it for years, its no big deal moving a slider.

Thank you admitting that amd have been releasing HDMI fix's for years. Because they haven't got a good driver team.

You're one big fan boy, even down to picking on children.

Mei · 5 Jul 2015 at 09:23

Martini1991 · 5 Jul 2015 at 09:25

Everytime I've ever used HDMI with AMD I've had to do the overscan.
It's never really bothered me, but for those who don't know any better, I can see an issue lol.

I thought it was just a HDMI thing, and didn't even consider if it'd do it on Nvidia or not.

deuse · 5 Jul 2015 at 09:34

Martini1991 said:
Everytime I've ever used HDMI with AMD I've had to do the overscan.
It's never really bothered me, but for those who don't know any better, I can see an issue lol.

I thought it was just a HDMI thing, and didn't even consider if it'd do it on Nvidia or not.

Maybe it's down to amd not likeing HDMI. I mean they missed out HDMI 2.0 on the Fury where as NVidia has never had this problem.

Anyway. Wonder if the 200s will see any optimized drivers this year?

Bonjour · 5 Jul 2015 at 09:36

I've always had to overscan my htpc boxes, which have used AMD cards. I never realised it was an AMD-specific issue.

Final8y · 5 Jul 2015 at 09:42

deuse said:
Thank you admitting that amd have been releasing HDMI fix's for years. Because they haven't got a good driver team.

Show me another HDMI fix, there has only been one that im aware of, you will likely not find another because most users work out there is a slider and not being set to 0 by default is not a big issue, unlike the limited colour range over HDMI that NV had for nearly a decade which could not be fixed by a matter of moving a slider because they haven't got a good driver team..
We could all pick anything about AMD or NV we dont like an label then crap because of it, but most of us will not go into a forum and keep going on and on about it when its a trivial issue.

hyperseven · 5 Jul 2015 at 09:58

Overscan has been a problem for donkeys, 60Hz is fine but have to adjust for 50 and 24 which I need for media.

deuse · 5 Jul 2015 at 10:09

Final8y said:
Show me another HDMI fix, there has only been one that im aware of, you will likely not find another because most users work out there is a slider and not being set to 0 by default is not a big issue, unlike the limited colour range over HDMI that NV had for nearly a decade which could not be fixed by a matter of moving a slider because they haven't got a good driver team..
We could all pick anything about AMD or NV we dont like an label then crap because of it, but most of us will not go into a forum and keep going on and on about it when its a trivial issue.

Read THIS thread Fan Boy. AMDMatt has thanked people for pointing out their driver teams mistake.
And when AMD do a fix for the latest driver they take the last one down on their site.

Oh Oh I get it now....I've seen through your BS posts and the suck up.
You want to be the next AMDFinal8y :eek:

you've been found out.

But you will be known as @FANBOYFinal8y