I have the exact same problem after the reset. I don’t use chat often, so I can’t tell for sure when this regression started on my machine. Now whenever I press enter to enter the chat, the game freezes for 5 seconds then exits to the desktop. I did follow suggestion #1, but it didn’t help, crash/freeze persisted.
I’m in the process of reinstalling the game, will report back when I try again.
There has been Windows update between the last time I was able to use the chat and when I noticed the freeze, so it’s hard to tell which software update is the culprit (I.e. D2 reset, windows update).
It’s unlikely, but I will try updating/re-installing graphics driver if a fresh installation of game does not help.
English
-
Lol I figured out the issue. @bungie you need to inform all users of the current windows update. As of May 9, there was an update to windows insider build (i believe it was 19624) and it causes a crash in destiny 2 whenever chat is attempted. The previous insider build is stable but the may 9 version causes some sort of instability ( i believe it has to do with steam chat and destiny 2 chat access files being intertwined and crashing). To solve the issue, rollback to a previous insider build or completely opt out and install windows 10 without insider again. That will solve the current issue
-
Thanks for the info. We don't support pre-release builds of Windows 10. If chat still crashes in full releases please let us know.
-
I think it’s perfectly fine that the game is not officially supported on pre-release build OS. However, it’s still worth opening an internal bug with the dev team so that they can investigate now, rather than later when/if this particular problem is propagated to the Windows 10 release branch. -Just my 2 cents as a software engineer.
-
I see. I can confirm that my machine is opt-in for insider build, currently installed build number is "Windows 10 Insider Preview 19624.1000 (rs_prerelease)". I don't think I will rollback my operating system just so I can use chat. But it's good to know what's likely causing this issue. Thanks!
-
Same issue with prerelease 19624.rs_prerelease.200502-1339