How to read performance reports
Big Walk is a networked co-op game with a host-owned save, so performance reports need more context than a simple good or bad label. A slow host, wireless connection, voice-chat issue or platform-specific renderer problem can all feel like the same problem to the group.
Every report should record platform, patch date, host machine or console, group size, render settings and whether the issue affected one player or everyone.
Official PC and Mac baseline
The Steam requirements are the stable baseline before adding community settings or handheld notes.
| Profile | Operating system | CPU / memory / GPU |
|---|---|---|
| Windows minimum | Windows 10 | Intel Core i7-7700K or AMD Ryzen 5 1600X, 12 GB RAM, GTX 750 Ti / Radeon R7 370 / Intel Arc A380 class GPU. |
| Windows recommended | Windows 11 | i5-10600K or Ryzen 7 3700X, 16 GB RAM, GTX 1070 / RX 5600 XT / Arc A750 class GPU. |
| Mac minimum | macOS 15 | Apple Silicon M1 or newer, 16 GB memory. |
| Mac recommended | macOS 15 | Apple Silicon M3 recommended, 16 GB memory. |
Launch-window platform signals
These notes are leads. They should be updated after patches, store compatibility labels or repeated player reports.
| Platform or topic | Current signal | Next verification step |
|---|---|---|
| Switch 2 | NintendoEverything described the Switch 2 version as playable with an apparent 30 FPS cap and some visual rough edges. | Check patch version and compare with other Switch 2 reviews before making a firm recommendation. |
| Switch 2 community discussion | r/Nintendo discussion highlighted performance concern as a launch topic. | Summarize only repeated patterns and avoid single-comment claims. |
| Steam Deck | SteamDeckHQ and ProtonDB are useful monitoring sources, but this wiki should not claim a final Deck status until verified directly. | Record resolution, frame target, Proton version and controls when tested. |
| Host frame rate | The official FAQ tells players to reduce render scale and quality when performance hurts the session. | Check whether the host or a joining client is the bottleneck. |
| Voice and network issues | Official troubleshooting points to audio devices, mic activity, feedback, bandwidth and host framerate. | Capture group size, platform mix and whether external voice apps were also running. |
| PC settings databases | PCGamingWiki can collect save, input, graphics and compatibility notes over time. | Respect license rules and verify fields before copying. |
Report template
Use this format when turning a community report into a wiki note. It keeps troubleshooting useful without overstating one player's setup.
- Platform and store: Steam Windows, Steam macOS, Mac App Store, PS5, Switch 2 or Steam Deck.
- Patch or capture date.
- Host platform, host network type and group size.
- Render scale, graphics quality and frame target if available.
- Audio setup and whether the group used in-game voice/text or an external app.
- Observed issue, reproduction steps and whether it affected all players.
- Source URL and whether the wiki has reproduced it.
Sources & attribution
Windows and macOS requirements, store tags and user-review context.
House House / PanicBig Walk official FAQPerformance, audio, controller and network troubleshooting.
NintendoEverythingBig Walk review for Nintendo Switch 2Switch 2 review with performance notes.
Reddit / r/NintendoSwitch 2 review discussionCommunity discussion lead for Switch 2 performance concerns.
PCGamingWikiBig Walk on PCGamingWikiSettings, save, input and compatibility tracking lead.
ProtonDBBig Walk on ProtonDBSteamOS and Proton compatibility monitoring lead.
Steam Deck HQBig Walk review on Steam Deck HQSteam Deck review lead; verify before copying settings.
SteamSteam Community HubDynamic source for player performance and troubleshooting reports.