Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
mine doesn't.
using -gamepadui is currently tied to using bin/dxvk_d3d9.dll instead of the normal d3d9.dll
I had the same issue and dxvk_d3d9.dll was the "faulting module" in Windows Reliability Monitor. if this is the same for you, this workaround would help.
I was able to get around this by renaming dxvk_d3d9.dll,
creating a symlink to SYSWOW64\d3d9.dll,
renaming the new symlink to dxvk_d3d9.dll to take the place of the original dxvk_d3d9.dll
(ThirteenAG's d3d9-wrapper is a working alternative to creating a symlink)
I couldn't simply copy the dll from SYSWOW64, because when I did, Steam would not detect a graphics api and keep using the desktop config for the controller. it was like HL2 was a launcher and Steam was waiting for the game to start.
Can you show me the steps of doing all these shenanigans to solve this problem? I didn't quite understand what you said.