{{
`${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
-
Edited by Pasha: 8/30/2021 3:15:29 PMI don't see anything new, it was said on Saturday)
-
Edited by MigitMD: 8/30/2021 2:44:27 PMDeleted.
-
Monday ... my D2 game does not start, it is not a failure in a NASA control tower, it is just a game that used to work well for all of us and now it does not. Solution removing BattlEye is easy ... ------- Lunes... mi juego D2 no arranca, no es un fallo en una torre de control de la NASA es solo un juego que antes a todos nos funcionaba bien y ahora no. Solucion quitar BattlEye es facil...
-
not even after the weekend... "maybe" next week right?
-
I doubt that someone‘s working on this on the Weekend. I would say: We get a fix bundled in a Patch on Tuesday (if there is any) or we dont get a fix at all and Bungie changes the OS Requrements instead. It took too long already … i really have a very bad feeling about this 😥
-
Yup, that's my fear too.
-
if they dont "give" a workaround for the week (maybe 2 weeks) without leveling, I think my plans to grind 20 relic levels and hard cap to try doing high end content will be thrown through the window.
-
I recorded my problem https://www.youtube.com/watch?v=gHy6w1xQYfU
-
Edited by Feltharion: 8/29/2021 2:17:40 PMThanks again Bungie! It's such a relief to know you guys have found the exact problem and cause of it, just a matter of time to get the game running for us again, stay safe! Don't mind the mad people, I imagine there's a lot but you guys are obviously working on it. Any news about the issue with cutscenes though? Are these somehow related?
-
-- GDPR: removed by user request --
-
@Bungie how would you describe yourself or call yourself if you were in my position?
-
I hope that DE will draw the consequences so that it never happens again.
-
Please do hurry, my friend can't play D2 with me because of this and it really bums me out. Thank you.
-
then fix it over the weekend. You promised us a product and you didn't deliver and for the last 4 years we have been getting half broken ones with no compensation , just removal or denial of access to content we paid for. FIX IT! Easy fix , remove battleeye. WE DIDN'T ASK FOR IT! And you hid it from the community cuz you knew it would cause backlash and boycott of the new season and then you didn't even do a basic QA test or google common issues with it like the one we are having now. FIX YOU'RE STUFF OR REFUND EVERYONE FULLY FOR THE LAST 4 YEARS!
-
BattlEye isn't the problem.
-
Probably, but I wouldn't consider that absolute yet. Battleye almost certainly has a precompiled module inside destiny2.exe - it could be a/the source, especially if they haven't finished a fix yet.
-
Edited by Zakrzep: 8/28/2021 6:26:43 PMMaybe some info about how long we gonna wait ? I think the approximate time will be fine.
-
Sorry, but I fail to see how a 'buffer overrun' translates to 'missing file installation'. How about we just revert to the older exe and go from there.
-
Something they static linked for buffer overrun protection isn't in the Win 7 API.
-
overrun protection for what? I played Destiny 2 on Windows 7 the day before this fiasco happened. So i'm genuinely curious as to what they screwed up; because before BattlEye, i had no trouble. Then they introduced it, and now I can't even open the game. So please pardon my lack of knowledge on the subject- because i'm curious as to how this happened and made it through testing without giant red flags of the game not even opening.
-
There was a change to destiny 2 that helps stop something called a static buffer overflow. Overflow in terms of memory means that an memory address that was out of bounds was overwritten. Such instances can cause programs to crash or even be used to run scripts that shouldn't be running. I could explain everything in more detail, but I would rather not leave a wall of text.
-
Just because a vulnerability isn't public doesn't make it less of a problem. And now that they've published this, reverting would be asking for people to find it.
-
um...what are you talking about?
-
Given the name of the library, it is unlikely anyone without access to put files on your computer in a place D2 cares about could even begin to try to exploit it.
-
Edited by XiiDraco: 8/29/2021 12:12:46 AMA buffer overrun happens when writing data past what is the expected memory space in an array — as a computer science topic. Of course you would need to understand, how memory layouts work in your computer, how and why data is written and in what particular context, and much more. I don't want to write an essay that you may need even more abstract contexts to even understand so I'll be brief. You wouldn't often notice a buffer overrun occurring because writing to memory outside of the expected space doesn't usually cause hard crashes (unless you are debugging for them) but instead affects data in other parts of the program. For example if you accidentally write past the end of a string (that's just text stored as data btw), the string might still say, "Hello World" but if the data you were using for your player's health is placed right after the string in memory, suddenly the health data has been written over and now your player has -2147483648 health (not specific this is just an signed overflow joke). Memory (heap in this case) corruption is NOTORIOUSLY hard to detect, find, and fix. I'm assuming the library that doesn't happen to exist on Win7 which is missing is for safeguarding against, or detecting accidental corruptions due to buffer overruns. And before you ask no, this is not corruption as in, file corruption on your drives or anything, this is memory corruption which happens all the time in programming, usually do to an oversight in code. It's only a temporary space and more often that not your OS can and will prevent a program from altering memory outside of it's space *accidentally*. As for your "giant red flags" about it going through testing. You can't test every single machine and environment those machines are running in. In this case, the bug (technically missing library they linked against so not really a bug but more of an oversight) very likely wasn't found on any configurations that they tested for. (I should also mention that if it relys on libraries from the OS, changes to the OS like updates could also break functionality for the game which wouldn't be Bungie's fault at all) And no, it's not easy to just "test everything". If you understand that you are lacking knowledge on the subject, maybe consider learning more about it. Computer Science is actually quite fun when you start to understand the concepts!
