Hi Tomshardware people,
After a lot of messing around trying to get hold of a R9 280X TOXIC edition from Sapphire I gave up and went with a Powercolor 280X. It was cheaper but it's the same board so I thought it would be ok.
I was wrong. I've had nothing but problems with this card since I installed it. Even after removing every trace of Nvidia from my system it ran extremely poorly, so I caved and formatted + reinstalled Windows 7 x64, installed all the latest drivers (from Guru3D ironically - because the AMD website was handing out a corrupt version which threw up an RSIS error) and eventually I managed to get it running.
So I've got most of my games reinstalled and I start to test them out, at first it seems fine but *something* just doesn't look quite "right" about the picture. It was really hard to put my finger on but to put it into context I've just come from an nvidia GTX 660 so I was expecting big improvements and this is really disappointing.
Basically AMD seems to have 'puffed up' the raw FPS numbers at the expense of smoothness of gameplay. That's my theory anyway because even at the same resolution on the 660, it was very slow, but it still played *smoothly*. My Powercolor R9 280X on the other hand is telling me via FRAPS that it's pumping out a solid 60+fps but my eyes and motor feedback from the screen are just screaming at me that something is off.
FURTHERMORE: I cannot overclock my monitor any longer. I comfortably overclocked my 27" 1440p QX2710 to 120Hz. With AMD it gets to barely 85 before it just freaks out and (thanks AMD drivers) it does not take well to my hot plugging/unplugging monitors.
To summarise I'm so pissed off with AMD right now, either the card itself or the drivers are just straight up nowhere near ready. I feel (as someone with 20/20 perfect eyesight, been playing with graphics cards since the FX5200) that the R9 280X is a real let down.
If anyone can shed any light on this or has any fixes please let me know before I just RMA this card and get a 770 instead.
Does anyone know what this could be down to?
After a lot of messing around trying to get hold of a R9 280X TOXIC edition from Sapphire I gave up and went with a Powercolor 280X. It was cheaper but it's the same board so I thought it would be ok.
I was wrong. I've had nothing but problems with this card since I installed it. Even after removing every trace of Nvidia from my system it ran extremely poorly, so I caved and formatted + reinstalled Windows 7 x64, installed all the latest drivers (from Guru3D ironically - because the AMD website was handing out a corrupt version which threw up an RSIS error) and eventually I managed to get it running.
So I've got most of my games reinstalled and I start to test them out, at first it seems fine but *something* just doesn't look quite "right" about the picture. It was really hard to put my finger on but to put it into context I've just come from an nvidia GTX 660 so I was expecting big improvements and this is really disappointing.
Basically AMD seems to have 'puffed up' the raw FPS numbers at the expense of smoothness of gameplay. That's my theory anyway because even at the same resolution on the 660, it was very slow, but it still played *smoothly*. My Powercolor R9 280X on the other hand is telling me via FRAPS that it's pumping out a solid 60+fps but my eyes and motor feedback from the screen are just screaming at me that something is off.
FURTHERMORE: I cannot overclock my monitor any longer. I comfortably overclocked my 27" 1440p QX2710 to 120Hz. With AMD it gets to barely 85 before it just freaks out and (thanks AMD drivers) it does not take well to my hot plugging/unplugging monitors.
To summarise I'm so pissed off with AMD right now, either the card itself or the drivers are just straight up nowhere near ready. I feel (as someone with 20/20 perfect eyesight, been playing with graphics cards since the FX5200) that the R9 280X is a real let down.
If anyone can shed any light on this or has any fixes please let me know before I just RMA this card and get a 770 instead.
Does anyone know what this could be down to?