{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by uniballer:
12/1/2017 2:58:30 AM
4
Thanks for explaining the obvious guys.
Its called a hyperbolic statement - look it up.
You can play semantics all you want - doesn't change the fact that Bungie failed to provide a solution, but Ubisoft had actual support representatives available to troubleshoot problems, and coincidentally, the service causing a problem with Uplay was also causing a problem with my Destiny instance.
#DestinyFixed.
English
-
So... how can we "fix" it too?
-
Run msconfig (press Win+R, type msconfig, press enter). Under the services tab, check the box to "hide all microsoft services", then click disable all. Next open the task manager, and under the startup tab, disable all programs. Now reboot. Hopefully Destiny will now work without giving a buffalo error at login. Now you can go through and re-enable services/programs 1 (or a few) at a time (and rebooting), to try to figure out which one was causing the problem, and disable that one.
-
Even with everything disabled (exept microsoft services) it doesn't work, i keep getting Buffalo and Weasel
-
You've probably got something different causing buffalo. I never got a weasel code, so could be its the same thing causing buffalo and weasel...
