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
https://imgur.com/a/t5OjA63
Or prevent the Nahimic service from starting automatically, because you won't need it purely for having your audio working: https://steamcommunity.com/app/883710/discussions/0/1743358239836205250/?ctp=13#c3658515990058969401
Yes, you can try renaming the files through Windows first, but it may say that you can't do that because they're in use by other programs (injected into other programs).
If that's the case, use the lockhunter app on those two files. It detects which programs have been injected by them and you can use it to close all affected programs and become able to rename the two DLLs.
You don't need these files purely to have audio output. If you rename the files and you decide you want to put them back, you can do that by renaming them to their original names.
I added the following lines to the file "C:\ProgramData\A-Volute\A-Volute.Nahimic\Modules\Scheduled\Configurator\BlackApps.dat":
Sidenote: their "support" is shocking. Seriously, they removed the option to report a problem on their support site. Like, say, an incompatibility with some other software. Already reported by the developer. And they just removed the issue discussion, and the ability to actually make issues.
Export a DWORD symbol "NoHotPatch" in your executable to prevent Nahimic from initializing.
No messing with any of Nahimic's config files necessary, the first thing it does when its DLL attaches is call GetProcAddress ("NoHotPatch") on the parent module and checks to see if it's flagged.