On Friday 03 April 2009 20:48:47 Clive Messer wrote:
On Friday 03 Apr 2009 18:05:01 Eli Wapniarski wrote:
> There are other problems right now with the 180.44 driver.
>
> See post
http://www.nvnews.net/vbulletin/showthread.php?t=130219
This problem is specific to S3TC under wine? I don't run games under wine, just
console apps! ;-) Of course, I should have a 'YMMV' in my first post or not
posted at all. The later, with hindsight.
Please bear with me... There is a point at the end of all this.
Actually if you read the post to the end the problem was resolved by wine. There is
currently a patch that I have applied to wine 1.1.18. Bug report at fedora posted at
https://bugzilla.redhat.com/show_bug.cgi?id=489144
There is are attachment a couple of attachements in the above mentioned bug report that
includes a working spec file and the patch. Please note that wine, for some reason can
only be built under mock. I tried to compile it in a i386 machine with no luck. And as you
can see from the bug report. The packager hasn't bothered to respond at all.
With the original bug report over at
http://bugs.winehq.org/show_bug.cgi?id=12560
Under 180.44 there is some kind of rendering issue that has nothing to do with S3TC. It
looks like something wrong with OpenGL under some conditions. Which means that if you are
using compiz or desktop effects, you could run into some trouble under some circumstances
despite what NVidia reports as things being fixed for KDE. While something might be fixed.
It certainly has broken something else. And plasma seems to work just fine under 180.29.
At least for me. At least for now.
So again. If it were me (and its not) :) Currently I would stick with 180.29 unless
something really compelling came up.
Eli
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.