I am not reproducing. The game starts fine for me on Windows with dxvk without any modifications.
Anyway there isn't any indication that dxvk can do anything here
The simple solution is to backup and delete the d3dcompiler_47.dll from the client folder
No, that's wrong. d3dcompiler_47.dll has a different job than DXVK. d3dcompiler compiles HLSL to DXBC and DXBC is what DXVK (or your D3D11 driver) works with.
So deleting d3dcompiler_47.dll can only cause problems.
dxvk-nvapi is obvious for RTX users to get DLSS and DLAA back
Yes, and I'm pretty sure that only works on Linux.
Hi, i use Win10/11 and was sad that DXVK would not work on my machine, and wanted to understand why.
The reason is most likely that some games insist on loading dxgi.dll from C:\Windows\System32. When you try to use DXVK with those games, they end up with d3d11.dll from DXVK and dxgi.dll from Windows and those two DLLs are not compatible with each other. Unfortunately there's nothing you can do about that.
DO NOT replace DLLs in System32 with DXVK ones! That would just break your Windows OS.
i didn't say that TESO will not start with the dxvk dlls placed in its client folder. The game will just ignore dxvk because the compiler is too old. you will not be able to get the hud of dxvk running or see any log files build.
Wine does bypass the integrated old compiler dlls since 2018 btw.
The mentioned fallback to the compiler dll in system32 works flawless, but the launcher will place the old dll just back, so you will need to replace it to get a permanent cure.
I do understand that DXVK can't do anything about it, so i'm sorry i was bothering you.
kind regards
The game will just ignore dxvk because the compiler is too old.
Once again, this has nothing to do with it.
d3dcompiler_47.dllx2 2026-05d3d11.dllx1 2026-05dxgi.dllx1 2026-05
Hi, i use Win10/11 and was sad that DXVK would not work on my machine, and wanted to understand why.
So i searched from every possible way to find the cause of the invisible error.
The simple solution is to backup and delete the d3dcompiler_47.dll from the client folder, wich leads to eso reaching into my windows/system32 folder and using the newest version of it, wich is from 2025.
I later found an old post regarding wine or proton mentioning a newer and compatible version of that file got integrated into wine i think.
dxvk-nvapi is obvious for RTX users to get DLSS and DLAA back
and for all others optiscaler could be a thing to get FSR