| Pages: [1] :: one page |
|
|
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Ardrilian
Gallente
Glowing Goat
   |
Posted - 2009.03.14 12:20:00 -
[1]
Edited by: Ardrilian on 14/03/2009 12:22:30
Edited by: Ardrilian on 14/03/2009 12:21:58
I seem to have a strange problem with the warp and wormhole effects. They appear very pixelated and ugly. (see picture below)
Screenshot of warp effect
All graphics settings are as they should be (or at least I think they are)
Screenshot of settings window
I've also updated the catalyst drivers for my Radeon X1950 Pro but that didn't seem to have any impact.
A friend of mine who is using a X1900 is reporting the exact same problems. Does anyone know if this is an ATI, a X1950/1900 or a general issue? Any solutions for fixing it?
Edit: failed at linking pictures
|
Bordimor
|
Posted - 2009.03.14 16:08:00 -
[2]
I have the same problem with an X1300 Pro.
I also tried different settings without luck.
|
Taika Gun'Kan
Caldari
French Empire Squad
|
Posted - 2009.03.15 00:37:00 -
[3]
I got the same problem. Could you tell me what shader version is recognized on your computer (for info x1950pro video cards run shader 3.0)?
|
Ardrilian
Gallente
Glowing Goat
|
Posted - 2009.03.15 11:56:00 -
[4]
 Originally by: Taika Gun'Kan
Could you tell me what shader version is recognized on your computer (for info x1950pro video cards run shader 3.0)?
I didn't find any software to check the shader model version on my graphics card but according to the manufacturers homepage, as well as Google, my x1950 pro quite clearly supports SM3 in all it's glory (it even mentions HDR and simultaneous anti-aliasing support).
Some more research on the internet however showed that people were experiencing similar problems (massively pixelated effects) the games called "mass effects" and "the witcher". Affected users were using various graphic cards with an ATI chipset mostly from the x1300 - x1950 range).
Some people implied that ATI was to blame for a faulty/partial implementation of SM3 on those cards while oder seemed convinced that it was a mere driver issue. However since those problems date back as far as catalyst 8.5 divers (I'm using 9.2 atm.) I'm not convinced with the driver theory.
If it's an ATI problem however I'd have to assume that there is a lot more users affected by this.
More feedback from other users would be appreciated. Especially if there is anyone out there with a similar graphics card who doesn't suffer from those problems.
|
Ardrilian
Gallente
Glowing Goat
|
Posted - 2009.03.15 12:14:00 -
[5]
I've just found something else which might be of interest. It all sounds rather technical but if I understand the article correctly, it basicly tells us that ATI did something quite bad and the whole x1*00 series has fubared SM3 support which most probably is the reason for the ugly effects that we're seeing:
ati and sm3 tomfoolery
|
Taika Gun'Kan
Caldari
French Empire Squad
|
Posted - 2009.03.15 18:07:00 -
[6]
Very interesting... and sad. Well i guess that this is the last time i buy an ATI video card. I was planning to get a new computer within 2 months. And now i m sure that i won't buy an ATI HD 4870 but a GTX 280 
|
Rex Rawhead
Caldari
Deep Core Mining Inc.
|
Posted - 2009.03.16 11:40:00 -
[7]
Hmm, i have an ATI x800xt and i also have this problem. Actually i thought this was why people were complaining about the warping effect 
|
tx eight
Minmatar
Blueprint Haus
Shadow of xXDEATHXx
|
Posted - 2009.03.16 16:38:00 -
[8]
Edited by: tx eight on 16/03/2009 16:44:19
Edited by: tx eight on 16/03/2009 16:43:11
Edited by: tx eight on 16/03/2009 16:42:22
From the AMD document talking about r300-r500 cards (up to X1950):
Linkage, page 12.
Quote:
All ATI graphics HW have a few items that deserve special consideration when using GLSL. The first major item of note is the absence of vertex texture units.
Cards in X2xxx, X3xxx and X4xxx series (r600-r700) should be fine, so no, you have no excuse for emorageswitch to Nvidia.
Blame routing: Microsoft for flaky specification, ATI for saving money by pretending to implement features, CCP for not researching hardware limitations or not using the R2VB workaround.
|
|
|
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |