03-12-2011, 03:42 PM
I've identified a new AMD/ATI driver bug when enabling shaders.
A workaround has been implemented in r2015: to activate the workaround, the option "Enable dynamic shader generation" has to be selected.
The workaround has been tested on different Catalyst versions (thanks to Darth for alpha-testing!):
- Catalyst 11.2: this version is bringing new bugs, even when shaders are not activated. Not recommended.
- Catalyst 11.1: the workaround is bringing some improvements in this version, but it is far from being perfect. You might experience different results depending on the tested application.
- Catalyst 10.9: not thoroughly tested, but the workaround seems to bring the most significant improvements in this version.
You can provide feedback when testing r2015 with AMD/ATI shaders in this thread. Please always provide a log file and screenshots, this might help me improving the support for AMD graphic cards.
AMD will probably soon release a Catalyst 11.3, let's see if this one brings new improvements...
A workaround has been implemented in r2015: to activate the workaround, the option "Enable dynamic shader generation" has to be selected.
The workaround has been tested on different Catalyst versions (thanks to Darth for alpha-testing!):
- Catalyst 11.2: this version is bringing new bugs, even when shaders are not activated. Not recommended.
- Catalyst 11.1: the workaround is bringing some improvements in this version, but it is far from being perfect. You might experience different results depending on the tested application.
- Catalyst 10.9: not thoroughly tested, but the workaround seems to bring the most significant improvements in this version.
You can provide feedback when testing r2015 with AMD/ATI shaders in this thread. Please always provide a log file and screenshots, this might help me improving the support for AMD graphic cards.
AMD will probably soon release a Catalyst 11.3, let's see if this one brings new improvements...