Attention, vous êtes sur le point de quitter Arc Games ! Souvenez-vous de ne pas divulguer les informations de votre compte, car le site auquel vous tentez d'accéder n'est pas affilié à Arc Games.D'accord, j'ai compris
Continuer et quitter Arc Games.Non merci
Retourner à Arc Games.
*The Eternal Dawn Minor Update will be available for download in the Windows 10 Store and Xbox Live Marketplace at 9a PDT (18:00 CEST) on April 6th.*
Welcome to the second Minor Update of the Eternal Dawn, and the final update of the Gigantic Open Beta! While the team shifts their focus to completing and polishing the final version of the game, this update introduces several fixes to some of the more prominent issues you might have encountered while playing. Whether addressing the “40 second” stall on the hero confirmation screen, ensuring your teammates are visible once they hit the battlefield, or preventing the loss of your fortune card draws when you’re pulled into a match, you’ll find a fix coming with tomorrow’s build! Just remember to download the latest game update starting at 9a PDT on Thursday, April 6th!
While you can read up on what the future holds for Gigantic in the latest State of Gigantic blog, we’ll also be watching and listening for any problems you encounter while playing in this week’s build! We want to hear any and all of the issues you uncover, so be sure to visit our social channels and chime into the discussion:
We'll see you on the airship!
You can find a full list of known issues with the beta build over on the official forum. We'll keep this list up-to-date with the biggest issues (and solutions) that are reported during the Open Beta:
We'll also be tracking the most impactful issues - as well as any workarounds or known solutions - on the official subreddit:
Known more widely as the "40 second" bug, players would fail to progress past the hero confirmation screen after locking in a hero to play in the upcoming match - usually with (you guessed it) 40 seconds left on the countdown. This was often due to a player failing to connect to the lobby, and would force the entire team to manually exit the match and accept a matchmaking penalty as a result.
Since that's not an intended experience for anyone involved, we've fixed two bugs surrounding the issue: one for the user who disconnected, and one for the rest of the players: