Heroic Games Launcher supports GoG pretty well. You can install it with Flatpak using Discover in desktop mode.
When you login to GoG and install a game, you will be able to “Add it to Steam” (top-right hamburger menu in game’s view) and it should then be available in your “Non-steam games” in gaming mode.
Other options are Bottles and Lutris
Oh, the article is written by Jason Evanghelo. Of course, he’s a giant Linux shill working at Forbes :D
Still great to see such press
Do other games run in general when using Vulkan API? (most modern games on Linux run with Vulkan, whether it’s Wine or native).
What’s your NVIDIA driver version? Did you even install akmod-nvidia?
Why would display protocol matter here? Makes no sense to me.
How do I even test the game if it won’t work on any of my Linux machines? Anyway, after reading this, I am fully ready to forget it ever existed.
I updated quite some time age and it was completely painless, why wasting time reinstalling?
It’s only bad when used incorrectly. Just store time in UTC and convert it to timezone of your setting to present it. Most modern languages offer a library that makes it just one more line of code. Not only it’s then clear and unambiguous, it supports all timezones.
The HDMI/DP was my wild guess. For now the problem should also go away if you just change in-game resolution for whatever is your screen. Maybe the problem isn’t being addressed because it was reported to Mesa user-space driver, but maybe the problem is in kernel module. It’s also not 100% always reproducible.
I know this issue. It’s reproducible when
The problem has long been reported in Mesa project, but nothing was done to help. My bet is that the bug sits in amdgpu kernel driver and not user space.
https://gitlab.freedesktop.org/mesa/mesa/-/issues/8705
EDIT: maybe it’s worth to report in kernel bugzilla or wherever amdgpu kernel driver bugs would go. I don’t reproduce this on my end anymore, because I changed my screen and it uses DP
EDIT2: I could only reproduce it on RDNA2 and yours is RDNA3. I had Polaris (RX 570) for quite some time and it was running on Wayland. Maybe it only happens on newer cards, maybe it’s regression added along the way
The problem will only get solved if there will be reliable methods for detecting cheats that don’t require direct ingeration in a client operating system directly.
Linux is ‘a terrifically hard audience to serve’
said owner of a company that last tried to oficially support Linux in late '90s.
I like how you accidentally (edit: or maybe not) donated Wine devs by buying CrossOver license :D
There were some recent fixes to Steam VR but I have never tried a VR headset myself. It should work on Wayland with a compositor that supports DRM-leasing protocol, so basically everything but GNOME.
Azure stuff (like az CLI tool) is generally available on Linux, I used it to provision services using Terraform. Things like .NET or MSSQL all have official support on Linux now.
That’s the way. Nothing improves the experience on Linux as much as a bit of learning curve. You may go with easy few clicks setup distro and then once you stumble upon any issue you’re clueless. Besides, Arch is much easier to understand than something like Ubuntu.
I’ve got pretty similar thoughts. I wasn’t into gaming all that much up until relatively recently when I built my first gaming PC at the beginning of pandemic. Thanks to that, I’m not only on market for bleeding edge AAA titles, but also discovering 3 dacades worth of PC games. My observation is that games got worse over time. They’re also a lot more expensive to make because it all must be visually impressive, which usually ends up with poor performance and bugs, requiring high-end hardware for the game to run somehow. Quite often games are broken and unoptimized on launch, they have that generic formula, watch cinematic, hold a button, watch some more, here’s your little tutorial fight, now more cutscene and a crappy puzzle. It really makes me feel, if game developers were more limited by hardware constraint and unable to feed legions of normie players to flashy graphics, they wouldn’t have other way to makes games attractive other than with better mechanics and level design.
Meanwhile Nintendo continues to release bangers for their ancient potato console.
ok then, salad more for me please
PopOS is currently using modified GNOME on Xorg. It’s impossible to get mixed refresh rates on Xorg/X11 (which is the legacy display protocol) and with your setup you are pretty much stuck with Wayland (the modern display protocol still, still progressing as a platform) - which is what you tried first if you used Nobara, whether it’s KDE or GNOME.
Note that PopOS 24.04 (that will be released this fall iirc) will in fact run on Wayland with all new Cosmic desktop (it’s first full DE written from scratch since like 90s) and promises great NVIDIA support - which can definitely be the case given recent updates.
Now on the flickering issues that you experienced, they’re specific to the NVIDIA driver and are just being ironed out. There is the new explicit sync Wayland protocol, new NVIDIA driver, patches for XWayland, patches for Mesa, maybe something more. It still might require pulling something that didn’t make it to stable distro repositories, but I think Nobara provides that and for sure will when 40 will get released soon-ish. I don’t have NVIDIA GPU, but I saw conversations on Nobara Discord and they help each other get NVIDIA going so maybe ask there.
The time frame is a bit of a problem here. If you want to avoid tinkering, hold for a little longer and in few months most distros (that ship a Wayland session) will most likely just work with your setup. If you want it now, feel free to get your hands dirty and find a way to run NVIDIA on Wayland with explicit sync support.
That’s the English language in a nutshell from my perspective as non-native