Like a lot of services you probably use today. One of the reasons for this was that Bloodhunt allegedly can't receive hotfixes due to Sony/crossplay and the game can only be updated roughly once a month. What's missing / what was rushed is a nice uninstall procedure. My concern- I left months ago after critical bugs were left in the game for several months at a time.The methods by which this anti-cheat middleware works (user mode service + sys kernel mode launches) is identical to EAC and Battleye.Not a single byte of anti-cheat middleware is loaded when you start your system (so it's not like Vanguard).Not a single byte of anti-cheat middleware is running when the game is closed.So, I'm going to reiterate once more for the FUD-spreaders in this thread: Manually closing the service or rebooting will fix this. This is a bug, and has been confirmed to me. This prevents the other services from stopping as well. In an exclusive interview with Newsweek, the developers behind 'Vampire: The Masquerade Bloodhunt' spoke about their newly-announced battle pass system. There is currently a known bug where sometimes (haven't encountered this myself) the main user-mode process (AntiCheatExpert Service) doesn't close. Sc query "AntiCheatExpert Service" SERVICE_NAME: AntiCheatExpert Service TYPE : 110 WIN32_OWN_PROCESS (interactive) STATE : 1 STOPPED WIN32_EXIT_CODE : 1077 (0x435) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0 Vampire: The Masquerade - Bloodhunt is a battle royale set in a world where vampires follow a law called the Masquerade, which involves keeping their existence a secret.If players are running around and acting like vampires in Bloodhunt, then how does the game handle the Masquerade. Sc query ACE-BASE SERVICE_NAME: ACE-BASE TYPE : 1 KERNEL_DRIVER STATE : 1 STOPPED WIN32_EXIT_CODE : 1077 (0x435) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0 Sc query ACE-GAME SERVICE_NAME: ACE-GAME TYPE : 1 KERNEL_DRIVER STATE : 1 STOPPED WIN32_EXIT_CODE : 1077 (0x435) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0
0 kommentar(er)
