{"id":5973,"date":"2017-11-22T21:41:14","date_gmt":"2017-11-22T21:41:14","guid":{"rendered":"http:\/\/BungieNet_ContentItem_46492"},"modified":"2017-11-22T21:41:14","modified_gmt":"2017-11-22T21:41:14","slug":"this-week-at-bungie-11-22-2017","status":"publish","type":"post","link":"https:\/\/sickgaming.net\/blog\/2017\/11\/22\/this-week-at-bungie-11-22-2017\/","title":{"rendered":"This Week at Bungie – 11\/22\/2017"},"content":{"rendered":"

This week at Bungie, we explored Mercury \u2013 in two timelines.<\/p>\n

Curse of Osiris will send you to a new destination, where you\u2019ll learn its fate in the past, present, and future. At the heart of the journey is a forest of endless realities.<\/p>\n

If you missed it, here\u2019s the recap.<\/p>\n

[embedded content]<\/p>\n

Next week, we\u2019re back with a parade of the gear you\u2019ll earn, including some details on new ways to earn it.<\/p>\n

<\/div>\n

Sustaining Operations<\/big><\/strong><\/p>\n

Working with the Destiny Operations Center, Destiny Player Support<\/strong> keeps a finger on the pulse of the Destiny 2 population. We investigate error codes, and we share our findings through @BungieHelp<\/a> for community awareness.<\/div>\n

This is our report.<\/p>\n

\n

Buffalo, Part 2<\/strong><\/p>\n

Last week, Hotfix 1.0.7.1 was released to address Buffalo<\/a> errors on PC. We have discovered that some players are receiving erroneous Buffalo errors within the game client that are caused by alternate factors. These issues sometimes relate to network stability, or having multiple PCs connected to Destiny on a local network. Please follow steps within the Network Troubleshooting Guide<\/a> to ensure you’ve applied the correct settings for Destiny 2 gameplay. Additionally, follow steps for configuring UPnP<\/a> if you have multiple PC\u2019s on the same network.<\/div>\n

Continued Investigations<\/strong><\/p>\n

\n