To be clear this is not asking for support, this is asking to configure EAC to not run it's VM detection at all. EAC can still run the same as it has and the security it provides is not changed. This will remove the Epic VM whitelist/exclusive special sauce for allowed VMs (to my knowledge only GeforceNow), and allow VM users such as ShadowPC and regular end-users to play in a VM without workaround s or custom patches to VM host software or guest software.

This is not new but since EAC has been deployed it has been configured to block execution from within a VM. The current workarounds in the wiki do not presently work as of around the middle of January this year, and even at the time prove that EAC was attempting to block VMs, as it was looking for common VM smbios values to block the execution in conflict with VRChat's previous statements that they do not care if an end-user runs a VM or not.

How it presently is trying to detect a VM I do not know exactly but I can tell that the methods to get VRChat to work solely with VM config tweaks do reduce performance and are windows guest exclusive:

1)Run with the hypervisor CPU extension disabled. (small performance loss)

2)run windows with the hyper-v platform enabled after ensuring the vendor virtualization cpu extension (SVM AMD/ VMX INTEL) is enabled. (massive performance loss)

It is possible to configure EAC to not block VMs, all Fromsoft titles I have (Armored Core, Elden Ring, Nightreign) that include EAC run in a VM fine with no workarounds on both Windows and Linux.

Tupper Promised to read this at a minimum :) (please and thank you)