The error message tells you to remove the launch argument. It is not always the problem. The DirectX 12 Not Supported error in AION 2 means the client started a DX12 or D3D12 render path your system could not service — but the trigger is often something else entirely. An outdated driver, a quarantined anti-cheat file, or a laptop running the game on integrated graphics all produce the exact same text.
Fix it by removing -dx12codecodecodecodecode or -d3d12codecodecodecodecode from the Steam launch options, updating the GPU driver, and forcing the game onto the dedicated GPU. That sequence resolves the error for most players within twenty minutes.
The mistake that costs players hours is jumping straight to reinstalling the game.
The launch argument is a decoy
Remove -dx12codecodecodecodecode and -d3d12codecodecodecodecode from Steam launch options first. The error text names them explicitly, so it is the fastest check. Right-click the game in Steam, open Properties, and clean out the General tab’s Launch Options box entirely. Then launch again.
Still failing? Stop touching launch options. The next most common cause is Windows Security flagging NC Guard, AION 2’s anti-cheat. Check Virus & threat protection → Protection history. If NC Guard files were quarantined, restore them, then add the game’s installation folder to the exclusions list. Players skip this step because the error text points at the GPU. That is a false trail.
The driver sequence most guides miss
Run dxdiagcodecodecodecodecode and confirm the Display tab reports DirectX 12 with a recent driver date. Then update the driver anyway. NVIDIA shipped a Game Ready driver for AION 2; AMD and Intel have their own releases. Outdated drivers reproduce this exact error on hardware that ran DX12 titles months ago.
Laptops have a separate trap. The game can launch on the integrated GPU while the system UI uses the dedicated one, and the renderer dies before you see a frame. Windows Settings → System → Display → Graphics, browse to the game’s executable in the binaries/win64codecodecodecodecode folder, then set GPU preference to High performance.
Troubleshoot in order, not everything at once
| Step | What it actually solves | Time |
|---|---|---|
| Clear Steam launch options | Stale -dx12codecodecodecodecode / -d3d12codecodecodecodecode arguments force a broken path |
1 min |
| Update GPU driver | Renderer fails on old driver despite DX12 support | 10–15 min |
| Force dedicated GPU | Laptops silently launching on integrated graphics | 3 min |
| Restore NC Guard files in Windows Security | Anti-cheat quarantine breaks the render pipeline | 5 min |
| Verify game files | Partial client from an interrupted update | 5–10 min |
Follow the order, not the symptom you think you have. The mistake that costs players hours is jumping straight to reinstalling the game. Verifying integrity catches a corrupt client in minutes and preserves all settings.
When the error keeps coming back
Run the executable from the installation folder as administrator — the desktop shortcut can inherit old compatibility flags. Then disable overlays from Discord, NVIDIA, and MSI Afterburner. Overlay hooks into the renderer trip the same crash on systems that pass every other check.
The -dx11codecodecodecodecode flag is a workaround, not a fix. It forces an older render path and drops DLSS frame generation support. Use it once to confirm the hardware is stable, then return to a normal setup once the real cause is cleared. Similar GPU access errors have hit other Unreal Engine MMORPG launches; the Crimson Desert graphics device block at launch required its own bypass procedure.
Here is the detail most guides skip: note when the error started. If the game launched once and then broke after a patch, NC Guard’s post-update signatures are the likely culprit — compare the file timestamps in the game folder against the patch date. A fresh driver is rarely the problem when nothing changed on your machine, but a freshly quarantined anti-cheat file explains everything.
