• TiZ_EX1@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Since the latency of Gamescope’s FPS limiter still seems to be a problem, and we’re still doing a pretty slapdash thing of using MangoHUD’s limiter instead, I went ahead and made a script that makes it just a little cleaner.

    After you save it and update your PATH variable as documented there, you can just use mangolimiter [-f FPS] %command% as the launch command.

    • brunomarquesbr@alien.topB
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      So FYI, the path addition did not work. The folder environments.d wasn’t there, and even after I created, nothing happened, it did not recognize it.

      So I ended up adding the following line to .bashrc directly. Also, “mangolimiter” is quite long to type in Deck’s screen, so I’ve shorten to “fps”. I’ll remove the -f parameter, probably, so in the end is going to be just “fps 40 %command%” , but thanks for it

      export PATH=“/home/deck/.local/bin:$PATH”

      • TiZ_EX1@alien.topB
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        If you created the folder environments.d, then you did it wrong; that directory doesn’t have an s in it. It’s $HOME/.config/environment.d. That will be why it didn’t work. Also, you likely have to at least restart Steam after making a change there, because those configuration files are read at session start.

        • IsaacLightning@alien.topB
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Did i set it up wrong? my game keeps crashing when I try it. I made a mangolimiter folder inside bin, but was that just supposed to be the file itself? also its saved as a .sav that wouldn’t let me execute it no matter what, so I just did the chmod command