search

yshui / picom

A lightweight compositor for X11 with animation support
https://picom.app/
Other
4.13k stars 589 forks source link

Picom makes Krita's canvas stutter, but xcompmgr (or no compositor at all) does not #1154

Open Pragmageddon8 opened 10 months ago

Monsterovich commented 10 months ago

Try --no-frame-pacing

Monsterovich commented 10 months ago

@le-dino I suppose you have ForceFullCompositionPipeline and ForceCompositionPipeline options disabled?

absolutelynothelix commented 10 months ago

can't reproduce. the only stuttering that i have is because of frame pacing and it could be fixed either with --no-frame-pacing on the command line or with no-frame-pacing = true; in the configuration file (frame pacing doesn't work well on nvidia gpus now but it should be fixed soon).

Monsterovich commented 10 months ago

@le-dino

no, the tablet runs on 60hz but I have ForceCompositionPipeline enabled because without it, horrible screen tearing is introduced. Just to make sure, I tested with full composition enabled too, but the issue persists.

These settings should be disabled if you are using a compositor, because ForceCompositionPipeline is a compositor, but implemented within the video driver. V-Sync in picom should be enabled to prevent screen tearing.

Monsterovich commented 10 months ago

These settings should be disabled if you are using a compositor, because ForceCompositionPipeline is a compositor, but implemented within the video driver. V-Sync in picom should be enabled to prevent screen tearing.

I understand. Disabled all composition pipelines on all my monitors, vsync = true;. There is still very bad screen tearing, due to this I cannot tell if it's any smoother.

Tested no-frame-pacing = true;, backend = "xr_glx_hybrid";, backend = "xrender";, backend = "glx";; no visible change.

I have an RTX 3060 Ti with V-sync enabled in picom (glx backend) and don't have the issues you have. I just installed Krita via Flatpak and checked it out.

2023-12-22_21-30-43.mkv.zip

Recorded video at 60fps even though I have a 144hz monitor.

It is possible that the problem is in the driver 545.29.06 because I'm using 535.129.03?