October 1 official checkpoint
Hotfix 1.5.2 adds FSR 4.1 for Radeon RX 7000 Series and above and further stability and memory improvements. October 1 feedback reports encouraging early crash data, with monitoring ongoing rather than a guarantee. Finish shader caching before continuing. The hotfix recommends resetting PC Video Settings after recording your current configuration; historical launch-option tests below are not a universal fix.
Historical checkpoint: September 25 status
AMD crashes and driver timeouts remain prominent in the September 25 publisher feedback. FSR 4.1 now targets Patch 1.6; it is not a confirmed current crash fix. The older launch-option workarounds below are historical diagnostics, not a universal solution. Save your original configuration, test one change at a time, and record GPU, driver and build.
Historical context: Patch 1.2
Community Update #1 says some AMD GPU users continue to report crashes. The developers are working directly with AMD and assessing potential Unreal Engine-level changes. Patch 1.2 contains broad client and server stability work, but neither the patch nor the community update claims that AMD crashes are fully resolved. The September 25 feedback now targets FSR 4.1 for Patch 1.6.
Safe troubleshooting order
Start with reversible official steps. Do not combine multiple registry, BIOS and file edits from community posts before verifying the primary-source workaround.
- Update AMD Software: Adrenalin Edition and reboot.
- Disable the AMD in-game overlay and close other capture overlays.
- In Steam Launch Options, enter the full line: -dx12 -USEALLAVAILABLECORES -malloc=system
- Launch the game and test the same map or repeatable scenario.
- If DX12 still crashes, replace the entire line with: -dx11 -USEALLAVAILABLECORES -malloc=system
- Delete the complete launch-option line to return to the default renderer.
Keep the launch field clean
Never run -dx12 and -dx11 together, and do not shorten the published command while describing it as the official workaround. These launch options are temporary diagnostics, not a permanent guarantee. If you joined the Crossplay Playtest, restore Video settings to defaults before comparing results because official notes also acknowledge settings persistence problems.
Record the result
For each attempt, record GPU model, Adrenalin version, exact launch argument, graphics preset, map, time to crash and whether an overlay was active. This produces a useful support report and prevents repeating the same failed combination.
When to stop
If both official renderer modes fail after a clean driver update, remove all launch arguments and check the latest hotfix notes. Avoid stacking unverified fixes that make rollback or support diagnosis harder.
Frequently asked questions
What should I check on Hotfix 1.5.2 first?
Finish shader caching and follow the current published Video Settings reset guidance after recording your choices. Older renderer launch-option experiments below are historical troubleshooting, not a universal current requirement.
Should I use the DirectX 11 or DirectX 12 line?
Try the complete -dx12 -USEALLAVAILABLECORES -malloc=system line first as documented, then replace the entire line with -dx11 -USEALLAVAILABLECORES -malloc=system if crashes continue. Never use both renderer flags together.
How do I undo the workaround?
Delete the complete launch-option line from Steam Properties → General → Launch Options.
Sources and verification
Sources are linked for independent checking. Dynamic figures are snapshots, not permanent values.
- Official Hotfix 1.5.2 · released 29 September
- Official Community Feedback #6 · 1 October
- Normalized official status facts · checked 2 October
- Official Community Feedback #5 · 25 September
- Publisher facts verified 26 September
- Official current AMD status
- Official Patch 1.2 changelog
- Official launch workaround
- Archived current issue-status evidence