¿No encontró lo que buscaba?

Nueva publicación
Bungie Answered

Day 6 of Error Code Weasel

I am going to keep making daily posts until this issue is not only acknowledged, but fixed, since it was so easily fixed during the server slam. There has been 0 update about error code WEASEL since Mar. 5th 5:30PM PST. This issue was fixed immediately during the server slam, but 0 fixes/word about fixing it since the initial post. 

Bungie Account Name
 - CloudyMinds#6190

Platform - Steam

Description of Issue - About 45-60 seconds after launching the game and loading into the introductory tutorial, there is a red error that overtakes my screen with error code weasel.

Repro steps - To reproduce this issue, you have to launch the game, wait for the splash screens, begin the tutorial, and 45-60 seconds into the tutorial, I am kicked off/out with the error code, and taken back to the home screen where it says "Press (mouse1) to continue."

Extra Info - I am on Windows 10 (22H2 build 19045.6937), with a wired connection, and have no connectivity issues in any other game/application, only Marathon. I have played Destiny 2 on the same setup a handful of times previously and never encountered this issue. This error code of weasel was originally fixed on day 2 of the server slam, but was reverted/not implemented into the final/full game. This issue has been persistent since launch day and I have yet to be able to play Marathon, still. It's extremely frustrating having to check the forums, Steam updates, and Bungie Support Twitter for an update on a fix being implemented, and still not being able to play 6 days after launch. I have gone through all of the articles for help, I have made various changes to my router and network settings, I have re-installed the game. The only thing I am not willing to do is wipe my entire OS to make this game work. It shouldn't even have to get to the point of wiping a fully-functional computer to make 1 piece of software work.. Almost at the 1 week mark of still not being able to play the game due to Bungie's devs taking their sweet time to look into it and fix it despite having the issue fixed almost instantly during the server slam.. 

2

Comentarios

2 comentarios
  • Comentario oficial

    Hi!

    Thanks for reaching out and reporting this. I'm sorry to hear you're still getting Weasel errors preventing you from playing Marathon. Our dev team is aware of an increase in Weasel errors and is currently investigating. If you'd like, you can report this in our Marathon Official Discord to help the devs gather more info on the issue. Make sure to include your Bungie Name, where you are playing from, and how often you see Weasel errors.

    As a side note, if you'd like to stay up to date on known issues we are actively tracking, be sure to check the #dev-updates channel in our Marathon Official Discord. That's where our dev team posts regular updates on issues such as these persistent Weasel errors.

    Our apologies for the inconvenience with these errors. I really appreciate your patience while we work on this.

  • Good thing people not getting their twitch drops are a much higher priority issue than people who CAN'T EVEN PLAY THE GAME

    1

Iniciar sesión para dejar un comentario.