[2019] Xbox Framerate Bug / Framerate Degradation

Hey guys,

We're currently investigating the issue where Xbox Frames can be incredibly poor and makes the game stutter. What would help us narrow down the cause and get to certain fix is gathering more information about why this problem happens, so if you're experiencing the extreme stuttering if you could please fill out the information below, that would be incredibly helpful.

What Xbox are you using?

- Xbox One

- Xbox One S

- Xbox One X

Do you have ATLAS installed on an Internal or External Drive?

- Internal

- Internal and External (game is on Internal)

- Internal and External (game is on External)

What game mode are you experiencing the issue in?

- Single Player

- Official Servers

- Non Dedicated (Host)

- Non Dedicated (Client)

- More than 1: please specify

- All

Have any of these workarounds resolved the issue for you?

Workaround 1:

Hit the dashboard button
Quit the ATLAS application
Relaunch it

Workaround 2:

Hit the dashboard button
Quit the ATLAS application
Restart the console
Relaunch ATLAS

Workaround 3:

Moving the game to an internal hard drive

Workaround 4:

Under Preferences: Capture and share: Allow game capture: Don't Capture.

Workaround 5:

Clear your Xbox Cache (guide on how to clear the cache)

This isn't a bug we've ever experienced on our side so we'd like to get to the bottom of it as soon as possible. Any information you're able to provide will be very helpful.

Thank you very much Pathfinders!

So you do not own an external hard drive at all right?

I've added another question about game mode

We do have some fixes in the pipeline which could resolve this issue (it would go out in the next client update which hopefully will be this week), however, we won't know for sure until we can reproduce the issue on our end.

Question, do you have an external HD at all?

Thank you for all the info guys!

Saved By Grace indeed. We think you may have found the issue.

Thank you all for your assistance in helping us to identify this issue. We are now working on fixing it. Please refer to the announcement at the top of the page.

There was a crash associated with this issue which would have happened in Non-Dedicated and maybe else where. The patch with this fix has just launched!

I'm going to lock down this thread as this specific issue was resolved by our latest client-side patch, however, if you are still experiencing similar problems please create a new thread and we'll investigate (and escalate to a mega-thread if more info is warranted).