October 1 official checkpoint
Returning now? Install Hotfix 1.5.2 if offered, let PC shader caching finish, review the published Video Settings reset guidance and test server filters and voice. The hotfix ships FSR 4.1 and replication improvements; October 1 feedback still monitors remaining issues and treats Patch 1.6 as upcoming. Save the local preparation checklist and share the planning link with your squad.
First: establish the version and one objective
Check the installed client rather than assuming a downloaded update finished applying. Read the latest release post and distinguish it from the next-patch tracker. Choose one goal for the session: relearn a role, compare a setting, or join the squad reliably. Trying every new feature while diagnosing a crash makes the result harder to interpret.
Second: find the same server as your squad
Agree on platform compatibility, a region to compare and a server-language preference. Refresh and narrow filters if a familiar server is absent: the developer describes a 200-session broad-search limit. Favourite the entry once you find it. Keep an alternative that the whole group can locate rather than treating a full server as a broken connection.
Third: confirm voice before taking a leadership role
Check the intended voice channel and input device while the squad is able to respond. A menu indication alone does not prove another player can hear you. The latest community post still has reliability improvements in testing. If voice fails, document whether it is transmission, reception or a channel-specific dropout; use the communication guide instead of assuming every symptom is the old robotic-proximity issue.
Fourth: revisit loadouts and spawning
Review the new rifle unlock conditions if your role qualifies, and keep the supplies or equipment needed for your chosen job. Remember the published 15-metre enemy restriction on garrison placement and the underwater placement block. A missing HQ icon after a match transition belongs to a separate active investigation. Recognizing that distinction avoids repeatedly trying to solve a server-state problem with loadout changes.
Finish with a note you can use next time
After the session, record which single issue improved and which one still reproduced. Keep the game build and settings with that note. Mark the checklist complete only after doing the preparation; the saved state does not claim the game itself is working. Sharing a plan gives a friend the same starting choices, not your private completion state. Reset when you want a fresh session checklist.
Frequently asked questions
Does this checklist upload my progress?
No. Completion is stored in your browser. Sharing includes only a validated region/platform plan; progress is not included in the link.
Does finishing the checklist guarantee the bugs are fixed?
No. It helps organize preparation and reporting. The latest official issue status remains separate from your local progress.
Sources and verification
Sources are linked for independent checking. Dynamic figures are snapshots, not permanent values.