{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
8/24/2021 7:26:55 PM
6
Same. Win7. Though I've seen people say they got same error even on Win10.
English
-
That's good, if more reports come in from Win 10 we may get the fix we need.
-
What I don't understand is why Bungie so neglecting Windows 7? Cutscenes aren't fixed almost for a year now. And now today's crash. Windows 7 is listed in System Requirements as a supported OS. So, why they aren't even officially acknowledging Win7 issues?
-
I believe the issue with the cutscenes were kind of "ignored" exactly because of what our friend Ontarom said. It does bugs me too, hopefully they'll find a fix since like you just said, other games works just fine with BattleEye in Win 7, there's other Anti-Cheat Softwares that doesn't.
-
I want to believe the win7 issue with the cutscenes wasn't critical so it might have fallen through the cracks (it kinda sucks, but you can still play the game, and regular cutscenes play fine). And not that they plan on just dropping windows 7 users. If this is an issue with battle eye, i hope they can reach some kind of compromise.
-
The funny thing is that I have several other games with BattleEye and they always worked and works fine: Arma 2, 3 and R6 Siege for example.
-
Here's to hoping this can be fixed, then.
