FACEIT AC its a problem

[zealous gale]

I dont know if it is a common problem or its only because i'm poor, but my pc it's not very recent and does not support secure boot.

With EAC there wasn't any problem, but the new anti cheat requires that in order to do his work, so now i'm unable to play the game.

I realy liked the game and its a shame i can't play it anymore, but i dont know what else to do aside from leaving it on my steam library only taking dust.

[stark crescent]

Please read #bbr-news. The secure boot requirement is being removed, if you still get the error, please uninstall then reinstall your game.

[zealous gale]

Wow, i really dont know why i didnt looked there, thank you

[stark crescent]

No problem.

[proper drum]

Yes, sooo glad the secure boot check will be removed whenever FACEIT AC comes back cause it was a problem for me also, was starting to get worried I wouldn't be able to play on release day

[onyx stirrup]

hey even if faceit was kept the way it was
you could still play on EAC community servers!

[tired field]

Unless its clear how progression will work for only community server players, i dont feel comfortable at all with that as a solution imo (also, still is a problem with Linux despite secure boot change, and also people who want or need to run VMs/docker stuff for work but dont wanna reboot every time they wanna switch between playing or not and dont wanna upgrade/change hardware to run tpm [wasnt this game supposed to be easy for older/lower end PCs to run and all that or smthn?])

[onyx stirrup]

VM/Docker thing is easy to get by actually
Windows 10: either VBS (hyperv) needs to be disabled, or TPM 2.0/Secure Boot can be enabled to keep VBS enabled

but yeah i understand with the progression being unclear right

[proper drum]

So just to clarify I'm not against FACEIT AC itself, I'm just not a fan of the secure boot check part, but latest developer comments suggest it should be disabled for Battlebit going forward, so no longer an issue? #bbr-news message

Disabling hyper-v is not ideal if you run docker with WSL2, as Aqua mentioned you'd have to restart each time for the change to take effect, who the heck wants to restart their machine twice to go from playing the game back to running their docker containers. I'd rather have the anti-cheat force you to stop any running hyper-v/containers then force you to disable it all together

[onyx stirrup]

well you can enable hyper-v
read above your message

[proper drum]

My whole comment is based off those who can't enable secure boot, for them disabling hyper-v was their only option to play the game before the devs decided to tell FACEIT to disable that check (temporarily reverted to EasyAntiCheat anyways), which is only annoying if you were using hyper-v, otherwise a non-issue

[slate wren]

you runnings vms/containers is not the issue, its the fact you are running a hyperv host, which is used to cheat (not saying you are cheating ofc, just that it is used by some to cheat)

[proper drum]

I realize the reasons for it, I just wish there was a more user friendly approach to it then requiring hyper-v to be disabled all together for those lacking secure boot, like enforcing all vm's are stopped instead, anyways probably just wishful thinking on my part lol

[slate wren]

forcing all vm's to stop would make your computer inoperable, you do realize your operating system is virtualized when its on right?

[proper drum]

Not suggesting the windows vm itself should be stopped, poor choice of words on my part

[slate wren]

it doesn't matter, it being virtualized at all is the issue, meaning that the host (the hypervisor, i.e. hyperv) is easily able to hide cheats in memory and instrument the cpu.

In hindsight I probably should have explained why its a problem in my first message rather than just pointing out the problem itself. Apologies.