Linked by lopisaur on Fri 25th Jun 2010 22:21 UTC
Thread beginning with comment 431907
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2006-01-02
Xlib only uses XCB essentially as a transport layer. It still has the same bad implementation on top of that.
I think you need to check your driver configuration or talk to some X.org devs because unless you have a really crappy gfx card (and it sounds like you don't), you shouldn't be seeing those issues. I have a T500 with a Radeon 3650 in it and it is quite snappy and I don't see artifacts or tearing. Compositing is also quite usable, which will significantly reduce flickering (just like in Windows Vista/7).