{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
7/10/2020 2:19:55 PM
10
Hi there. What kind of error codes/messages are you receiving?
English
-
Initially I wasn't receiving any errors at all when my load times would take ages. It still loaded me in but it'd take at least 10+ minutes. Yesterday, every time I tried to load into Gambit with my friend I got the "beet" error even though nothing is wrong with my internet and I've tested it on other games. I typically close Destiny completely and have to re-login for anything to work, but it didn't help me this last time despite doing it 3 times.
-
What is your NAT set to? Have you reviewed our [url=http://www.bungie.net/en/Help/Troubleshoot?oid=13610]Advanced Steps Networking Guide[/url] for information on UPnP, NAT, and Port Forwarding?
-
Изменено (TheHaraamPolice): 7/10/2020 2:54:37 PMError code beet suggests that you may have pc hardware below minimum specs. I recommend that you ensure all drivers are up to date or by running the scan and repair tool. Clear your cache as well. Here is more information about beet: https://www.bungie.net/en/Help/Article/46903 Other Possible fixes for beet: Update graphics card driver Using cable connections, fiber, and DSL Change NAT Type
-
I also only tend to experience these issues on a fireteam. On my own, I do fine. (Except for load times. Those still suck from time to time).
-
Ok you should use the advanced guide given from bungie help.
-
I'll definitely give it a look when I'm off work. Thanks!
-
No problem! Glad to help!
-
I mentioned in my initial post that I've already done that. My computer meets all if not exceeds the recommended requirements (which are higher than the minimum). It is not my PC.
-
It’s always recommended to clear your cache
-
Every other activity was working just fine though. Loading in to the tower and other locations was fine.
