Originally posted by biasquez
View Post
looks like Catalyst 9.2beta leaked.
Collapse
X
-
Originally posted by Boerkel View PostYes glxgears = refresh rate :
301 frames in 5.0 seconds = 60.195 FPS
301 frames in 5.0 seconds = 60.066 FPS
I don't think CPU is a problem. I've got a 2x2.0 GHz Turion and CPU-usage is far below 100%. So there must be another reason for this strange "tearing-line". I really don't know why this happens...
The only thing I can think of is to check the output of mplayer to make sure it really is using gl and not falling back to x11 for some reason.
If you are using composite/compiz that will mess things up.
Leave a comment:
-
-
Originally posted by SolidSteel144 View PostCan you guys help me correctly install this driver? I'm new to installing them manually.
On Jaunty...
Leave a comment:
-
-
Can you guys help me correctly install this driver? I'm new to installing them manually.
On Jaunty...
Leave a comment:
-
-
work !
Hello! i installed beta driver on ubuntu hardy its working perfectly. My card is a x800xl.
Lightsmark work and its fast
I followed this guide for the installation and replaced 8.561 with 8.580:
tested also google earth and compiz enabled, there is anyway the hassle of flickering. i really dislike it.
Im going to make further tests with an agp card.
Leave a comment:
-
-
I'm using Gnome and switching Compiz off doesn't solve anything. It's really strange. Perhaps fglrx works fine and my xserver or anything else is broken?
Leave a comment:
-
-
it doesn't tear here. But I am not using broken compiz but kde 4.2 prereleases.
Leave a comment:
-
-
fglrx tears. I though it was common knowledge by now. Vsync. "works" in so far that it keeps frames in sync with your monitor's refresh rate, but images still suffer from tears (whether it be videos or games).
Leave a comment:
-
-
Originally posted by Boerkel View PostYes glxgears = refresh rate :
301 frames in 5.0 seconds = 60.195 FPS
301 frames in 5.0 seconds = 60.066 FPS
I don't think CPU is a problem. I've got a 2x2.0 GHz Turion and CPU-usage is far below 100%. So there must be another reason for this strange "tearing-line". I really don't know why this happens...
Leave a comment:
-
Leave a comment: