On Tue, 2004-01-13 at 14:51, Felix KÃhling wrote:
On Tue, 13 Jan 2004 14:38:37 +0100 Michel DÃnzer <[EMAIL PROTECTED]> wrote:
On Mon, 2004-01-12 at 17:44, Michel DÃnzer wrote:
There are still minor problems, e.g. in the xscreensaver endgame hack, but those might be related to colour material (known to horribly break trackballs, e.g.).
The funny thing about the problem in endgame is that it's much less severe if run as
R200_DEBUG=state /usr/lib/xscreensaver/endgame 2>/dev/null
as opposed to just
/usr/lib/xscreensaver/endgame
A timing problem?
Apparently...
Sure this is about timing?
What I see in endgame is this:
Every few seconds, the colors change from orange/brown to orange-brown/grey. Compared to R200_NO_TCL (or software mesa) both of these color sets are wrong (should be orange/grey if mesa is correct).
Apart from that, I couldn't see other errors (with a 9000pro).
Maybe not all necessary state is submitted?
Roland
------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
