[Albuquerque]

I don't disagree, but it still somehow exists. I needed to subtract about 5% for the picture to fit correctly; go figure. Without it, the start button is chopped off almost entirely and nearly all icons along the left edge were not visible sans the text label.

[Grall]

Do you get a re-scaled image then or an actual bona fide 1:1 pixel image? All digital outputs should just be straight pipes, no mucking about with overscan. If for some reason a video source needs CC removal, that should be handled by the video player, not the graphics output hardware.

[homerdog]

Originally Posted by Albuquerque

I don't disagree, but it still somehow exists. I needed to subtract about 5% for the picture to fit correctly; go figure. Without it, the start button is chopped off almost entirely and nearly all icons along the left edge were not visible sans the text label.

Maybe you can adjust your TV instead of the GPU output. Most TVs I've seen have an option for "Just Scan" or something like that which does 1:1 mapping with no overscan.

[Albuquerque]

No 1:1 mapping available, unfortunately. Even without overscan.

I'm quite sure the older TV is to blame; it's a tri-panel LCD rear projection unit made by Hitachi. It has good picture quality for what it is, but it's still eight years old. Some day when it dies, I'll replace it with a far more modern unit that (hopefully) does 1:1 mapping on digital inputs.

[swaaye]

The overscan on HDTVs is definitely something that varies by TV. Some TVs don't need adjustment. Also, using VGA is sometimes the best choice for various reasons with TVs (ie color range, DPMS and avoidance of image enhancement).

[Richard]

Originally Posted by Grall

Maybe they should moularize stuff more, or do they figure people have so much disk space these days that who cares about seven score and ten megabytes of files not relevant to your currently installed hardware?

I don't care about the HD requirement. I do care about the measurable AND noticeable delay my i7 2600k + 8gb RAM experiences at boot whenever CCC is installed (and I don't mean when the native image generation is running). I also care about the two processes the AMD service spawns when ATT gives me everything I need without needing to run at all.

[tangent]
CCC needs to either die or be rebuilt on non-.NET. I like .NET mind you, I often develop on it myself but for a glorified registry editor you don't need it and you certainly don't want it on a performance context. Especially since ATI saw the light and removed the skinning option from it and the real-time 3D previews. ZOMG WinAmp is popular, people want skins on EVERYTHING! Or ZOMG, people want to wait a good 10 seconds for their registry editor to load the splash screen or tick a checkbox and watch their computer freeze for a couple of seconds while the renderer is reset and the assets reloaded. Engineering Masturbation.
[/tangent]

Btw, I do think the driver installer package is already fairly modular. It let's you install just the driver (+ Catalyst Installer grrr) which is what I do plus a bunch of other things separately: OpenCL SDK, HTMI/Audio, CAP, etc. In fact, if the CAP is now recommended even for singlegpu parts they might as well roll it with the driver.

[Babel-17]

I forgot to mention, regarding the 12.6 betas, I'm getting a problem with disabling ITC processing not being "remembered".

My Sony XBR6 limits my options with ITC processing enabled. I end up stuck being unable to use my tweaked, advanced, settings.

So every boot up I have to enable, then disable, ITC processing.

[mczak]

Originally Posted by Grall

Why is there even such a thing as overscan correction on HDMI? That thing's a holdover from vacuum tube TVs in the SDTV era that ought to have been just killed by now. Killed and killed again, so it's dead.

Digital video broadcast still relies on overscan, there's still some garbage around the edges quite often otherwise - though IME usually only very few pixels nowhere needing close to ~5% overscan that TVs are doing... So if you have some sort of digital receiver connected to a display device with hdmi you need overscan (or your receiver could do scaling but I think things just weren't designed that way).
But yes this is a ugly relict carried over for some reason from analog tv. This is however no excuse for producing display devices which cannot disable overscan, these are just BROKEN (I believe though they very rightfully finally died out).

[Albuquerque]

I believe I have figured out the long idle issue; multiple threads on various forums pointed to the use of an HDMI cable (or, in my case, an HDMI connected to the card that then feeds an HDMI->DVI connector at the TV) which somehow b0rks the process.

I swapped for a bog-standard DVI cable and my power draw now drops properly when the TV is fully off. It was a pretty decently sized chunk of power too; 55W idle moved to ~39W idle. Still more than the 2W add that I was expecting (compared to the 35W idle power of the integrated graphics), but better than the 55W idle I was getting.

[Grall]

Btw, I just noticed that AMD fixed the powertune slider bug for systems with two (or possibly, more) GPUs in the same system in the 12.6 beta driver. Thank you, that only took what, six months?

[Albuquerque]

Oh, yeah the powertune slider never stays where I put it for my 7750 either (-30%). But that's Cat 12.4's; sounds like the betas might fix it...

[Babel-17]

Originally Posted by Babel-17

I forgot to mention, regarding the 12.6 betas, I'm getting a problem with disabling ITC processing not being "remembered".

My Sony XBR6 limits my options with ITC processing enabled. I end up stuck being unable to use my tweaked, advanced, settings.

So every boot up I have to enable, then disable, ITC processing.

Sweet, AMD fixed this too with the slightly newer betas I found over at Guru3D.

http://forums.guru3d.com/showthread.php?t=364084

[jakobx]

I have some stability problems with my new sapphire 7850 OC on win7 x64 with latest beta drivers. Ive only had it for a week, but so far i havent had any crashes while actually using the computer (desktop or 3d). It seems that after my monitor goes to sleep it has trouble waking up. A lot of times i will see a corrupted screen. When this happens its a 50/50 chance that either i can continue working like nothing happened or i will have to restart the computer because the only thing responding is my mouse.

I can see LiveKernelEvent related errors in event viewer and the culprit is AMDs driver.

Has anyone had the same problem as me? Is it perhaps a known bug? Any workarounds?

[Richard]

I had never seen it on a desktop but this is an usual ocurrence on laptops (obviously*). I last had it (consistently) with a nvidia card. Some drivers would often not resume from sleep forcing me to revert to an earlier version. You should also make sure you have all the chipset drivers up to date.

* I'm curious, do you mean sleep as in your desktop has a battery or hibernate?

[jakobx]

The computer is always on. Only my monitor goes to sleep after 20 minutes.

All the drivers should be up to date (just built the machine last week).

Maybe the real 12.6 driver will fix this problem. AMD hasnt had much luck with drivers this year jusdging by all the problems people have.

[Dave Baumann]

Remember, please report issues here

[jakobx]

Originally Posted by Dave Baumann

Remember, please report issues here

Reported.

[Davros]

Found this :

ith the release of the AMD Catalyst™ 12.6 Beta driver (“Catalyst”), AMD would also like to announce that we are moving away from our Monthly Catalyst release plan. Our goal is to ensure that every Catalyst release delivers a substantial benefit to our end users; as we have today with the release of the Catalyst 12.6a Beta. We will still continue with the Catalyst naming convention; Catalyst: Year.Month. You just won’t see a new driver every single month. We are confident that this will only benefit the end user; you’ll only need to upgrade to a new Catalyst driver, when it makes sense. We would also like to announce the introduction of our new AMD Issue Reporting Form. We made a number of improvements to the older Catalyst Crew Feedback form, making it more comprehensive, ensuring high quality feedback. Feedback is very important in every product company’s life, especially in our fast paced environment. This is not just a check-box for us – we take these reports very seriously. We will review every report posted here and investigate every issue encountered. Please use this form whenever you encounter something worth mentioning.

[Svensk Viking]

Looks like 12.4 was the last driver for the good old HD 4870 before going to legacy then

[Grall]

"Good"... Well, everything's relative I guess. Those cards were powerhogs in idle mode (~40W each in crossfire, even at 2D clocks), and while decently fast in games for their time they didn't run Crysis that well, nor most GPGPU apps either.

Today you should be able to find something (maybe much) faster that draws way less power (and thus not belching such copious amounts of heat), won't have legacy status drivers and not have such noisy fans either...

[swaaye]

Grall - Your 8800GTX cards are older, hotter and slower but have better support.

Their 4000 series was pretty popular. I'm surprised they had the gall to backburner them. But perhaps their legacy support will be decent. It sounds like the mainline cards won't get new drivers much more often either.

[3dcgi]

If Nvidia isn't spending time optimizing apps for the 8800 (which I suspect) they're legacy and you just don't know it.

[eastmen]

Originally Posted by Grall

"Good"... Well, everything's relative I guess. Those cards were powerhogs in idle mode (~40W each in crossfire, even at 2D clocks), and while decently fast in games for their time they didn't run Crysis that well, nor most GPGPU apps either.

Today you should be able to find something (maybe much) faster that draws way less power (and thus not belching such copious amounts of heat), won't have legacy status drivers and not have such noisy fans either...

Well I bet Nvidia was still selling the 8800 in 2011 while amd basicly stoped with the 48x0 in late 2009 early 2010 when the 5x00 series became popular.

Heck the g80 chips are basicly the gt 200 chips that were used in the geforce 300 series

[swaaye]

Originally Posted by 3dcgi

If Nvidia isn't spending time optimizing apps for the 8800 (which I suspect) they're legacy and you just don't know it.

Perhaps, but I'm not sure how to tell when the 8800GT that I have runs everything I throw at it. 38x0 has not been so fortunate. I imagine the fact that a bazillion G9x cards are out there has an effect on this.

[Svensk Viking]

Originally Posted by swaaye

Perhaps, but I'm not sure how to tell when the 8800GT that I have runs everything I throw at it. 38x0 has not been so fortunate. I imagine the fact that a bazillion G9x cards are out there has an effect on this.

I've noticed that Nvidia's Windows 8 driver also supports all their cards from the Geforce 6 series.

My trusty old HD 4870 will only be supported by the driver coming with Windows 8, which I guess means no catalyst. Well, since I don't like how Win8 looks I guess I'll comfort myself with that

Having read about DX11 being a superset of DX10.1 and even bringing some benefits like DX11 multithreading support on DX10 and 10.1 hardware, I was hoping those cards would continue being supported for yet a while