Originally Posted by netllama
This bug is currently under active investigation by development, however, it will not be resolved in the next driver release.
When will it be resolved? Do you have a time frame set out for this issue? Can you assure me that this issue is being investigated seriously, and that you're not simply casting it aside?