Thanks for joining the Graphics community.
We are still investigating the issue and should have test results soon, I will report back once I have more information from our engineering department.
CMAA in control panel doesn't automatically enable/disable with app launch.
See the release notes, specifically the part that talks about CMAA
The way the CMAA feature works is as follows:
1) An application is launched and creates a DirectX context - could be a game or could be an office application.
2) graphics driver is loaded to perform hardware accelerated rendering. At the time the driver is loaded it reads a Windows registry key to determine whether CMAA override is enabled. If so, the driver will use CMAA until the application is closed; if not, the application will not use CMAA.
As a result, the surest way to have CMAA only affect the apps you intend (e.g. games), The recommendation in the release notes is for user to manually turn CMAA on in control panel before launching a game where you want to use the CMAA feature and then disable manually in the control panel after the game is launched (or after you exit the game) and before launching other apps.
To avoid accidental blurring, the driver has a list of applications that will not use CMAA even if it is left enabled - that list includes Internet Explorer, Chrome, Firefox, the OS home screen, etc; however that list does not include Microsoft Office apps.
CMAA helps, but it would be too much of a hazzle to go manually turn CMAA on everytime before playing a game.
Right now i am using a workaround to turn off hardware graphics acceleration in Office 2013. This works but of course a real fix would be nice, since CMAA is an otherwise very nice feature.
It seems with the latest driver 10.18.14.4156 the problem is finally gone.
Glad to hear that, and thank you for sharing this information.