jmke

Thank you for bringing this issue to our attention. Our driver engineers have looked at the problem, and found that it had crept into the code due to the changes made to support AA on new UT3 engine based games. So the root cause of the problem has been identified and it will be addressed in a future driver. You should know that the UT3 engine does not normally support AA, but AMD has put a lot of effort into adding it, so that our users can benefit from improved visuals in those games using it. We had not received any Catalyst reports of the problem before this article was published. In the future, we would like to be informed of rendering issues and given some time to investigate. Negative speculation on improper optimization is unwarranted. Adding features not intended to games is not trivial and often can lead to visual changes, which we try to address. It’s a complex process that creates new rendering paths in the driver which need extensive quality checks; but we gladly do this to benefit our users. Regular rendering (non-AA) shows no anomalies and is proof that the issue is not related to Catalyst A.I. itself

http://www.pcgameshardware.com/aid,6...d_a_statement/

__________________