As if there drivers were so good, now they pull this? way to go AMD. Try improving instead of treating your paying customers like this.Just another reason to buy nVidia, its like AMD is trying really hard to go bankrupt.
As if there drivers were so good, now they pull this? way to go AMD. Try improving instead of treating your paying customers like this.Just another reason to buy nVidia, its like AMD is trying really hard to go bankrupt.
Really trolling hard here.
How many people own circa 2007 hardware HD 2000/3000 that aren't planning on upgrading soon?
If you aren't upgrading chances are you dont need new updates coming from AMD.
I dont have any problem with them focusing more on the present, to ensure that they have the very best drivers they can coming out.
HAF922 (3 fan upgraded) 700w ModXtreme
MSI GD-65 // HIS 5850 // Saitek Esclipse
Core i5 750 @ 3.32Ghz (OC Genie) Megahalem w/ 1200rpm Scythe Slipstream
G. Skill RipJaws DDR3 2000 4x2 gig
Samsung SpinPoint F3 1TB // 5:1 Dell Surround
24inch Samsung ToC // MX518
HD4000 was sold at least until HD5000 emerged, that was mid to end 2009 - 2.5 years ago. That is quite recent. Question is, if problems arise for these cards and new games, will AMD react and if so, how quickly? As a paying customer I would not want to ask these questions roughly 3 years after buying my card...
what are u talking about, with my 4890 (the fastest dx10/10.1 single gpu) it still plays things most maxed out with no AOat 1920x1200, the only things that it could not do so far are metro and bf3. i expect it to at a minimum keep up and play things on high until the next gen of consoles comes out.
exactly i got my card in june 09, i bought an HIS from ZZF and it has a 3 year warranty so it is not over yet. on one hand they are being honest about what they support, but on the other the last time they did this there were no updates and they still have not fixed servor08/r2 not being detected by AVE (or CCC) and since there wont be a server 08 driver it will destroy upgrading for alot of people.
Last edited by zanzabar; 04-24-2012 at 11:12 AM.
3770k, M5E, kingston 2x4GB cfr
samsung 2TB F4EG, samsung 840 250GB , CM690II, corsair 750tx
Well for example all '12 drivers for Win 7 64-bit I've tried with HD4850 get about 14K in 3DMark06...because the memory clock is stuck at 2D clocks even in 3D. Normal scores are ~17K.
I hate the amount of regressions AMD's drivers tend to have, because they rush releases to keep the monthly schedule. Some even go unnoticed or unfixed.
For the last year or so, 5x00 series cards have not properly supported dual monitors when overclocked with Overdrive or even BIOS, because no matter what the BIOS 3D clock, later drivers set the GPU at 850/1200 regardless unless you enable overdrive on these cards.
Second monitor flickers horribly to the point that I must run stock frequencies or OC only before starting a game and shutting off the second monitor. (...and it happens to whatever monitor is designated "2" in the driver)...
Otherwise, I haven't had a single problem...and this only happened well into 2010.
Don't get me started on nvidia drivers either, they used to be plagued with problems, especially Vista/7 drivers...up until 2009 (when my 8800GTS 320MB died) I had so many issues...
I worked out a fix for that problem and you only have to set it for your primary display and could OC when i liked.
My 2D clock needs to be 400Mhz GPU and 1200Mhz Mem with 3 monitors, when i set Overdrive it would go to single screen clocks GPU 157Mhz MEM 300Mhz and give the tearing/flicker.
Mem:
<Property name="Want_0" value="30000" />
<Property name="Want_1" value="120000" />
<Property name="Want_2" value="120000" />
changed to
<Property name="Want_0" value="120000" />
<Property name="Want_1" value="120000" />
<Property name="Want_2" value="120000" />
GPU:
<Property name="Want_0" value="15700" />
<Property name="Want_1" value="55000" />
<Property name="Want_2" value="90000" />
changed to
<Property name="Want_0" value="40000" />
<Property name="Want_1" value="55000" />
<Property name="Want_2" value="90000" />
Needed to use enable custom fan Profile and edit that profile that was made.