{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Terr:
8/24/2021 10:30:03 PM
2
I disagree, it seems that destiny2.exe fails when you invoke it directly because it can't find a generic Windows 8+ DLL.
BattlEye is simply _hiding_ that error when it indirectly launches destiny2.exe for you.
English
-
I too think that this is on Bungie's end, cause other games with BattleEye works fine.
-
Huh...that explains why it works on other games at least. Hope they can fix it asap...
-
Edited by phich: 8/24/2021 9:09:10 PMBattleye reported an error with Fortnite on the same PC - so may not entirely be Bungies fault - get a 'api-ms-win-downlevel-kernel32-l2-1-0.dll missing error, but seems Fortnite has then managed to launch anyway...
-
As a Win7 user, Overall i believe its at Bungies end. Fortnite had a recent update and there was some bugs on the Battleye part but it was a pathway issue. Overall Battleye works fine otherwise with Fortnite win7. Funny I've had zero issues (minus the win7 2fps videos) with Destiny until this update.
-
Same thing with me, it's definitely on Bungie's end then. Thank you guys for clarifying!
