Title, I can’t switch to Wayland because of nVidia (and because I love Awesome WM).

  • JoshCodes@programming.dev
    link
    fedilink
    arrow-up
    13
    arrow-down
    1
    ·
    1 year ago

    X11 doesn’t limit it, but you will want to enable “Force composition pipeline” to prevent screen tearing. nvidia and Wayland work together btw. It’s not a match made in heaven but they do work.

    • gianni@lemmy.ca
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      1
      ·
      1 year ago

      It’s simply not worth it. I used Wayland for a couple years but ended up switching back to X11 on nVidia hardware.

    • Pasta Dental@sh.itjust.works
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      It does work, but its just really glitchy and unstable. Idk how many times Ive woke my pc from sleep and my cursor was just a giant square of gibberish pixels. Or the fact that night light still does not work on GNOME + Wayland because the proprietary driver does not support GAMMA_LUT (this issue has been open for years btw)

    • UkaszGra@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      I think forcing pipeline enables vsync or something because there is noticeable input delay when playing on 60hz screen.

  • vd1n
    link
    fedilink
    arrow-up
    6
    ·
    1 year ago

    Why can’t you have Wayland with Nvidia?

    • taaz@biglemmowski.winOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      1 year ago
      1. I love my AwesomeWM setup. Unless someone completely rewrites it, it will never work with Wayland (as far as I have read the gh issues).

      2. I need this PC to “just work” and I have seen a lot of problems with Wayland and Nvidia drivers, top-quality gaming is a secondary on this one so X11 has been the choice.
        Though I am aware stuff is getting better, should probably try it anyway

  • Hubi@feddit.de
    link
    fedilink
    arrow-up
    7
    arrow-down
    2
    ·
    1 year ago

    No. I have a 144Hz monitor and a 60Hz monitor and both work at their maximum frame rate.

  • taaz@biglemmowski.winOP
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    1 year ago

    Thank you everyone, was rather sure that variable refresh rates of different monitors were a hard problem for X11.

    So, in nvidia-settings I made my 120Hz one the primary and set the refresh rate from auto to the highest for both monitors (120, 60)

    The only difference I noticed was that easyeffects window is now completely unreadable, somehow the text and frames bleeds out/blurs and only gets sharp when hovered with mouse but still buggy. Force-compositon-pipeline did not help there.
    Will have to diagnose tomorrow.

  • priapus@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    1 year ago

    No, you can force it to run both monitors at the highest refresh rate, but this can cause tearing on the lower refresh rate monitors. From what I remember, you can choose the monitor to sync to in the Nvidia X settings.

  • lckdscl [they/them]@whiskers.bim.boats
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    1 year ago

    Edit: here’s the relevant commit that addresses this (I think).

    No. I can’t remember what the default behaviour is now. But that isn’t true anymore. Source: I’m currently on X11 and my 144 Hz works next to my 75 Hz one with nvidia.

  • vd1n
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    Are you sure your are running nvidias drivers? Not the generic ones?