{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by BNGHelp6:
8/30/2021 3:12:13 PM
181
Hello. All updates surrounding this issue will be added to this thread: https://www.bungie.net/en/Forums/Post/259546034
English
-
Thanks for Update 2, great to hear a root cause is identified. Ideally Update 3 would be that an approach to the fix is planned, ideally with an ETA to set expectations. It would be best if there was an ETA before the weekend.
-
Update 3 was it won't be ready before the weekend starts lol
-
Like they knew we were going to ask about b4 weekend...LOL
-
Any ETA?
-
Probably not if they on the how stage
-
I am torn between the hope of an early fix and the resentment for the lost time. I thought Bungie was playing the Season of the Lost W7 Guardians
-
Thanks for the update guys! :)
-
i am glad to hear that the problem has been found altough i am curious if there is a rough estimation of how much longer we have to wait.
-
Considering the slowness of their answering and their minimal concern, not to mention both battle eye and bungee claimed that they do not know what it is causing this, but looking into it..Concerns me alot.
-
They just said they had found they cause of the problem and before that they already mention that the problem was on their part and not on battle eye. I think it will be fixed soon enough and the slow updates is understandable since i doubt they have many people noting down the bugs and it's likely another deparment which also fixes it. All we can do is just be a little more patient :)
-
Right with you man. but never stopped being patient I know how things are sometimes especially with all that data to go through.. and praise destiny 2 gamegods...
-
This is going beyond a joke now.
-
Bungie, It has now been 24 hours since you began investigating a catastrophic failure. Do you have any news for us? Because right now this is going the route the FPS problem did where the post slowly slides down the page until you forget about it. Your "Some users can't start the game" update is no longer very reassuring three days later. Please provide an update ASAP. Some more detail than "we are investigating" is now required. It is too long without serious recognition.
-
New update about 40 min ago - some buffer overrun protection change is at fault. It sounds like they've identified the root cause. That's certainly progress.
-
Hey, some progress is progress indeed! Now we can just sit back and wait on an ETA since they have committed to fixing it instead of abandoning 7.
-
Well said.
-
As a service provider to others for over 40 years, I have never distributed a single deliverable to an end user that didn't meet my own established/published criteria and constraints. If I went out and grabbed someone else's product and slapped it onto my deliverable to a client and it failed, my integrity is damaged (whether I get sued or not). The difference here is that the consumer/client (me and other Win7 valid users) are limited in our recourse - we basically will switch our interest toward another game and abandon the failed one. I hope it gets fixed soon - Destiny 2 is a nice stress relief and diversion. This snag is nothing compared to the complications and SNAFUs that cross-play will probably encounter. Bungie - this is your canary in the coal mine; if you can't get this little thing right, then it is doubtful that you will care about your impacted consumers. But hey, you can get revenue from other or new users so at the end of the day, you win regardless. I love capitalism and understand it can be a harsh mistress! I can live with that. /Good luck on the battleye fix for W7 users/
-
forses....
-
Still broken with the same missing file issue
-
Just had a 144 byte Destiny update come through.... still broken with the same missing file issue :(
-
Do we have any update?
-
Let me start with this... Thank you very much for the update and continued attention shown to this problem! Now the follow-up... Do we have a really rough ETA or are we just hanging in the dark until y'all over at Bungie know what to do? I suppose the best way to phrase my question is... Does Bungie know what has caused the issue and are working on a fix, or are we still on the "determining the root cause" phase which is going to be required before a fix can begin to be developed? Posting this here from the other thread. Maybe we will get an answer on this one.
-
I would offer my PC to be used in determining the problem but I have so much... "research material" that it's unsafe.
-
Been researching Projekt Melody? Skynet cometh...
-
Never really watched any of them. Never really got my attention.
