Server Slam Known Issues List – Marathon Help Center

The following is the current list of Known Issues players may experience when playing in our Server Slam open preview weekend.

Disclaimer

This is not a complete list of all known issues, but a targeted list of specific issues and their possible workaround solutions.

Capturing gameplay with apps like OBS and Discord may cause instability, specifically issues with inputs.
- Solution: We’re currently working on a fix, but you can try capturing your display/screen rather than a game/client capture.

The game client may experience latency or freezes when doing actions such as; resizing resolution, changing settings, exiting to desktop, adding friends, etc.
During launch, the screen may appear black while loading.
- Solution: Let the game load, it could take around 15-30 seconds to resolve.

Non-officially supported platforms, such as the ROG Ally X, will experience frequent crashes.
Setting the CMAA graphic setting to max may corrupt the graphics.
- Solution: Restart the client

Players may become “soft-locked” if they use the terminal while mid healing animation.
- Solution: Don’t interact with the terminal while using a Patch Kit or Shield Charge.

An issue can cause Runner bags to appear empty when attempting to loot it.
Perimeter: Some loot may not spawn in South Relay on Perimeter.
If a player is viewing the Armory tab while it refreshes, purchases may fail.
- Solution: Play a match or restart the client.
The Loadout menu has a small chance of not loading if navigating to and from the Loadout and Shell select tabs quickly.
- Solution: Slowly move to any menu tab, then back to the Loadout tab.
Equip prompt on Sponsored Kit says "Invalid" instead of "Not enough space" when there isn't room to unequip gear.
"Sell all" button in the inventory overflow window is not a hold function button as indicated.
Inspect Item is displayed as a press input rather than hold on controllers.
- Solution: Hold the indicated button

Thermal Optics Scope may disappear if a Runner becomes invisible while using a gun with it attached, leaving only the targeting dot visible.

If an item that is auto sold on exfil exceeds the Credit limit, the Runner’s primary weapon and mods may appear with a credit limit pip or red “X.”
The Full Screen Reward Cinematic that plays in the Run Report will occasionally display #item_invalid# text and will be completely blank if a Runner levels up during and does not loot or open loot containers.
- Solution: This is only visual and rewards are still gained.
Compromised weapons may show as retained instead of transmuted.
Compromised items do not display as transmuted in the Run Report if a Runner exfils with a Matter Fixative.

Rook: Unclaimed completed Contracts may inhibit use of Rook.
- Solution: Change your Runner Shell in the Shell selection, claim the completed Contract, and then change back to Rook.
If a Crew member has completed the first objective (Kill 3 UESC) in the Contract “Welcome to Tau Ceti,” they will be able to interact with the second objective blocking other Crew members that haven’t completed the first objective.
- Solution: Complete the first objective (Kill 3 UESC) before interacting with the second objective.
When Rebooting (reviving) a down but not out (DBNO) Crewmate, their status will show as "Disconnected".
- Solution: Crewmate can still be revived if they have not disconnected.
The LMG Gun Shield mod may stop deploying if a Runner rapidly swaps weapons multiple times.
- Solution: Don’t spam weapon switching.

In the settings menu, selecting a slider bar will cause some settings to snap to the minimum value.
- Solution: Utilize the indicated buttons on the slider to adjust.
While in a run, word wrapping can appear incorrect when hovering over some items on the ground.
UI elements are cutoff in several areas when utilized minimum screen bounds.
Rook image in Runner Select can disappear when quickly navigating from the Customize to Runner tab.
- Solution: This is just visual, and Rook can still be selected.

When in a crew with a member with a high ping, the crew leader will encounter the Passionfruit error instead of the player with the high ping.