Yeah, I turned it on in Catalyst, hopefully I'll see the results in-game. Otherwise, I agree with the enjoyment =D Tomorrow can't come soon enough. I'll just make sure I report the issue when provided the opportunity to do so.
Curious. What's your reasoning? I can think of maybe a performance hit because it's not "native" to the game...I'm interested in your perspective.
However, people who install the game down the road may have varying settings for their cards, so from a beta perspective, isn't it worth it just to try it for the sake of letting devs know what works/doesn't?
It is a good idea to provide data on what works and what doesn't. With that being said, I'll say it again: they disabled it for a reason. A good reason at that. Bypassing it with Catalyst will override that temporary fix while they sort the problem out. I would advise that you leave it on app controlled - at least for STO, and unless the problem is fixed for tomorrow.
This is good for you because you don't experience the issue, and it's good for Cryptic because they won't have to process countless more reports of the same well known issue. They've already spent a hefty amount of resources into squashing it.
But again, it could very well be fixed in the next patch before the servers go live tomorrow.
Yes, it's a straight-out known issue. ATI AA still needs compatibility work with STO. You can force it but it is not reccomended at all and is virtually guaranteed to lead to crashes. Leave AA alone until it's re-enabled in the client.