Didn't find what you were looking for?

New post
Bungie Answered

Stuck on Signing In Screen As A Brand New Player

Hello, I know this is a bit of a known issue but I am a little worried. I bought Marathon on Steam, downloaded it and started it up. The first issue happened when right after the Terms of Service sign up. I believe a cinematic or a tutorial was supposed to show up on screen for me to watch/play through but the screen went black instead for many minutes. Afterwards I decided to shut off the game from the Steam client side and try again. Now instead of a black screen, I saw the "Click to Play" screen show up and after clicking it goes to the "Signing In" loading screen. I sat there for a good 10 minutes before giving up. Now I have 2 hours of Sign In Simulator on steam... I tried the troubshooting methods suggested in this site and looked at the other forums for help but none of it worked. I believe that my Huwei 5G Router is to blame from what I have been researching. I might be paranoid right now but I worry since that I turned my game off after the Terms of Service screen, I might never even be able to play Marathon in the future. I hope this can be passed on to the devs so a good fix can come in the future. I really want to try out this game.
0

Comments

2 comments
  • Official comment

    Hi there,

    Thanks for reaching out, and I’m sorry you’ve been stuck on the sign-in screen instead of playing. Closing the game after accepting the Terms of Service will not block you from playing in the future or lock your account.

    Along with the steps in our Marathon Network Troubleshooting guide (including NAT, UPnP, and firewall checks), please try the following if you can:

    • Fully power-cycle your router and PC, then try again

    • Verify your game files in Steam or perform a clean reinstall of Marathon

    • Temporarily try a different network (wired connection, different router, or mobile hotspot)

  • Hello, 

     

    Glad to know that won't be the case, thank you.

    I have tried all of those methods. Both on the 1.0.6 and 1.0.5.3 versions on Steam and the problem still persists. 

    I think I will wait for an update that will fix this. Thank you for the suggestions anyway and have a nice day.

    0

Please sign in to leave a comment.