{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by MigitMD:
8/30/2021 3:41:13 PM
4
Thanks for acknowledging this and giving it an actual thread, made by you.
If it seems like whatever fix will take weeks to figure out, might I recommend taking BattlEye out for now and reverting to the previous EXE so that we can still play while you work on a fix that includes BattlEye integration?
Also I'm seconding and 'thirding' the communication; please have a routine 'update' on the status, so that it puts us at ease, knowing you're actively working on this. Also, please test run it on a Windows 7 system, so that you know it works. Also, it's not just Windows 7, some Windows 8 and Windows 10 (home) users have been hit too.
English
-
So they're still trying to figure out how to fix it, and not at the testing stages of if a fix works. Doesn't seem like we'll get the fix before the reset, in time to get some week 1 stuff.
-
Sadly.
-
They did say its not battleye related
-
I know, I'm starting to think that whatever change they made, has to do with their implementation of BattlEye, not the software itself. So, my recommendation to them is to take BattlEye out of the equation for now, thereby allowing those affected (windows 7,8) to play again, while they work in the background trying to get their implementation procedure to function correctly on Windows 7/8. Instead of the normal "we're gonna fix this and not everyone can play while we do so." I honestly don't care if they use an anti-cheat system or not, because I don't like playing PvP at all...i just want to play the game in general, which is PvE.
