{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by X51000:
3/12/2023 7:01:10 PM
39
DETAILED: Startup hangs at loading screen before title screen indefinitely
EDIT: I may have found a fix (shoutout to SlenderBeans), this at least worked for me. This is probably related to audio device changes such as using a USB audio interface, or in general a recent change to your sound configuration like new headphones. If that sounds similar try this
- Open windows > settings > App Volume and Device Preferences
- Make sure steam is set to Default
- Launch Destiny
- Navigate back to your App volume and device preferences
- Set Destiny to Default
- Force quit Destiny via task manager
- (I deleted my cvars.xml here, this may or may not be required)
If that didn't work for you @әуәѕ who has been in this situation for a long while also found that they had to clear their Nvidia shader cache. This didn't work for me, but if you have exhausted all other options try this as well
***********************************************************************************************************
I will document everything I can, I'm clearly not the only one with this issue, but none of the suggestions I've tried have worked
If a ticket is escalated on this problem, try this one as I hopefully have a lot of info below:
Issue: starting 2ish days ago, cannot load titlescreen.
DxDiag here: [url]https://pastebin.com/JtwdPHrY[/url]
cvars: [url]https://pastebin.com/4xgKgRuC[/url]
steamID: 76561198147271008
Current Behavior:
- Launch Destiny from steam
- Steam dialogue "Updating ticket..."
- Destiny window opens (may take a few moments longer than usual)
- Initial glyph loading spinner, lasts forever, never enters title screen even after 20 minutes
What I've tried, with no success:
Steam:
- Verified install
- Reinstall through steam
- Move install folder with steam
- Run steam as admin
- Delete the cvars.xml, both by individual file and by removing the bungie folder from appdata/roaming
- Disable Steam Overlay and Geforce Overlay
- Launching with Big Picture Mode
- Launching with a contoller
Drivers:
- Update Nvidia drivers (531.18)
- Downgrade Nvidia drivers (528.02)
- Update Windows 10
Firewall (using BitDefender)
- tried with disabling firewall
- added exceptions for all executables I could find:
- destiny2.exe
- destiny2launcher.exe
- miniTicketDbg.exe
- beservice.exe
- beservice_d2.exe
- BEService_x64.exe
- executibles detected by bitdefender pass firewall as expected
Windows Debug:
- Windows compatibility for win 8
- Launch from windows safe mode
- Added "Run as administrator" to the following executables:
- destiny2.exe
- destiny2launcher.exe
- miniTicketDbg.exe
- beservice.exe
- beservice_d2.exe
- BEService_x64.exe
Battleye Service:
- Uninstall using Destiny 2/battleye/Uninstall_BattlEye.bat, and then reinstalling by:
- running Install_BattlEye.bat
- launching through steam (runs install with BattlEye dialogue)
- editing to change file slashes (why not) (didn't work and reverted)
Port debugging:
- netstat -ano | findstr :<PORT> on the following ports without destiny 2 running:
- 3074
- 3724
- no tasks were found
- WITH DESTINY RUNNING no processes were found on those ports, do I have the wrong port numbers maybe?
GeForce Experience:
- (a user reported destiny2 wasn't visible here, but it was for me)
- Launch through GeForce
- Change video settings and try launching again, through windowed mode
--------------------------------------------------------------------------------------------------------
EDITS
- Replying in comments and also posting additional solution attempts here:
Harddrives:
- move from C:/ (nvme) to E:/ (ssd) and back again
- Samsung Magician Debug (no errors on any drives)
Network:
- Xbox networking debug (windows settings)
- /ipconfig release/renew/flushdns
- restarting router
- switching from ethernet to wifi
Additional fix from https://www.bungie.net/en/Forums/Post/262457475?sort=0&page=0&path=1
<cvar name="force_enable_multi_threaded_render_submit" value="0" ></cvar>
Toggle value=0 to 1 and back, did not work
SteamLink:
- suggested here: https://www.bungie.net/en/Forums/Post/262479762?sort=0&page=0&path=1
- Tried with iOS
- Tried with Steam streaming through macOS
- No dice
************************************************
Final notes for a while:
Some new discoveries. When watching resource monitor => network I've found some processes being created when launching destiny. When monitoring netstat some of these processes become CLOSE_WAIT or TIME_WAIT
Additionally the error event name in my DxDiag is AppHangB1, looking up that error brings up a lot of other steam games that have had similar issues, but the solution usually involves reinstalling steam, or messing with files. I've seen some folks try reinstalling steam but that doesn't seem to help
I think I've done enough on my end of diagnosing these for now. But for anyone else who wants to pick this up maybe start looking there
-
Thank you so much for your help. I've been trying to solve this bug for a couple of days and got nothing. In my case, the sound device change was the problem. Thank you!
-
Not sure if this will help anyone else, but I found an article on Reddit describing a service that's installed with MSI boards called Nahimic. Apparently it's a chore to get rid of (as most think it's malware) and a service that's automatic with MSI products. So I followed a suggestion to disable the service and stop it from auto booting with the system and volia! Destiny started working again. **From Reddit** "Another thing, check device manager under sound adapters you'll notice A-Vol and Nahamic in their might be note to disable and not uninstall. BUT FIRST THING! Go to services and stop nahamic. then right click to open services. find that service in their called nahimic and properties to find file for that system."
-
Thank you man, I've not been able to get in for a while, it means a lot to me, thank you.
-
THANK YOU! I'd been having this issue since the 3/23 updates. It was the output audio not having a setting after an update that was doing it for me. Seems to be solved now and I'm back in game. Happy days!
-
Good job. It's a sound device issue. Normally my default sound system is logitech 5.1 surround system. when I switched to my razor kraken headset all of a sudden the game Loaded.
-
Steam player. Last Wednesday & Thurday I couldn't play due to not being able get past the spinning logo's. Friday I could log in again so I played all weekend. Now 3-13-23 i got home from work and nothing again. (spinning logo's) thx BNGHelp4 for keeping us in the loop
-
2 RepliesHey All - I just wanted to take a second to say we greatly appreciate everyone's time and effort that you've put into trying to figure this out. As decisive as the community may be at times, it's really inspiring when players come together to help each other, and us at Bungie, on fixing issues like these. I've forwarded this thread to one of our engineers who has been working very hard to figure out what is causing this problem for so many of you and how to fix it. So please keep posting your troubleshooting steps here, and any other relevant information that may be important. We see you and haven't given up yet, nor will we! Thank you!
-
1 ReplyFor those who are interest, there is a work around. It is not a perfect solution, but you can "technically" play D2. Download Nvidia GeForce Now, and load D2 through Nvidia's remote server. After waiting for the queue to be done, it will login you into D2. The game is playable, but not enjoyable due to latency issue. However if you really want to play D2, this is temporary solution until Bungie come up with a permeant fix.
-
OMG Thanks so much for a solution!
-
1 ReplyWoo!! I’ve been dealing with this for nearly a week now and your suggestion about adjusting the app sound settings seems to have done the trick, thanks so much! Prior to changing those settings I identified a set of Nahimic Service (known malware) in my audio drivers and deleted all associated files, so that could have been part of what helped get me back on track too. Just figured I’d throw that in there as well for anyone else still dealing with this!
-
1 ReplyEdited by X51000: 3/12/2023 7:05:34 PMI found a fix that I've mentioned in the comments but edited to the top of the original post. I've also made a new post for visibility https://www.bungie.net/en/Forums/Post/262533431 I hope this helps some of y'all as well, I really do :)
-
I've been dealing with this issue since launch and following this thread while trying to get it working again. I was able to finally get mine fixed last night. Even though I had already tried it with no luck, I moved my install folder again to a different drive. I moved it from a HDD to a SSD, and for whatever reason this time it stuck. I go right to the main menu, hardly even see the spinning symbols. Thanks for digging so deep in to this.
-
1 ReplyIt's strange that, given your fix, the problem began so out of the blue
-
2 RepliesSo, I figured out what was causing the issue for me. I can't recall which thread I saw it in, but someone mentioned that "turning on their bluetooth headphones" fixed the issue for them. This caught my attention, as I did recently upgrade my sound setup from just some headphones plugged into the headphone port, to a DAC/AMP setup that is using USB instead of the headphone jack. I unplugged the DAC/AMP, and plugged in my old headphones. Booted up Steam, and Destiny launched perfectly normal. Went straight to title screen, and I got to orbit without issue. I believe the issue [i]could be[/i] Steam not having a proper output device selected in the Windows settings, at least that is what it was for me. After Destiny launched normally, I closed it out, unplugged my old headphones, and plugged my new sound setup back in. I then went to Windows Settings > System > Sound > App volume and device preferences. In here, I scrolled down to Steam, and made sure that the Output Device (the top dropdown menu) was set to Default. It was blank. After this, Destiny continues to launch normally, even after a system restart. To boil it down, I think the issue was Steam not having a proper output device selected in the Windows settings. It was probably selected specifically to my headphone jack previously, and so when those were unplugged, Windows defaulted this setting to blank. I had a very similar issue with Spotify not working until I did this same exact fix. Hopefully this fixes it for at least some others.
-
Edited by 9_9: 3/11/2023 11:07:32 PMnoticed something new in my own dxdiag after hard reupdating steam, in addition to all of the APPHANGB1, destiny2.exe now has another entry of RADAR_PRE_LEAK_64. old call of duty titles gave this error when they were poorly optimized on release..... again leading me to believe its a failed update just like the day1 witch queen problems which also had people stuck at the title screen. and before any 'mentors' flood in here, there are no problems with my RAM and ONLY destiny 2 has this particular entry and this many entries in the dxdiag..... EDIT: when searching this particular entry with destiny 2, i am again finding your post on reddit. its getting hilarious at this point
-
saw your post on reddit looking for fixes to apphangB1 LOOOOOOOOL, even those guys say theres no help ever on this forum. pretty funny
-
1 ReplyEdited by 9_9: 3/12/2023 12:04:22 AMFIXED IT!!!!!! sorry for the spam on your post today but i was caffeinated to hell and this issue has been making me angry! try this https://www.bungie.net/en/Forums/Post/262528392 reply there if it works or not please!!
-
3 Replies+1. Same issue. None of the methods helped.
-
1 ReplyEdited by SlenderBeans: 3/11/2023 11:04:47 PMI've started having the same issue. Game was working fine Thursday night, and now I'm just stuck on rotating emblems. Dxdiag: [url]https://pastebin.com/PmZXXmRi[/url]
-
2 RepliesHere is my dxdiag as well, hope this gets fixed soon [url]https://pastebin.com/Tnm1mtZZ[/url]
-
i have the same problem. Unfortunately since the last day 09/03/2023, at approximately 8 pm, my game does not go through the game's initial loading screen. I have this very annoying problem, and I've tried in every way to get the game to run normally. Uninstalling the whole game, steam, updating all drivers, bios, peripherals everything that can be updated. But unfortunately the game still persists. it's been 24 hours without being able to connect to any Game server. Quite a problem, especially for those who paid for the game's DLC, and are unable to enjoy it.
-
1 ReplyI have the same problem (endless spinning logo screen) steam user. My problem started Thursday night. I have not been able to play since Wednesday night. I'm able to log into my destiny2 phone app along with my DIM app and see and move all my items, so that's alittle comforting knowing nothing is deleted. bungie please keep us in the loop as to your progress on this topic.
-
2 Replieshad the same issue i found a fix that worked for me: i started destiny with steam link app with my phone (it didnt actually started tho, closed it itself immedietly) after that i started trying to start normally and it worked.
-
1 Replythey FINALLY acknowledged it in todays twab
-
Was having this same issue on day 28, it got better in the 3rd, but still: Can play the game normally from 1AM GMT-3 until 8AM GMT-3, after 8AM the following starts: Contacting servers after 10 - 30 minutes, followed by a Baboon + contacting + weasel (can connect back INSTANTLY when i get booted to title screen) Happens over and over again, until it hits a low population playing, cant even complete a Nightfall/VOps/Battlegrounds while servers are hot.
-
https://pastebin.com/g8qza23i From the twab looks like they want us to paste our dxdiag's, idk why, but there's mine. Having the same problems as y'all's since Lightfall dropped. Here's hoping we re now on the path to fixing this annoying bug...
