ENB Injector Query

[dubiousintent]

Remember, you have to launch the very first time after installing using "FalloutNV_launcher.exe" so the game detects your hardware and configures your "FalloutPrefs.ini". After that is done, you can run your "bat file" with ENB and 4GB patched "FalloutNV.exe".

 

Otherwise, please detail how you launch (paste your bat file in "spoilers") and I'll see if I can spot what is wrong.

 

-Dubious-

[Ragnarok101]

I have it set up to first launch the ENBInjector, then the FNV Launcher.

 

 

 

@echo off
cd "C:\Games\Steam\steamapps\common\Fallout New Vegas"
start ENBInjector.exe

cd "C:\Games\Steam\steamapps\common\Fallout New Vegas"
start FalloutNVLauncher.exe

exit

 

 

While enbinjector.ini looks like this:

 

[LIBRARY]
LibraryName=enbseries.dll

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

 

 

Also, it still doesn't work even if I launch 'manually' using the shortcuts I have in place...so I don't think it's the batch file.

Edited October 11, 2017 by Ragnarok101

[dubiousintent]

You don't really want to use "FalloutNVLauncher.exe" after the very first time. Use "FalloutNV.exe" in your bat file instead.

 

Check that you have the "Fallout.ini" and "FalloutPrefs.ini" files in your "Users" folder, and that they have the edits you made for ENB. (I'm concerned the "Launcher" may have replaced them with the "default" INI file.)

 

No need to change the "enblocal.ini" file.

 

FYI: You do not need to have two "cd" lines in your "bat file", unless they are to two different folders. The "cd" command changes the "default working directory", which remains in use until another is set. So the first line is all that is necessary.

 

You might want to replace the second "cd" line with a "pause" command instead. That will cause a prompt to "press any key to continue", which will buy time for the ENBInjector command to finish initializing before the game is launched. I don't know that is a problem, but it's worth testing out.

 

If that does prove successful, you could replace the "pause" with a "sleep n" command (use "sleep --help" to see the description and options) which will delay the script for "n" seconds so you don't have to hit a key for it to proceed.

 

-Dubious-

Edited October 11, 2017 by dubiousintent

[Ragnarok101]

You don't really want to use "FalloutNVLauncher.exe" after the very first time. Use "FalloutNV.exe" in your bat file instead.

 

Check that you have the "Fallout.ini" and "FalloutPrefs.ini" files in your "Users" folder, and that they have the edits you made for ENB. (I'm concerned the "Launcher" may have replaced them with the "default" INI file.)

 

No need to change the "enblocal.ini" file.

 

FYI: You do not need to have two "cd" lines in your "bat file", unless they are to two different folders. The "cd" command changes the "default working directory", which remains in use until another is set. So the first line is all that is necessary.

 

You might want to replace the second "cd" line with a "pause" command instead. That will cause a prompt to "press any key to continue", which will buy time for the ENBInjector command to finish initializing before the game is launched. I don't know that is a problem, but it's worth testing out.

 

If that does prove successful, you could replace the "pause" with a "sleep n" command (use "sleep --help" to see the description and options) which will delay the script for "n" seconds so you don't have to hit a key for it to proceed.

 

-Dubious-

 

After some experimentation, I think it's the batch file (even after editing as you stated) causing the problem.

Launching manually causes no problems and the ENB works as designed.

 

Further experimentation reveals that, for some reason, launching from desktop shortcuts is what is causing the problem. Maybe Win10 puts up an overlay?

Anyway, launching anything from the desktop shortcuts I created via Windows Explorer causes the bug (and causes the 'can't be changed because open in another program' problem), so I'm assuming it's that.

Do you know anything that might have caused this?

[dubiousintent]

I don't have Win10 (still on Win7), so I am not up on all it's nuances. But long ago I adopted the habit of not putting most shortcuts on the desktop (which is a special "Users\<AccountName>" folder), but under other folders I personally created instead. Once "libraries" came along I created a "Public" library (see "Understanding Libraries" article) and then added the folders where I separated my various shortcuts by general function (e.g. a separate folder for "games", one for "apps", and one for "most frequently used (MFU)") to it. I have a separate folder where I have all my "scripts" such as "batch files" (which makes it easier to find and edit them). That way I avoid all the unexpected shenanigans MS inflicts upon the behavior of it's "special" folders, especially with regards to what it considers "executables" (which include "bat files"). My guess would be that you have things sitting on your "desktop" (a "special folder") and that is the root of your problems.

 

You do realize that "Windows Explorer" itself is a program, and if you have a file or it's properties open in Explorer, then you will get that message if you try to use anything else with it? You can use the tool "FileMon" from SystemInternals to determine exactly which programs have the file open at the time.

 

-Dubious-

[Ragnarok101]

I don't have Win10 (still on Win7), so I am not up on all it's nuances. But long ago I adopted the habit of not putting most shortcuts on the desktop (which is a special "Users\<AccountName>" folder), but under other folders I personally created instead. Once "libraries" came along I created a "Public" library (see "Understanding Libraries" article) and then added the folders where I separated my various shortcuts by general function (e.g. a separate folder for "games", one for "apps", and one for "most frequently used (MFU)") to it. I have a separate folder where I have all my "scripts" such as "batch files" (which makes it easier to find and edit them). That way I avoid all the unexpected shenanigans MS inflicts upon the behavior of it's "special" folders, especially with regards to what it considers "executables" (which include "bat files"). My guess would be that you have things sitting on your "desktop" (a "special folder") and that is the root of your problems.

 

You do realize that "Windows Explorer" itself is a program, and if you have a file or it's properties open in Explorer, then you will get that message if you try to use anything else with it? You can use the tool "FileMon" from SystemInternals to determine exactly which programs have the file open at the time.

 

-Dubious-

I am aware about Explorer, but what you're saying about Windows thinking of the desktop folder as something special makes sense and is probably the root problem.

 

Thanks for your help, but I think I'll stick to launching things manually for now, given Win10 being temperamental.

 

Don't get Win10. Seriously. I only have it because it came with my new laptop, and the whole thing is basically a tablet/touchscreen-meant OS, and is riddled with bloatware you can't eliminate.