Which CODM settings get reset when Season 7 lands on GameLoop PC
A major patch resets several layers of settings at once. Knowing which ones and where they live gets you back to your normal gameplay in under five minutes.
Every major Call of Duty: Mobile season patch resets a predictable set of settings. Season 7 is expected on 5 August and there is no reason to assume it will behave differently. The time to note your current configuration is before the patch, not after.
The two distinct settings layers
GameLoop PC players have two places where performance-related settings live, and both of them reset independently.
Inside the game — graphics quality, shadow detail, frame rate cap, and audio — these are stored per the game's own profile. A season update refreshes this profile and frequently reverts options to default values suited to mid-tier mobile hardware, not a desktop.
Inside GameLoop itself — renderer (DX11 or DX9), virtual display resolution, frame cap (if set at the emulator level), and memory allocation — these usually survive across patches because the emulator is not updated by the game patch. Usually. It is worth checking.
The symptom when only the in-game layer resets: the game loads, frame rate feels wrong, but the emulator's own interface looks unchanged. This is the most common post-update confusion and the one with the fastest fix.
What typically reverts
| Setting | Where | Typical post-update default |
|---|---|---|
| Graphics preset | In-game → Settings → Graphics | Medium or Low |
| Frame rate cap | In-game → Settings → Graphics | 30 fps or device-default |
| Shadow quality | In-game → Settings → Graphics | Enabled, High |
| Anti-aliasing | In-game → Settings → Graphics | Enabled |
| Controller vibration | In-game → Settings → Controls | Enabled |
| Custom key bindings | GameLoop key mapper | Potentially wiped |
Anti-aliasing and shadow quality are the two that cause the most visible drop in competitive clarity when they re-enable — the image softens and silhouettes against complex backgrounds become harder to read. These are worth restoring first.
Key mappings specifically
Season patches have inconsistently affected custom key mappings across different seasons and different machines. Some users find all their bindings intact; others find the scheme reverted to the default GameLoop layout.
Take a screenshot of your current key mapping layout before the patch. This takes thirty seconds and costs nothing. If your layout survives, the screenshot is irrelevant. If it does not, rebuilding from a screenshot is an order of magnitude faster than reconstructing from memory.
Season 7 adds at least one weapon class (rocket launcher — the JOKR) that requires a key binding not needed in any prior season. That binding will not exist on your current layout regardless of whether your other keys survive. Check for it specifically.
The shader compilation window
The frame rate in the first match after a major patch is not representative. New maps, weapons, and modes each require shader compilation on first encounter, and that compilation happens during gameplay. The first session will stutter and then largely correct itself. The second session is a much better baseline.
This is the most commonly misdiagnosed performance problem of every season launch. It resolves on its own. The correct response is to finish the session, not to start changing settings.
AOW 32-bit versus 64-bit after the patch
GameLoop documented a crash affecting the AOW 64-bit engine on CODM in December 2025. No resolution has been announced. Season 7 may or may not trigger this on your machine — it depends on which code paths the season's new content exercises.
If Season 7 produces crashes that were not there in Season 6, the first diagnostic step is switching to AOW 32-bit in GameLoop's settings. Do this before reinstalling anything. The 32-bit engine costs some headroom on high-end graphics settings but is Tencent's documented workaround for the crash class in question.
What to note now
Before 5 August, write down:
- Your current in-game graphics preset or the exact settings you use
- Your emulator renderer (DX11 or DX9)
- Your in-game frame rate cap
- Whether you have custom keybinds and a screenshot of the layout
After the patch lands, restore these in sequence: emulator settings first, then in-game graphics, then keybinds. Give the game one full session before making further adjustments. The shader compilation window distorts your read on actual performance.
Season 7 Terminated — complete guide index
This article is part of the Season 7 Terminated guide series for GameLoop PC. For a full overview of every mode, guide, and fix in Season 7, see the Season 7 Terminated hub.