Steam installeren
inloggen
|
taal
简体中文 (Chinees, vereenvoudigd)
繁體中文 (Chinees, traditioneel)
日本語 (Japans)
한국어 (Koreaans)
ไทย (Thai)
Български (Bulgaars)
Čeština (Tsjechisch)
Dansk (Deens)
Deutsch (Duits)
English (Engels)
Español-España (Spaans - Spanje)
Español - Latinoamérica (Spaans - Latijns-Amerika)
Ελληνικά (Grieks)
Français (Frans)
Italiano (Italiaans)
Bahasa Indonesia (Indonesisch)
Magyar (Hongaars)
Norsk (Noors)
Polski (Pools)
Português (Portugees - Portugal)
Português - Brasil (Braziliaans-Portugees)
Română (Roemeens)
Русский (Russisch)
Suomi (Fins)
Svenska (Zweeds)
Türkçe (Turks)
Tiếng Việt (Vietnamees)
Українська (Oekraïens)
Een vertaalprobleem melden
But its not accurate, you are changing DX12 Dlls to run in DX11 mode. The issue that is affecting most of us, is EAC which means unreal engine Easy Anti-cheat. It has nothing to do DX11 or DX12. and actually the second widely known step about renaming Elden ring executables you reference is to bypass EAC, which is separate besides the DLL risky work-around.
The thing is you should not be posting fixes on steam forums around modifying system Dll's and advertizing it where peoples computers may become compromised.
I've tried a monstrous amount of solutions these past 2 weeks and could not get past the white-screen issue until I did what was written in this post. Many thanks!
It actually has to do with DX for a lot of people. For me for instance, I tried every fix out there, including starting the game without EAC, and it still crashed on the first white screen while launching. The only thing that made it work was with the DXCPL emulator thing, with the "forcewarp" function on. Except I couldn't play the game as it was running 4 fps or something like that. So that cleary was a DX issue. Which was confirmed by this fix as now the game runs perfectly (although obviously in offline mode).
Also, what are the risks exactly with swapping those DLL files ? Could someone be more specific ?
This was my issue.
Using DXCpl to "Force WARP" allowed me to get past the white screen and enter the game, albeit with very bad performance. EAC wasn't the issue.
And this DX12 dll replacement fix worked very nicely.
Head over to the following path on your PC:
C:\Program Files (x86)\Steam\steamapps\common\Steamworks Shared\_CommonRedist\vcredist
You should see the following folders:
2012\vc_redist.x64.exe
2013\vc_redist.x64.exe
2019\vc_redist.x64.exe
Go to the C:\Program Files (x86)\Steam\steamapps\common\Steamworks Shared\_CommonRedist\DirectX folder path.
Next, run the DXSETUP.exe file to reinstall/update DirectX.
Reestart your PC to fix the issue.
I don't understand your instructions.
Step 1) Uninstall every Microsoft Visual C++ Redistributable you have installed.
Step 2) Head over to the following path on your PC:
C:\Program Files (x86)\Steam\steamapps\common\Steamworks Shared\_CommonRedist\vcredist
You should see the following folders:
2012\vc_redist.x64.exe
2013\vc_redist.x64.exe
2019\vc_redist.x64.exe
In Step 2) i found these folders and exe files.
What am I supposed to do with these exe files?
Double click on them and install.
Why are we dropping strange files into system32 anyway? This is a bad idea and Steam thinks so too.