Tagged: compositing
- This topic has 8 replies, 4 voices, and was last updated Jul 27-4:25 pm by fab161.
-
AuthorPosts
-
May 10, 2022 at 3:52 pm #82967Member
fab161
Hello there,
I’m using antiX (runit) on a more powerfull machine (8GB RAM; 4 cores) because I really like small window managers like IceWM and the configuration the antiX devs apply to it. Sadly, I do have screen tearing issues by default e.g. when moving windows around, so I’m currently using picom as a independant compositing manager with the glx backend and vsync option enabled — this solves the screen tearing problem. However, IceWM (and other window managers/desktop environments too) feels way less snappy because of it. So I’d like to ask you guys if you may know a lightweight compositing manager for window managers. For example there are the compositing options of Xfce working great but those are very much connected to the Xfce environment..
Thanks,
FabianMay 10, 2022 at 5:10 pm #82969Moderator
caprea
::Hi Fabian, if really screentearing is the only reason for you installing a compositor, it can perhaps also be solved in another way.
There are solutions here on the forum for intel and nvidia chips.
Please post
inxi -GxxxMay 10, 2022 at 5:47 pm #82975MemberPPC
::Compton or picom (for antiX 19 or 21) – they are pretty light. If you install ft10-transformation pack, it includes a pre configured menu entry to start compton/picom with some nice default settings.
Edit: I run a fluxbox with ft10 toolbar/menu enabled and even with compton visual effects on, my way less powerful desktop than yours is incredibly snappy… I found no slow down when I run icewm…
P.
- This reply was modified 12 months ago by PPC.
May 10, 2022 at 6:58 pm #82982Member
iznit
May 11, 2022 at 8:07 am #83019Memberfab161
::Thanks for your replies. Currently xcompmgr seems to do the stuff i want to — further i disabled showing the window itself in icewm while moving and this is pretty neat for now. Previously i tried compton and picom; to be honest i can’t see much difference especially when they are using the same backend (glx). But there is one thing i noticed: in the icewm session with rox it draws shadows as it should (same thing in icewm sessions without desktop icons) but when i use zzzfm it seems like its blocking the shadows. Kinda weird.
May 11, 2022 at 8:10 am #83020Memberfab161
::@PPC icewm still runs as fast as it could i think, just the moving of windows feels like beeing slowed down by the glx backend.. the xrender backend doesnt do that.
May 11, 2022 at 9:18 am #83022Memberfab161
::@caprea
Graphics: Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Hewlett-Packard driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:1916 class-ID: 0300 Device-2: Cheng Uei Precision Industry (Foxlink) HP HD Camera type: USB driver: uvcvideo bus-ID: 1-9:5 chip-ID: 05c8:0383 class-ID: 0e02 Display: x11 server: X.Org 1.20.11 compositor: xcompmgr driver: loaded: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz s-dpi: 96 OpenGL: renderer: Mesa Intel HD Graphics 520 (SKL GT2) v: 4.6 Mesa 20.3.5 direct render: YesMay 11, 2022 at 10:57 am #83023Moderator
caprea
::You can try this “Force the intel driver over the default modesetting”
https://mxlinux.org/wiki/hardware/intel-video-driver/Your card is a bit more modern like mine. I use the intel driver for an Intel 4th gen, it saves me from screen tearing, which was really nasty with the modesetting driver.No compositor needed.
July 27, 2022 at 4:25 pm #86605Memberfab161
::@caprea thank you, exactly what I was looking for. By myself, I thought it would just be possible to fix this with a compositing manager. Default settings seem to be weird sometimes. 😉
-
AuthorPosts
- You must be logged in to reply to this topic.