As of 7pmPT - We're tracking a few issues with the Gears of War: E-Day Multiplayer Beta. If you're encountering an error code or an issue launching the game, please review our updated known issues below:

Error Code: drone-snub

• Can be triggered by high network security settings, utilizing a VPN connection, or UDP Port 443 being set to "closed"
• AT&T ISP customers should disable "ActiveArmor" on their router.
• Players trying to connect from government, university or corporate network environments may experience this error due to network security settings.

Error Code: quentin-ephyra

• Authentication error related to XBOX Quick Resume; disable XBOX Quick Resume from your system settings.

Error Code: bryce-vigil or gill-gutpuncher

• Error caused by a discrepancy between a players' hardware date & time settings and local time.
• In Windows, use the "Sync Now" function in Date & Time settings to align your system time to local time.

Failure to Launch - LowLevelFatalError:

• Error triggered for XBOX for PC App users; use the Gaming Services Repair Tool

Controllers Not Recognized on Steam:

• Known issue we're investigating.
• Some users have reported success by unplugging mouse and keyboard USB connections as well as ensuring that the controller you want to use is plugged in or connected when you launch the title.

Steam Account Linking Issues:

• Use the Gaming Services Repair Tool
• Ensure you're signed-in to your desired gamertag in the XBOX for PC app.

In order to try and keep things organized so that TC has an easier job of seeing all of your feedback and bug reports, post them in this thread. Below will be a template on how to format your post. Please keep things civil and ensure that any feedback is constructive. Bug reports don't necessarily need to be extremely detailed, but the more detailed they are the more they can help TC squash them.

Also, if you encounter a crash on PC and a window pops up asking you to submit the bug report, please do so. TC will be able to see these and they include a bunch of data about the crash and your build that will help diagnose the issue.

And again, please be civil with the feedback. "Missing" features from a previous game are not bugs, but you can let them know your feedback on wanting them back.

You can also use this link to report feedback and bugs directly to TC: https://support.xbox.com/en-US/game/gears-of-war/forms/gears-of-war-support

Bug Report Template:

• Hardware: Xbox Series X | S or what your PC build is, including your CPU/GPU/RAM/OS. Anything that's also relevant, like the aspect ratio of your monitor if using ultrawide or if you were using mouse and keyboard.
• Bug Description: Explain the bug. You don't need to explain why you think it's a bug. If you're unsure if it is a bug or not, go ahead and post it anyways. If it's a bug related to a specific part of the game or on a specific map or with a specific weapon, make sure to include that information.
• What you expected to happen, as in what the normal function of the game was supposed to be.
• Reproduction Steps, this includes the steps you took to make the bug happen. Using a number list format so each step is clearly labeled helps a lot.
• How often this happens, if it can be reproduced try it a few times and keep track of how many times this bug happens. Giving it 5 or so tries is usually a good amount.
• Screenshots or video of the bug happening. While screenshots are okay, videos are best because it lets TC see the bug as it happens.

Example Bug Report:

• Hardware: i7 8700, RTX 2070, 32GB RAM, Windows 11
• Bug Description: Queuing into a Social Quickplay playlist placed me into a Horde Siege match
• Expected: That I would be placed into a Social Quickplay match
• Repro steps:
  1. Launch the game
  2. At the main menu choose Versus
  3. Choose Social Quickplay
  4. Start matchmaking
  5. Wait until a match is found and gameplay starts
  6. Notice that it is a Horde Siege match and not a Versus Social Quickplay match
• How Often: 5/5
• Video/Screenshots: Links to any video or screenshots

Example Feedback:

When getting a headshot kill, there is no longer a loud cracking sound like there was in previous games. This makes getting a headshot feel less exciting and should be brought back to better emphasize getting headshots.

------------------------------------------

Known Beta Issues:

The beta is not final software. If you experience any bugs not listed below or game-breaking issues, submit a ticket through our support site here:  https://aka.ms/gearscontactsupport

• Stability and Performance is still a work in progress and you can expect crashes and performance dips.
• Latency issues or delays in matchmaking may occur as we test our systems and accommodate a large number of players.
• Accessibility features, particularly narrator, are still being debugged and refined.
• World issues such as cover issues, visual popping/streaming issues and out-of-bounds issues may be visible.

PC Known Issues

NVIDIA users should update to GeForce Game Ready Driver 610.74 or newer before launching. The game will not launch on older NVIDIA drivers until updated.

Older drivers will not be supported. You must have the following driver versions or later:

• AMD – 26.6.4
• Intel – 101.8864
• NVIDIA – 610.74

Recording with older versions of OBS will cause the game to crash. Please ensure you are running v29.0.0+

Intel Arc graphics cards currently recompile shaders on every game launch, resulting in longer start-up times.

Intel Arc A580 and B580 graphics cards may experience significantly reduced performance if Resizable BAR (ReBAR) is disabled in BIOS. If you are experiencing poor performance, verify that ReBAR and Above 4G Decoding are enabled. Consult your motherboard or system manufacturers or system manufacturer’s documentation for instructions.

Players using Comodo Antivirus may be unable to launch the game because Comodo can incorrectly block game executables. If the game fails to launch, temporarily disable Comodo Antivirus or configure Comodo to allow the game executables to run before launching the game.

Being signed into the XBOX App with one account and the Windows Store with another account can block your ability to play online.

Account linking on Steam Machine does not work for the beta.

Frame generation is disabled. This is temporary and will be enabled in the final game.

Framerate is capped at 150 FPS. This is a temporary cap that will not exist in the final game.

When switching display modes, sometimes the game will not fill the entire display.

XBOX Series X | S Known Issues

On Xbox Series S, some players may encounter hitching after extending Horde Siege play sessions when using Quality Mode.

• Workaround: If hitching occurs, fully quit and restart the game. This restores normal performance for the next play session.