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
That sounds like you have Special K installed for that game within its game folder, so you'd have to remove the dxgi.dll or d3d11.dll file from the folder the game executable resides in.
As long as those DLL files remain, when you launch the game SK will start alongside it and auto-create the My Mods folder.
Right next to the install button, there's an uninstall button.
Clearly not enough guides on how to unistall this program properly, anyway thanks for the help.
Local installs of Special K won't "move" to other games, and for a global install it's as easy as uninstalling it through Windows' Programs and Features list.
The one time we've had a case of a local install of Special K being applied for another game than the one the user applied it for was when the user had GShade installed. GShade works by symlinking its DLL file to game folders, and when the user installed a local copy of Special K to the game folder, they inadvertently replaced GShade's original DLL file with Special K... So basically instead of having GShade apply for multiple games, they managed to have Special K apply for multiple games...
And in those situations there's really nothing we can know or even be aware of, as SK is working as intended and it's ultimately GShade's reliance on symbolic links that causes the whole situation to begin with.