[yummypaint]

To be fair this is adobe's fault. The only reason it isn't available on linux is because adobe goes to great technical and legal lengths to ensure it can't be. A VM with seamless windowing isn't a bad solution for running that kind of forcewear, compromising the whole host OS seems excessive.

[OO000oo]

Blaming doesn't fix anything. The real point here is that it's a political issue and the open source community is too infantile for politics so they keep lying to themselves instead.

[heyoni]

I wonder if it would work under a vfio system.

[bravetraveler]

Almost surely! Outside of seeing obvious signs like VirtIO devices, one can go to great lengths to hide the virtualization

Similar tricks that work for the ESEA Anti Cheat client and Nvidia code 43 will likely suffice

VFIO takes this a step further and provides one less virtualized device

[heyoni]

I really want to try VFIO and ditch my windows install completely but I'm worried about anti cheats. Nice to hear there are steps you can take...

You have experience with this? If so, just wondering...are there linux distributions to avoid for VFIO? I'm between arch and NixOS, nothing too outside of the mainstream.

[bravetraveler]

It's definitely worth a whirl! Some anti-cheats are more effective at catching this than others.

I was using this as my method of 'Gaming on Linux' until Proton became a thing.

Lots of experience, indeed, though my memory hasn't aged particularly well. I even had SLi working with two RTX2080s! Hacked drivers and EFIGuard to bypass security things

Valorant was the one game I couldn't really manage.

Perhaps with more determination, but I lost interest rather quickly. Not that into the game and Proton really hurt my VFIO involvement; the timing was unfortunate.

There are some rote edits to the libvirt XML I can't recall. Both to get the nvidia driver to work (if applicable, look for 'code 43'), and to hide the VM state for anti-cheats.

You'll generally be well served by your distribution of choice with modern kernels and QEMU/libvirt.

I don't know Nix well, but from what I gather, you get to pick a lot... so it shouldn't be a problem. Arch is Arch, it'll be fine being so new!

[heyoni]

> Lots of experience, indeed, though my memory hasn't aged particularly well.

That's kind of hilarious because my aging thing is manifesting itself in making me unable to play more complicated games. Like, I wish I could get into dwarf fortress or the new baldur's gate but always feel fried and opt for a round of call of duty (and now diablo 4). Those games are require 0 reading, it's all instinct and nothing in the game happens without some audio-visual feedback...

The irony here is that I might take a deep dive into VFIO because call of duty is one of those games that will never work with Proton...I guess for you that was Valorant?

These must all be the side effect of having kernel level anti cheat programs running on Windows and very dedicated anti-cheating teams.

> I don't know Nix well, but from what I gather, you get to pick a lot... so it shouldn't be a problem. Arch is Arch, it'll be fine being so new!

I have a habit of setting up linux machines and forgetting the process. I'm hoping NixOS will help with that :D

[bravetraveler]

Don't worry, you're not alone! I have the same 'aging problem'

Though... I suspect it's a compound issue. Work is draining! Mindless fun is all I can handle, too :D

Kernel level anti-cheat is indeed the bane of Proton. Fortunately, VFIO can help there - giving a full trusty Windows kernel.

I long for a future where 'we' collectively reject these. I believe there are less-technically-invasive methods for dealing with cheaters than... essentially writing a driver and creating attack surface area.

NixOS should indeed - forcing you to write things down as you go!

I'm partial to Ansible for this, personally. You can automate quite a lot with it - there's a very healthy ecosystem of modules for almost anything you could imagine

If written well, it will work on any distribution. It's a fun challenge/art

[the_lego]

> adobe goes to great technical and legal lengths to ensure it can't be

Could you elaborate? It was my impression they simply didn't care, but I never looked into it.