Bungie Answered
Weasel Error code that started while loading into postgame screen after an exfil
I have 150+ hours in the game with no issues until 4:30 this morning when I get a weasel error code after exfiling and loading into the postgame screen. The weasel error has persisted since through restarts, network resets, reinstalls, everything I tried. all right before Cryo launches...
I just want to play the game :(
0
Commentaires
Hello there,
Thank you for your detailed report.
We understand that the Weasel error code has persistently cropped up when you play Marathon. Some players have reported success at resolving the Weasel error code by repairing Windows. When you have a moment, you may wish to try the following steps:
We also have an Advanced Troubleshooting Guide, if the Network Troubleshooting Guide did not help.
Thank you for the speedy reply. While I understand this troubleshooting method may resolve the issue for some users, I doubt the reason behind the Weasel I encountered was due to a change in the windows files/system as I had run several sessions without an update or restart until the occurrence of the error. This was especially troubling as it happened while loading from exfil to post game, and without my noticing was originally initiated by a Ginger error message that I did not fully read as I was pressing spacebar to quickly skip through the postgame and start another run. After accidentally selecting the 'wait for party' option the Weasel errors occurred.
This issue ended up resolving itself after accepting defeat for 2 hours and attempting to launch the game again around 30 minutes prior to the release of Cryo Archives. Upon the launch of the game after clicking to sign in, the Ginger error showed itself once again. This time, noticing it was different than the Weasel errors before, I selected the leftmost option to 'leave party/return to lobby anyway'. This eventually loaded me into a post game screen that showed my run was "status unknown"
However my exfil did thankfully track server side and I was able to keep my haul!
Another troubling thing regarding this error code is that I was on a Rook run and therefor not in a party during the run in which the error occurred.
Vous devez vous connecter pour laisser un commentaire.