Re:Ask HN: Those who run mainly Linux and game on Windows, w...
by 1_1xdev1 on Sunday July 14, 2024 @06:10PM
(#40963570)
I assume no based on your comment, but have you ever run into issues where your vfio setup didn’t work with AAA games with intense anti cheat? Like cs:go/cs2 or valorant? That’s what’s always held me back
Re:Ask HN: Those who run mainly Linux and game on Windows, w...
by DvdGiessen on Monday July 15, 2024 @05:29AM
(#40966380)
I haven't so far. CS:GO and now CS2 run natively on Linux, so never played those online in the VM. I hear Valorant's anticheat is trouble, but I haven't played it (and probably won't for that reason; personally I have so many other games left to play I'd probably just do that instead of having to install Windows on a separate boot drive).
Re:Ask HN: Those who run mainly Linux and game on Windows, w...
by bravetraveler on Thursday July 18, 2024 @05:54AM
(#40994048)
Not all, but many, of these can be avoided with edits to the libvirt XML. Some things just rely on seeing hyper-v extensions. Others use more indicators.
Since you mention CS - I had ESEA working and they're notably difficult to bypass. Valorant was the only game I couldn't figure out that I had tried. Destiny was fine.
Past tense because I've chosen liberty instead - not playing anything with invasive AC, dropping Windows, and running Linux full time
VM running using libvirt and virt-manager, using QEMU underneath, with custom hook script that makes passing through the hardware a bit more seamless.
Although with how awesome Wine/Proton and ecosystem are these days I have so far played almost all my games on Linux. I created the VM setup because I thought I'd need it, but turns out I didn't really. Think I've played through 20-30 games or something like that now with minimal issues on Linux, including big budget AAA games within a few days of their release, smaller indie games, all kinds of different ones. Most tinkering required was for older games that'd need similar tweaks on modern Windows as well.