| 15 Oct 2023 |
 @woobilicious:matrix.org | Oh nice. I don't know what FCP is, but maybe something else related, Gsync or something causing issues? | 17:33:17 |
 @Lownin:matrix.org | woobilicious: on Nvidia, there is often screen tearing on Linux even with vsync on. Probably some driver issue, super annoying.
On the NixOS Nvidia page, https://nixos.wiki/wiki/Nvidia under "Screen Tearing Issues" you'll see where you can mitigate it by enabling an option "Force Full Composition Pipeline"
In my experience, this works pretty well, but it has some side effects; the worst for me is it introduces some input latency, but it's tolerable.
I recently started experiencing an issue where if I enabled force full composition pipeline, games would lock up right after they started. Gsync is enabled and disabled for me separately, and only available when using DisplayPort, but even disabled, I had the problem.
I've been trying to solve this all weekend and listening to you mention DisplayPort, and knowing the composition pipeline affects sync, and thinking about how I re-arranged my monitors somewhat recently and I guess decided to use different cables (a vague memory so wasn't thinking about it before) I decided to try it. HDMI only, no display port, and it worked.
| 17:39:02 |
| @woobilicious:matrix.org | Do you even need that with wayland? that looks like a hack for X compositors (after googling around). Lownin does enabling Vsync not work? I have no perceptable latency with sway+vsync+180hz. | 17:46:42 |
| @woobilicious:matrix.org | here's my 5head patch: https://gist.github.com/YellowOnion/eed6071d1b4226ba54be787ad1b81b31 | 17:50:12 |
| @Lownin:matrix.org | woobilicious: Enabling vsync by itself smooths out the framerate, and gives me a nice, consistent tear line right on my screen. Same problem regartdless of if I have KDE's compositor enabled or disabled. Googling around shows a lot of people still have the issue with Wayland. I tried Wayland briefly, but had to switch to lightdm because it failed to start with sddm. Not a big deal, but I'm also on NixOS 23.05, not unstable, and my understand a lot of work is going into Wayland support right now so I figured I'd give it a go on the next stable release. | 17:50:45 |
| @woobilicious:matrix.org | Lownin: ahh that sucks :-( tearing is so much better when your game is doing 300fps and not anywhere close to vsync. | 17:53:15 |
| @Lownin:matrix.org | woobilicious: I think that's only true on a high refresh monitor? Mine are all 60hz, so you always see the tear line and microstutters introduced by the lack of sync. | 17:56:07 |
| @woobilicious:matrix.org | Lownin: at 300fps the difference per-frame is small, and if the tear line moves unpredictably up and down the screen it's hard to see, Source games tend to be better for this, but if you have like a game with a frame-rate cap close to vsync the line becomes more noticable, I only just upgraded to >60hz this year so I know all the tricks because I hate input latency lol. | 18:04:11 |
| @Lownin:matrix.org | I was actually just experimenting with Portal 2 since I was trying to rule out native vs proton games locking up. I was running at and around 300 fps, and i could still see lots of microstutters and some tearing.
I guess in theory the tearing should be less noticeable since at such a high frame rate, the difference between frames is more minimal. Couple things might be exacerbating them for me though. The microstuttes, and being on ultrawide so a big horizontal plane difference is a bit extra for me. | 18:12:18 |
| @woobilicious:matrix.org | Lownin: does wayland itself tear like when you're in windowed mode?, disabling scanout in sway fixed a VFR bug for me, maybe that'll work for tearing as well. | 18:14:37 |
| @Lownin:matrix.org | I sort of bounced off wayland before I really tested it. Nix make it easy to try it out though. My old config is just commented out. I could take another swing at it really quick if you like. | 18:15:30 |
|  Eva (backup) changed their profile picture. | 18:24:07 |
| @Lownin:matrix.org | Redacted or Malformed Event | 18:24:13 |
| Eva (backup) changed their profile picture. | 18:24:15 |
| Eva (backup) changed their profile picture. | 18:24:56 |
| Eva (backup) changed their profile picture. | 18:25:03 |
| Eva (backup) changed their profile picture. | 18:25:10 |
| @Lownin:matrix.org | woobilicious: still getting tearing in Wayland. Also, Element and discord are just black windows. I am having to use my phone. It feels faster though! | 18:29:09 |
| Eva (backup) set a profile picture. | 18:31:39 |
| @woobilicious:matrix.org | Lownin: damn :-( oh well. | 18:38:11 |
| @Lownin:matrix.org | Lots of folks reporting it here as well - https://forums.developer.nvidia.com/t/535-54-03-screen-tearing-while-gaming-on-wayland-session/257065/14 | 18:44:38 |
| Eva (backup) changed their profile picture. | 18:46:46 |
 K900 | "Screen tearing on Wayland" feels like an extremely Nvidia issue to have | 18:49:15 |
| Eva (backup) changed their profile picture. | 18:49:28 |
| Eva (backup) changed their profile picture. | 18:50:18 |
| @Lownin:matrix.org | Well, shit. I went back to X11 and now the problem with games locking up when using Force Full Frame Composition is back :( | 18:54:42 |
| Eva (backup) removed their profile picture. | 18:58:08 |
| Eva (backup) changed their profile picture. | 19:00:41 |
| @Lownin:matrix.org | Seems to be solved with a backdated driver. | 19:05:37 |
| @Lownin:matrix.org | Took me a bit to figure out how to do that. | 19:07:18 |
