{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
3/18/2023 2:55:47 AM
4
Error Code Weasel When Equipping Void Loadout
Every time I try to use my void loadout, I get weasel coded. I have 2 void load outs and both do this. All other load outs are fine.
-
I had the problem earlier on Solar, when I was changing both Aspects and Fragments. For example, one Loadout has Aspects AB and Fragments 1234, and another Loadout has Aspects BA and Fragments 4321. Switching from one to the other causes an instant "weasel" error and kicks me to the title screen. Other combinations of Aspects and Fragments can cause it too, but unpredictably. It also works (breaks) on all characters and on all subclasses. A workaround solution would be to unequip things like mods, Aspects, and Fragments before equipping a Loadout. The Loadouts seem capable of filling empty slots.
-
4 RepliesEdited by SamTheArchangel: 3/18/2023 9:33:10 AMPlease check your void loadouts and see if the aspects are saved in different slots, if you’re using the same aspect in both of them, if so, see if putting the same (shared aspects) in the exact same slots for both, fixes it. (Make sure to save/overwrite them with the new orientation). I read somewhere in forums that someone said that is the issue, if it does fix it, credit goes to them.
-
Edited by Ursa Major: 3/18/2023 11:06:56 PMJust started getting this as well on the 3rd slot, right column loadout. Seems to be void loadout on my hunter. Selecting the loadout causes destiny to instantly crash with weasel error. Tried exiting to desktop and restarting, but it seems to be permanently broken now.
-
For me it's my pvp arc loadout. In the 3rd slot (Right under the first slot)
