Skyrim and Oblivion with DXVK: edition by edition

Which edition do you have?

Skyrim SE and AE

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.

DXVK’s profile for SkyrimSE.exe sets one option:

ENB has a history here: GitHub issues 865 (Skyrim SE with ENB freezes before the title screen, 68 comments) and 2033 are user reports, and the DXVK 3.1.1 notes in our research mention an ENB shader crash fix (we could not read it). ENB uses the same DLL names as DXVK, so choose one or chain; see conflicts. We claim no Community Shaders compatibility: it is untested. One user report (issue 5885) describes a 30% loss on Windows with Skyrim SE; we have no numbers of our own. Test yours with the five-step method.

Skyrim LE (2011)

A 32-bit Direct3D 9 game, so x32\d3d9.dll beside TESV.exe (F38). The 32-bit address space limit applies: see VRAM and memory. ENB again uses the same file names.

Oblivion (2006)

Also 32-bit Direct3D 9. A depth flicker is reported in issue 3918; we could not check its status. Oblivion Reloaded, a graphics mod that hooks Direct3D 9, collides with DXVK’s d3d9.dll: pick one or chain (not tested).

Oblivion Remastered

Reported to run on Unreal Engine 5 with Direct3D 12, which DXVK does not handle. Proton uses vkd3d-proton for it; see DXVK vs vkd3d-proton.

Remove DXVK

Delete the DLLs you copied (F12).

What we have not tested

• Any run of any edition: FPS, stutter and crashes are unmeasured.
• Community Shaders and ENB compatibility.
• The LE and Oblivion profiles and the Oblivion depth flicker.
• Whether DXVK is better or worse than native Direct3D on your GPU.
• Oblivion Reloaded and other mods.

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.