• 0 Posts
  • 20 Comments
Joined 3 years ago
cake
Cake day: July 5th, 2023

help-circle

  • i had to double check its

    settings - window management - window behavior - window action - at the bottom you can set mouse wheel to ‘keep above/below’

    what launch options are you using on games? i haven’t had this issue using proton + native wayland launch options. iirc gamescope treats windowed apps differently because its only a container and doesn’t understand the diff between windowed and borderless windowed

    testing in baldurs gate 3, no launch arguments, this works in both borderless windowed and full screen for me without taskbar popping up. though clicking on the window sitting above in fullscreen minimizes and in borderless i have to click back in to regain mouse control. basically the overlay can steal focus, maybe a kwin rule on the overlay to prevent focus stealing might work?






  • the 1000x before bit has quite a few sideffects to it as well.

    • lesser used languages suffer because there’s not enough training data. this gets annoying quickly when it overrides your static tools and suggests nonsense.
    • larger training sets contain more vulnerabilities as most code is pretty terrible and may just be snippets that someone used once and threw away. owasp has a top 10 for a reason. take input validation for example, if I’m working on parsing a string there’s usually context such as is this trusted data or untrusted? if i don’t have that mental model where I’m thinking about the data i might see generated code and think it looks correct but in reality its extremely nefarious.



  • https://wiki.archlinux.org/title/Gamescope

    might go through some of those troubleshooting steps and make sure you have drm kernel modeset.

    one other thing you might try (at end of the page) by setting LD_PRELOAD=”” with the command which can at least rule out features that sometimes break on certain games. I’ve had game recording and overlay cause similar issues and could only launch after disabling those in game settings.

    also might not need gamescope? mesa 25.1+ and proton 10+ have a lot of the features built in and I’ve not noticed much if any performance difference. now i only use gamescope if i run into issues and usually only if protondb shows consensus that you need to use gamescope or specific workarounds.







  • my recommendation if you do is to look at refresh rate, going 120hz to 240hz felt like a much bigger upgrade to me than sdr to hdr. especially if you’re playing games that depend on response times, it just feels smoother. hdr in Linux is decently there on kde but there’s still issues getting it to work everywhere like Firefox, though they still look nicer than regular sdr imo. also avoid hdmi, especially if using amd!



  • nobara is more focused on gaming and includes patches and software to play games without having to tinker a lot. you could use any distro but some games might have performance issues or require additional settings and configuration. nobara gets rid of maintaining that yourself, you might still have to tinker with a few things like launch options but not as in depth as other distros.

    another popular distro is bazzite which does similar things, though i feel that’s a bit more advanced to understand some concepts.

    if your curious about switching i would recommend, if you can, to install a second hdd (can be cheap/small) and try one or both of them for a week to see what it’s like and how well your games run. also if you don’t like how one looks you can also try different desktop implementations. coming from windows, KDE will feel very familiar.



  • given how many targets are supported by llvm there’s really little difference in cross platform support asides from building artifacts for the specific target platform. wrapping package delivery in a package manager removes the additional complexity to the end user.