You are not logged in.
Pages: 1
Hey guys
Ive done alot of research and checked alot of forums for this. but i cant get a straight answer i guess most dont even reply, so i thought id come right to the XFCE core basically due to this error, compiz is the only effects manager i can use that has sync to vblank and doesnt tear the screen
( i know its weird, but some reason i despise compiz!! i dont want to use it )
Xfce Version: 4.8
Your Distribution and Version: Xubuntu 11.04 and Archlinux with XFCE 4.8 = occurs in both
Ok basically compositing. when i have the XFCE4 XFWM Compositing options enabled. i recieve heavy screen tearing in every game i play and movie
My Graphics Specs
Gefore GTX 460 1GB
NVIDIA version 280.13 Drivers
Latest Kernel with Xubuntu 11.04
Now when i use compiz. and enabled compositing with Sync to Vblank in opengl and Detect Refresh rate, i dont recieve any tearing and everything runs fine, accept for when exiting a full screen window. it crashs the desktop - known Compiz bug
Now im wondering, is there any fix for XFCE. or is there anyway to get the XFCE4 compositing manager to Sync to VBlank like compiz does, and use opengl/detecting refresh rates
I might also add that the XFCE display manager was not reading my refresh rates properly, disabling the TwinMonitor Option in my Xorg.conf fixed this issue, but i am not sure if that will effect the compositing manager , whether they work together or not
Anyway. I would like to add that beyond this little issue, which is a well known one and happens with nvidia and almost any compositing WM, so its not XFCE's fault. it would just be nice if u guys could add Sync to Vblank options and refresh rate like Compiz does
Id just like to add and thank the XFCE developers beyond this issue, XFCE is the best piece of desktop software ive used in linux ever, especially 4.8 it has made unity and gnome obsolete to me and im very pleased with it even without compositing and with docky
I really hope somehow this problem gets fixed, hopefully nvidia fix there side
Last edited by nankura (2011-08-05 09:01:48)
Offline
I also get tearing in videos when the compositor is enabled with the xf86-video-intel driver.
This is a known bug: https://bugzilla.xfce.org/buglist.cgi?q … ch=tearing
But it looks like the current developpers aren't experiencing it...
Offline
what bugs me the most is that its a known bug, its common, to common to the point that every distro has one or two reports of this bug with nvidia. all over the forums, bugzilla's everywhere have reports of it
And nobody, especially nvidia has done anything about it, though.from what ive seen with XFCE, i do have faith they will get something done. but its ridicilious that this bug has been around since ubuntu 10.04 and the 200 series nvidia drivers and nothing has been done for it
Offline
small report, i found this reported multiple times in KWin AND XFWM - seems to be a vsync issue with nvidia drivers and Nouveau
https://bugzilla.xfce.org/show_bug.cgi?id=7237
http://web.archiveorange.com/archive/v/ … zE1lhXnOLl
Last edited by nankura (2011-08-06 01:04:07)
Offline
i noticed this little workaround for compiz and ubuntu 11.04
http://www.shareconnector.com/ubuntu-11 … workaround
is there anyway for those commands to apply to XFWM4
Offline
just to update again, i found this
http://www.phoronix.com/scan.php?page=n … &px=ODcwMw
http://www.phoronix.com/scan.php?page=n … &px=NzY1Ng
http://dri.freedesktop.org/wiki/CompositeSwap
http://phoronix.com/forums/showthread.p … post153218
i am aware to most of this seems like old news, but im curious if this can be applied to the new kernels and if this could be a fix, because the problems still exsistant
But i dont understand what there saying, there talking about kernel .33 and were on .38 these days or 3.0. so im not seeing these improvements, or maybe i missed something but theres no clear instructions on applying these fix's to XFCE/nvidia drivers or other WM's , seems native in mutter
Last edited by nankura (2011-08-06 04:58:49)
Offline
Pages: 1
[ Generated in 0.013 seconds, 7 queries executed - Memory usage: 539.84 KiB (Peak: 541.13 KiB) ]