• 0 Posts
  • 1.25K Comments
Joined 3 年前
cake
Cake day: 2023年6月12日

help-circle







  • Yeah, I’m using them as an example of an underwhelming product that nevertheless has a market at its price, which millions of people regularly purchase knowing how shit it is because the price is tolerable for a guilty pleasure.

    Measuring the time in percentages here doesn’t make sense. A 1 hour difference on a 3 hour game can easily be chalked up to variance (even the estimate of 3-4 hours has a 1 hour range) but 10 hours off a 30 hour game is enormous. If we also made it $50 instead of $5 and argued for time per dollar as a value metric, sure, those would be equally misleading, but time per dollar is less important as the total cost decreases. Nobody would say a 2 cent movie ticket is half as worthwhile as a 1 cent ticket. They’re both approximately as valuable as the experience itself because the cost is negligible.





    • update your system

    • delete your game’s wineprefix, it’ll regenerate and may fix issues from changing versions

    • lutris is not likely the issue unless you’re using its runtime and something is clashing with it. With proton-cachyos-slr, you should have lutris runtime disabled and prefer system libraries enabled. See here: https://wiki.cachyos.org/configuration/gaming/

    • wild guess, but new versions of proton-cachyos use ntsync by default which requires a kernel module that may not exist in your older system. I’m not sure if it falls back to fsync in this case, but that could cause issues. System update fixes this.

    • if you’re on wayland and using PROTON_USE_WAYLAND, the change to proton 11 may have broken some games. These typically would be crashes / white screens rather than lag. In this case you can disable PROTON_USE_WAYLAND or use the older proton 10 based version of proton



  • Using aur helpers is fine if they make it easy to read the pkgbuild, which paru does. It’s too annoying to check for PKGBUILD and upstream/vcs updates for each package individually.

    Ideally the aur helper would point out when 1) a package changed maintainers since your last install, 2) a package’s PKGBUILD itself changed (not just the upstream/vcs source), 3) the PKGBUILD is less than 24h old or so. And for #2, it should also show you the changes similar to what you see on the AUR site’s “view changes” page. I’m not aware of any aur helper that does these things, but hopefully recent events prompt a change.