{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
8/18/2019 3:05:17 PM
1
Error Code Buffalo
I cannot get Destiny 2 to work. Yesterday, the game was behaving very poorly, terrible latency and ping, npc's not loading, etc. so I closed the game and tried to relaunch which did not fix it. I completely deleted the blizzard launcher and all its corresponding files, then reinstalled it. Today, when i try to launch the game, all i get is the error code buffalo. I've already scanned/repaired the game, checked for updates, restarted pc, restarted blizzard launcher, changed DNS server IP, all to no avail. I have good internet (100MB/s) and the speed is not the issue. I am not logged into blizz from another computer. What can I possibly do now besides waiting a month to finally transfer to steam?
-
Hi slayersabre. The [url=https://www.bungie.net/en/Help/Article/11912]BUFFALO[/url] error occurs when there is a connection issue with Battle.net's servers. You may want to review our [url=https://www.bungie.net/en/Help/Article/11912]BUFFALO[/url] help article for more information about this issue. If that doesn't help: [quote][b]1.[/b] You may also want to try opening the battle.net launcher "Settings" and change the "When I open a game" option to "close the battle.net launcher completely" option. [b]2.[/b] Some players have suggested disabling Internet Protocol Version 6 (TCP/IPv6) on the PC might help with this issue. [b]3.[/b] You may want to change your region/server to another location. [b]4.[/b] Some players have suggested disabling the "Always require authenticator for login" option in your Blizzard account settings. [b]5.[/b] Some players have reported that disabling IPV6 has helped them with this issue. [b]6.[/b] Some players have reported that logging into their Battle.net account and Destiny 2 on another PC then logging out and logging into them on their first PC have resolved this issue. [/quote]
