If that is the case then fair enough. I only refered to that driver issue because I thought, (mistakenly maybe), that is what the poster was refering to.
If however, as you state,(and the other poster meant), this is a different application specific fault with the driver that the developer is already aware of then I'm sorry to have raised it again.
I'm not trying to pick fault. I was only trying to be helpful by relating what I believed to be a fault.
By the way, I can't install 174.xx WHQL version as it fails saying no compatible hardware found. I have however tried the beta version of the same driver and with this driver AA seems to be being applied to everything. Including LFS when I set the AA to "none". So it would appear to me that this beta driver is also buggy and therefore of no help to me.
So, I've gone back to what are officially the latest available WHQL certified drivers for my particular hardware (169.25).