{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
4/17/2021 12:39:46 AM
2
Anteater... giving up.
I've read your replies, i've seen your support posts.
I have zero issues with any other games, no latency to speak off, no packet loss, wired connection, ports forwarded, rechecked file integrity on Steam, still i'm unable to complete a single Grand Master because I know FOR SURE i'm getting a random kick to orbit with "code: anteater".
Tonight, got anteater during a raid and then 2 additional times during GM.
I love your game, I really do, but this is just stupid and shows an absolute disregard for your player base and for people willing to spend money on the content you produce.
-
Bungie uses a unique hybrid peer-to-peer architecture for Destiny 2 network connections, so comparisons to how well other games function are actually irrelevant when troubleshooting D2 error codes. [url=https://help.bungie.net/hc/en-us/articles/360049199051]Clearing the console cache[/url] by powering down and leaving the hardware unplugged for at least 5 minutes, or [url=https://support.steampowered.com/kb_article.php?ref=3134-TIAL-4638&l=]clearing the Download Cache[/url] and verifying the game files via Steam, could potentially help correct these kinds of issues. If that does not resolve the issue, you can review the [url=https://help.bungie.net/hc/en-us/articles/360049496531]Network Troubleshooting Guide[/url].
