Independent guide · not affiliated with the DXVK project or Valve · downloads always link to the official GitHub

Try: d3d9.maxAvailableMemory, DXVK_HUD, GTA IV, Failed to create Vulkan instance

GAME · ASSASSIN'S CREED SERIES · UNTESTED BY US

Assassin's Creed games with DXVK

Origins and Odyssey are reported to be 64-bit Direct3D 11: copy x64 d3d11.dll and x64 dxgi.dll next to the game exe. AC1 to Revelations are reported to be 32-bit Direct3D 9 or 10, and Valhalla and later use Direct3D 12, which DXVK does not cover. These games use Ubisoft Connect, so read the online note first. We have run none of them.
Checked
2026-11-07
How we checked this
RECIPE · ASSASSIN'S CREED ODYSSEYUNTESTED · COMMUNITY DATA
EXE
game exe (name not verified) · game folder (reported)
Bitness
64-bit → x64
API
D3D11
COPYx64/d3d11.dllx64/dxgi.dll
DXVK
3.1.1 (untested)
Built-in profile
none
Conflicts
Ubisoft Connect overlay
ONLINE anti-cheat: do not use online
TESTED untested

The series at a glance

REPORTED
Assassin's Creed games and DXVK (reported values and DXVK's source; none run by us)
AC I to RevelationsDirect3D 9 or 10, 32-bitYesAC II: d3d9.deviceLossOnFocusLoss (from the brief, unverified)Bouncing image bug, issue 2249 (open when we checked)
AC III, IV: Black FlagDirect3D 11Yesd3d11.cachedDynamicResources = a (from our research brief; the 1.10.1 and 2.6 notes name both)None recorded
UnityDirect3D 11Yesnone knownNone recorded
SyndicateDirect3D 11Yesdxgi.customVendorId = 10de (profile for ACS.exe, from DXVK’s source)None recorded
Origins, Odyssey64-bit Direct3D 11Yesnone knownOrigins on AMD under Windows: users say 2.6.0 was the last good version (issue 5813)
Valhalla, Mirage, ShadowsDirect3D 12NoShadows: dxgi.enableDummyCompositionSwapchain = True (from DXVK’s source)Direct3D 12: see vkd3d-proton

Exe names, bitness and Direct3D version for each game: not verified by us. Use the Game Checker before copying anything, and do not list a game here as working until it has been tested.

Origins and Odyssey: install

  1. Download DXVK from GitHub

    Use the official release page only, and check the hash with the verifier on the download page.

    Check: You have dxvk-3.1.1.tar.gz.

  2. Open the x64 folder

    Assassin’s Creed Odyssey is reported to be a 64-bit game, so you need the x64 folder. DLLs of the wrong bitness do nothing and give no error (F05).

    Check: You see d3d11.dll.

  3. Copy d3d11.dll, dxgi.dll next to the game's .exe

    A Direct3D 11 game needs both d3d11.dll and dxgi.dll (F40); with only d3d11.dll the game fails to create its device (F06). Next to the game’s own exe.

    Check: d3d11.dll and dxgi.dll sit beside game exe (name not verified).

  4. Start the game and check

    DXVK writes <exe>_d3d11.log next to the game on Windows (F13). Turning on the HUD is the other check; see the HUD guide.

    Check: A log file appears next to the .exe.

To undo it, delete the DLLs you copied (F12): see the uninstall guide. The general steps, with the checklist and warnings, are on the Windows install page.

Both games have a built-in benchmark, which is the fairest way to test: run it without DXVK, then with, as on the performance page. A r/allbenchmarks post reports about +30% for Odyssey when CPU-bound; we did not reproduce that.

AC I to Revelations

These use Direct3D 9 or 10 paths, so the DLL set depends on which exe you run (x32; D3D9 needs d3d9.dll, D3D10 needs d3d10core.dll, d3d11.dll and dxgi.dll, per the DLL page). AC1 reportedly has separate DirectX 9 and 10 exes; we did not verify the names. Issue 2249 reports a bouncing-image bug (113 comments).

Unity and Syndicate

Direct3D 11, x64 DLLs (d3d11.dll plus dxgi.dll). DXVK’s Syndicate profile reports an NVIDIA vendor ID to the game (dxgi.customVendorId = 10de) so the game avoids a code path that causes trouble with AMD’s AGS library. That reason is from our research notes.

Valhalla, Mirage, Shadows

These use Direct3D 12, which DXVK does not handle: DXVK vs vkd3d-proton. DXVK still has a Shadows profile because the DXGI side matters under Proton.

Remove DXVK

Delete the DLLs you copied (F12).

What we have not tested

  • Any run of any game in the series: FPS, stutter and crashes are unmeasured.
  • Exe names, bitness and Direct3D version of each game.
  • The profiles for AC II and AC III and IV: not in our extract.
  • Whether the bouncing-image bug and the Origins AMD issue still apply.
  • Online and anti-cheat behaviour.

Check your own copy

The Game Checker reads your .exe on your device and tells you its bitness and Direct3D version. Our checker also flags files in the game folder that use the same name as DXVK’s DLLs.

Questions people ask

Does DXVK help AC Odyssey?

We do not know. A r/allbenchmarks test reported about +30% when CPU-bound; we did not reproduce it.

Which Assassin's Creed games work with DXVK?

Games using Direct3D 9, 10 or 11, reportedly AC1 through Syndicate, Unity, Origins and Odyssey. Valhalla and later use Direct3D 12, which DXVK does not handle.

Why does the screen bounce in AC1 or AC2?

Issue 2249 reports a bouncing-image bug with DXVK in the early games. We could not check its status.

Which DXVK version for Origins on AMD?

Users report 2.6.0 as the last good version on Windows (issue 5813). That is a report, not our result.

Do these games have anti-cheat?

We have not verified. They use Ubisoft Connect with online checks, so use DXVK offline only.

Sources

  1. DXVK source: built-in profiles (config.cpp at v3.1.1) · accessed 2026-11-07
  2. DXVK issue 2249: bouncing image in AC1 to Revelations · accessed 2026-11-07
  3. DXVK issue 5813: Origins on AMD under Windows · accessed 2026-11-07
  4. DXVK README at v3.1.1 · accessed 2026-11-07