{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
8/26/2021 9:37:25 PM
5
Latest update: our issue made it to the top of the issue list in todays TWAB.
The latest reply from the bungiehelp bots here is they're still working on it but doubt it was battleye related.
English
-
Wonder if it'll be fixed this week, so we don't lose a weeks worth of bright dust, pinnacles, and eververse stock.
-
Edited by Omega: 8/26/2021 9:59:07 PMI think instead.. we should worry about some type of in game compensation from Bungie...
-
Doubt it. While this may have affected hundreds of player, we still likely only account for a single digit percentage of their customer base (across all platforms). Realistically, this is probably some oversight in their code not correctly referencing the location of library definitions or something in non-Win 10 OS. That it got through QC and that the cutscene stutter has not been fixed for almost a year, is a pretty clear indicator that we're only around because they're still legally obligated to keep us. With that in mind, them fixing the bug to let us play is probably their equivalent of "compensating" us.
-
Well sadly ..the percentage is larger because there are many ,many on Windows 8 and 10 that still can't play either..
-
Win 8 likely has the same problem as us, but I suspect the Win 10 people are dealing with something else. Most of the ones that claim to have it on Win 10 have been scarce with information. Some of them have recently claimed they fixed the problem with changes to their anti-virus exceptions or running the game as administrator.
