Ce n’est pas ce que vous cherchez ?

Nouvelle publication
Bungie Answered

Sage/currant on rook

I've been getting error coded pretty consistently when trying to load in as rook. Just now i got saged however its mainly currant and another i cant remember. I hope this gets read and fixed... I love rook!!
0

Commentaires

4 commentaires
  • Commentaire officiel

    Hi there,

    Thanks for reaching out.

    The error code SAGE occurs when you or one of your crewmates took too long to connect to the game or load the upcoming map. CURRANT is a networking error that means the game client failed to connect to the dedicated server it was matched to.  


    A few things to try:

    • Restart everything
    • Fully close Marathon, then reboot your PC/console and router. A simple restart cleared CURRANT for a lot of players.  
    • Check your network path
    • If possible, use a wired connection instead of Wi‑Fi.
    • Disable any VPN or proxy and try again.
    • Check security software (especially on PC)
    • Temporarily disable or whitelist Marathon/BattlEye in any antivirus or firewall (Kaspersky and similar suites have come up in other connection issues).  

    If you continue seeing the SAGE error, we recommend you refer to our  Network Troubleshooting Guide for troubleshooting steps.

    If you keep hitting CURRANT after that, it helps the devs a lot if you include your platform, region, ISP, and whether you’re using a VPN or third‑party antivirus when you report it.

  • I am having the same issue but only with rook. I restarted everything and my wifi is fine. It seems like just an issue with rook at the moment

    0
  • same thing is happening with me now and it's only happening when I try to play as Rook. Tried resetting the game, as well as resetting my router and going LAN wired instead of Wi-Fi. Still happening.

    0
  • Hi Cabbage,

    Thanks for the report.

    Since this is only happening when selecting Rook, and you’ve already tried restarting the game, resetting your router, and switching to a wired connection, this looks more like a Rook-specific matchmaking issue. We are aware of players reporting this issue and are investigating.

    A temporary workaround is to queue with a different Shell for now if you keep getting CURRANT and SAGE error codes.

    Please share your platform, region, and whether you have crossplay is enabled or disabled so we can add those details to the investigation.

    0

Vous devez vous connecter pour laisser un commentaire.