{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
8/3/2024 9:21:01 AM
5
Almost certainly caused by audio output: for instance, if you have headphones plugged in, unplug them and relaunch the game.
Open steam
Open destiny 2
Open volume settings and check where the output is for steam and destiny
Set both to default
Task manager close destiny and reopen)
https://www.bungie.net/en/Forums/Post/262533431?sort=0&page=0
https://www.bungie.net/en/Forums/Post/262528392
English
-
If you think this is an audio issue, can you think of a way to trouble shoot and solve the problem? Do you know why it is that audio would prevent the game from even launching the title screen? Shouldn-t there be a timeout in such cases?
-
I can only surmise that if the game engine can't get ahold of a working audio output (because it's not set correctly or for some other reason it's not available) it just stalls waiting for the resource to be connected or freed for use. I concur that there should be a timer somewhere in the engine for this kind of situations, but apparently there isn't...
-
Thanks for your answer, as I mentioned above that does not work.
-
Tried also reading both linked threads? The second one offers a different solution.
-
You are right, the solution is different, but it still doesn't work. I reset-ed the shader cache on my AMD GPU and killed battle eye through task manager, and the game is still stuck in a loading screen. Also, unlike the post, terminating battle eye does not close D2.
