Sorry in advance if this is the wrong place to ask.

Hello, everyone. I’ve recently gotten back into NixOS and immediately noticed that NVIDIA is buggy. (no surprise there) I’ve searched far and wide and it seems that no one else has these bugs? (I am most likely wrong though) I’ve gone mad trying to fix these two.

Here’s some extra info:

This is not distro exclusive, i’ve tried on fresh installs too.

I am using 565 with an RTX 3060 gpu.

I am on wayland/hyprland.

Curiously enough, this doesn’t happen on native games such as Metro 2033 or HOI4, only on proton.

apologies for the shitty gameplay and recording, and thanks.

  • Fushuan [he/him]@lemm.ee
    link
    fedilink
    English
    arrow-up
    3
    ·
    22 hours ago

    I had that issue before the explicit sync was implemented in the nvidia driver for Wayland. It’s got to be related to that.

    Out of order frameworks a is literally a frame syncronization error.

    • fxomt@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      22 hours ago

      Weirdly enough I am on explicit sync. I tried on Plasma and this didn’t happen, still had its own problems. X11 was literally flawless though? Weird…

      • Fushuan [he/him]@lemm.ee
        link
        fedilink
        English
        arrow-up
        4
        ·
        22 hours ago

        The way x11 handles frames makes this a Wayland exclusive issue sadly. I’m on plasma so that might be why my issues was fixed. Weird indeed. Good luck in any case, these kind of issues are annoying as hell.

  • セリャスト@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    2
    ·
    22 hours ago

    Hey! I tried fixing this problem for years on a laptop using and AMD CPU and Nvidia GTX 1650 because it made Trackmania unplayable at my level of competition. Never managed to fix it, I just changed PC in the end.

    • fxomt@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      22 hours ago

      The struggle is real 😞

      What GPU do you use now? AMD or NVIDIA?

      • セリャスト@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        22 hours ago

        Amd on desktop, amd on laptop iGPU, and amd on steam deck. Never encountered this kind of weird stutter backtrack agaim. Funniest thing, it would even happen to software like Firefox if I made em run on the gpu

  • fxomt@lemm.eeOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 day ago

    Well, i’m fucked. I think i’m going to have to return to windows.

    I’ve learned my lesson, NEVER buy nvidia.

    thanks for all the help everyone, and happy holidays :)

    • Zoot@reddthat.com
      link
      fedilink
      English
      arrow-up
      3
      ·
      24 hours ago

      Sorry for you troubles, but curious, what game is this? The map is obviously from GMod but nothing else looks like Gmod

  • RedWeasel@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    2 days ago

    Does hyprland support explicit sync at all? That sounds like the explicit sync issue that was fixed earlier this year.

    Edit: Could run waycheck and see if linux-drm-syncobj-v1 (explict sync) is listed. I looked for NixOS and it “should” be supported, but best to double check.

    • fxomt@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 day ago

      Yup, explicit sync is implemented on Hyprland, i tried waycheck.

    • fxomt@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 days ago

      lmao yeah, you get used to it eventually. I can’t play on 90 FOV anymore, it seems small now 😅

  • Malix@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    2 days ago

    try disabling the gsp, helped a lot with weird stutters on my system (kde/plasma, wayland, 3090, 565 driver).

    IIRC it was just setting NVreg_EnableGpuFirmware=0 to nvidia module

    edit: only works for the regular nvidia driver, not for nvidia-open

    • fxomt@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 days ago

      I disabled it, but nothing changed (i used regular NVIDIA and made sure it was disabled, too), but thank you

      • Malix@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 days ago

        probably asking the obvious, but you did the … whatever mkinitcpio does, after changing the module’s config? Totally derped with that myself and wondered why my new settings didn’t take x)

        • fxomt@lemm.eeOP
          link
          fedilink
          English
          arrow-up
          2
          ·
          2 days ago

          I use nixos and it doesn’t use mkinitcpio. Rebuid, reboot, and it works. I also made sure I disabled the GSP using nvidia-smi, so I’m sure that it isn’t the problem.

    • fxomt@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 day ago

      Well fuck me, X11 doesn’t have this issue at all. but i use wayland because X11 has its own set of bugs that causes me headaches. It’s a lose-lose for me.

      • entropicdrift@lemmy.sdf.org
        link
        fedilink
        English
        arrow-up
        2
        ·
        14 hours ago

        Nvidia kinda sucks on Linux because of the poor Wayland support and slow turnaround time on Wayland bug fixes, sadly

  • boegy@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    4
    ·
    2 days ago

    I had this happen on Fedora with amd cards as well. At the time I was using riverwm which is based on wlroots. I tried a few other WMs that also used wlroots and had the same problem, so I think the issue is somehow related to wlroots but I don’t know enough about it to be sure.

    When I tried on KDE Plasma (Kwin) I had no issue. So you may want to try Plasma or Gnome and see if the issue persists.

    • fxomt@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 days ago

      Tried plasma, the bug was “fixed”, but the performance was horrid.

      fyi, hyprland isn’t wlroots anymore, its standalone :)

      • boegy@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 days ago

        ok, I haven’t used hyprland so I wasn’t sure. The wayland tiling WMs I tried all had the same problem so I don’t know what the underlying cause is. I personally don’t have performance issues on wayland plasma and I don’t have an nvidia card in a linux system so I can’t test it further. I hope you are able to figure it out.

  • morbidcactus@lemmy.ca
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    2 days ago

    I’ve got a 4070ti running most recent nvidia-open on arch and haven’t had that happen, but I don’t tend to run with vsync often.

    What proton version are you running this on? Had some weird almost microstutters in cutscenes playing DA:Veilguard through moonlight on my steamdeck. Swapping to experimental resolved that, think it was one version of proton-ge that I had the issue with.

    Do you have vrr enabled by any chance?

    Are you running through gamescope? Have had grief with gamescope and nvidia, but that was mostly with hdr.

    • fxomt@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      1 day ago

      Many old games have vsync enabled by default :/ happens with all proton versions (I use ge), don’t use vrr or gamescope, but I’ll try on experimental again JIC if I was wrong (god I hope, lol) thanks for the tip.

      edit: experimental didn’t work either :(