Yeah… I finished up the Tom’s article. Nope, I lied… I just gave up on reading it 😌
It just seems like something that could be encapsulated, no? I guess since they call it a hypervisor bypass it sits below the virtualization layer… which is essentially Greek to me. About 1 million years ago, I tried to get solid Works to run in a Windows VM on Lennox and it wouldn’t work. Best I could tell they were using device names that the virtual machine substituted for real hardware… I tried to recompile it and change the names, but I gave up because I didn’t care that much. Since I was using Solidworks pretty much all the time a dedicated machine wasn’t a big deal… as hard as most gamers game, that seems like the route I would go if it were me.
A deadhead gaming box more-or-less isolated… obviously it’s not exactly gaming on Linux, but if you’re playing a game on a windows computer from your Linux desktop… I’d argue that it’s the next best thing.
The Denuvo workaround only runs on Windows and creates the mother of all security holes.
Yeah… I finished up the Tom’s article. Nope, I lied… I just gave up on reading it 😌
It just seems like something that could be encapsulated, no? I guess since they call it a hypervisor bypass it sits below the virtualization layer… which is essentially Greek to me. About 1 million years ago, I tried to get solid Works to run in a Windows VM on Lennox and it wouldn’t work. Best I could tell they were using device names that the virtual machine substituted for real hardware… I tried to recompile it and change the names, but I gave up because I didn’t care that much. Since I was using Solidworks pretty much all the time a dedicated machine wasn’t a big deal… as hard as most gamers game, that seems like the route I would go if it were me.
A deadhead gaming box more-or-less isolated… obviously it’s not exactly gaming on Linux, but if you’re playing a game on a windows computer from your Linux desktop… I’d argue that it’s the next best thing.