ENBoost troubles (injector version)

[VAULTRENEGADE]

I've been trying to get the injector version of enboost to work with no luck. I've had no issues with the wrapper version in the past, however I can't seem to get the injector version to hook propperly as it stands. (The wrapper version is not an option due to my intended ussage of the application alongside VorpX).

 

I'm just trying to figure out what I'm doing wrong at this point. I've coppied enbhost.exe, ENBInjector.exe, enbinjector.ini, enblocal.ini, and enbseries.dll into my FNV root directory. I am currently using the 4GB patcher (newer/ non- .exe version should auto hook), as well as NVSE. No text appears in the corner of the screen upon boot, nor is the configuration menu available in game.

 

And yes, I'm activating the injector application prior to booting NVSE through FOMM.

 

My enbinjector.ini is as follows:

 

 

[LIBRARY]
LibraryName=enbseries.dll

[TARGETPROCESS]
ProcessName0=nvse_loader.exe
ProcessName1=FalloutNVLauncher.exe
ProcessName2=FalloutNV.exe

Thoughts?

Edited May 28, 2019 by VAULTRENEGADE

[dubiousintent]

I never used the injector version. Checking the web did not turn up any mentions of it with the "FNV4GB Patcher" version. But one recommendation which seems reasonable was to add the "FNV4GB.exe" to the ENBINJECTOR.INI file under the "[TargetProcess] section. (Edit: On second thought, that should not be needed as that file "patches" the default game EXE and does not run after that.) And that you need to run the Injector with Administrator privileges (because "injecting" means "modifying" the original files at runtime).

 

* Did you install Steam to it's default location? If so, please see the wiki "Installing Games on Windows Vista+" article for why the original default Steam behavior of installing games to the "C:\Program Files" or "C:\Program Files(x86)" folder tree was bad (they learned better, and don't do that any more); and why "disabling UAC and running as Administrator" is NOT sufficient, with instructions how to move it. This is the single most important thing you can do to fix and protect yourself against problems in the future. (And an "injector" mod is going to look like malware under those circumstances.) As much of a PITA as that is, it's never going to be any easier than now. System updates often cause issues with games installed to these folder trees. Please see the 'Restoring to "Vanilla"' section of the wiki "FNV General Mod Use Advice" article as well.

-Dubious-

[VAULTRENEGADE]

 

I've been trying to get the injector version of enboost to work with no luck. I've had no issues with the wrapper version in the past, however I can't seem to get the injector version to hook propperly as it stands. (The wrapper version is not an option due to my intended ussage of the application alongside VorpX).

 

I'm just trying to figure out what I'm doing wrong at this point. I've coppied enbhost.exe, ENBInjector.exe, enbinjector.ini, enblocal.ini, and enbseries.dll into my FNV root directory. I am currently using the 4GB patcher (newer/ non- .exe version should auto hook), as well as NVSE. No text appears in the corner of the screen upon boot, nor is the configuration menu available in game.

 

And yes, I'm activating the injector application prior to booting NVSE through FOMM.

 

My enbinjector.ini is as follows:

 

 

[LIBRARY]

LibraryName=enbseries.dll

[TARGETPROCESS]

ProcessName0=nvse_loader.exe

ProcessName1=FalloutNVLauncher.exe

 

I never used the injector version. Checking the web did not turn up any mentions of it with the "FNV4GB Patcher" version. But one recommendation which seems reasonable was to add the "FNV4GB.exe" to the ENBINJECTOR.INI file under the "[TargetProcess] section. (Edit: On second thought, that should not be needed as that file "patches" the default game EXE and does not run after that.) And that you need to run the Injector with Administrator privileges (because "injecting" means "modifying" the original files at runtime).

 

* Did you install Steam to it's default location? If so, please see the wiki "Installing Games on Windows Vista+" article for why the original default Steam behavior of installing games to the "C:\Program Files" or "C:\Program Files(x86)" folder tree was bad (they learned better, and don't do that any more); and why "disabling UAC and running as Administrator" is NOT sufficient, with instructions how to move it. This is the single most important thing you can do to fix and protect yourself against problems in the future. (And an "injector" mod is going to look like malware under those circumstances.) As much of a PITA as that is, it's never going to be any easier than now. System updates often cause issues with games installed to these folder trees. Please see the 'Restoring to "Vanilla"' section of the wiki "FNV General Mod Use Advice" article as well.

 

-Dubious-

 

Good suggestions, but I've already exhausted those options. Steam is installed to a separate SSD; UAC disabled by default. Unfortunately running it as administrator yielded no results. I'll have to tinker with it some more tomorrow- maybe there's something wrong with my .ini settings. I don't know.

[dubiousintent]

Forgive me if I appear to be belaboring the point, but "disabling UAC" is not a solution. This is a commonly misunderstood function.

 

Disabling "User Account Control" (UAC) only stops Windows from prompting you to grant "administrative" credentials to an application that the system says must have a "UAC elevation". Disabling UAC does not automatically then enable the permission for such applications. Instead, (for all intents and purposes) it automatically denies them. (Please read this MS article on how it works in Win10. The basics have been there since the inception of UAC with Vista.)

 

This is why I say you have to move the game out of the system folder tree in order to bypass the problem. This older 32-bit game did not have to contend with UAC at all at the time it was designed. The system folder protections are not going to allow your ENB injector to modify game files without "UAC elevation".

 

-Dubious-

[VAULTRENEGADE]

Forgive me if I appear to be belaboring the point, but "disabling UAC" is not a solution.ÃÂ This is a commonly misunderstood function.

ÃÂ

Disabling "User Account Control" (UAC) only stops Windows from prompting you to grant "administrative" credentials to an application that the system says must have a "UAC elevation".ÃÂ Disabling UAC does not automatically then enable the permission for such applications.ÃÂ Instead, (for all intents and purposes) it automatically denies them.ÃÂ (Please read this MS article on how it works in Win10.ÃÂ The basics have been there since the inception of UAC with Vista.)

ÃÂ

This is why I say you have to move the game out of the system folder tree in order to bypass the problem.ÃÂ This older 32-bit game did not have to contend with UAC at all at the time it was designed.ÃÂ The system folder protections are not going to allow your ENB injector to modify game files without "UAC elevation".

ÃÂ

-Dubious-

The root directories for both Steam and FNV are located on my "E" drive, so I don't think that's the problem. After doing some more research, it looks like the injector application suffers major compatibility issues with certain versions of Windows 10. The cause of this is unclear, making a solution dificult to ascertain. A certain user recommended installing the June 2010 directX runtimes that were absent from the default redists list, but this didn't change anything unfortunately. I'm curious to know whether there's been ANYONE at this point who's been able to get the injector version working with windows 10 Edited May 28, 2019 by VAULTRENEGADE