obs-vkcapture trips VAC protection on Steam Client Beta

[Loomeh]

I upgraded to the Steam Client Beta and tried launching CS:GO (A Valve Anti-Cheat protected game). When trying to join a match, I get an error message from VAC Removing obs-vkcapture %command% from the launch options fixes this.

Neofetch output if it provides any use to you somehow

[nowrep]

Try OBS_VKCAPTURE=1 %command% -vulkan

[Loomeh]

@nowrep that's what i was already using.

[nowrep]

You wrote

Removing obs-vkcapture %command% from the launch options fixes this.

which is not the same thing.

[Loomeh]

@nowrep my other launch options are -novid -high -vulkan.

Why would I use vkcapture if I wasn't using Vulkan?

[nowrep]

obs-gamecapture command will also preload GL capture library, which I wouldn't be surprised to trigger anti-cheat. Do you still get the VAC error with OBS_VKCAPTURE=1 %command% -novid -high -vulkan?

[Loomeh]

@nowrep Yeah.

[nowrep]

Does mangohud work? MANGOHUD=1 %command% -novid -high -vulkan If yes, then you can report this to Valve as there is nothing for me to do.

[sekhat]

I tried to replicate this on my machine but have been unable to do so. Using both obs-vkcapture and OBS_VKCAPTURE=1 methods and I am able to matchmake fine .

Also Arch linux, using latest AUR git package obs-vkcapture-git.

Though I'm using an NVidia Card.

Either VAC has been updated such that this obs-vkcapture wouldn't cause it to trigger, or something else happens to trigger it in conjunction with obs-vkcapture. I'd be curious to see if other AMD users get this issue? Maybe it's something to do with what the vulkan loaders for Mesa vs Nvidia behave?

[nowrep]

I think I can close this. Even if it actually triggered VAC there's nothing for me to do about it really.

If you still have this issue, please report it to Valve.