Jump to content

Photo

Can't get ENB's to work at all.

enb mod organizer 2 mo2 fallout new vegas fnv viva new vegas

  • Please log in to reply
10 replies to this topic

#1
jhx96

jhx96

    Journeyman

  • Premium Member
  • 37 posts

So I followed the Viva New Vegas guide (https://vivanewvegas...b.io/index.html), minus a few hardcore survival things and added some other mods not listed in the guide, but avoided most said mods to avoid in the guide. The exception being ENBs, cuz simply put, I want a better looking new vegas. I've also tried NVReloaded + the viva new vegas NVGE preset for it in addition. But for some reason now, MO2 just immediately crashes to desktop upon launching New Vegas with the d3d9.dll file installed, even without NV Reloaded installed. And I've tried using the injector version, the game launches but the enb never applies. I've searched high and low for a solution, but nothing seems to work. 

 

Weird part is I was able to run enbs on this computer back in February.
 
Also as a side note, using NVR 3.2.0 for some reason causes a weird glowing blue texture on the ground. However switching to 1.3.0 seems to have resolved that issue.
 
Here's my load order:

Spoiler

 

Specs:

CPU - AMD Ryzen 7 3700X 8-Core Processor

GPU - NVIDIA GeForce RTX 2080 Ti

RAM - 16.0 GB

OS - Windows 10

Attached Files



#2
M48A5

M48A5

    Resident poster

  • Members
  • PipPipPipPipPip
  • 8,965 posts

What do you have installed that does not appear in the load order?



#3
jhx96

jhx96

    Journeyman

  • Premium Member
  • 37 posts

I have nvse_loader.exe, the 4gb patcher, Improved Lighting Shaders, JIP LN NVSE Plugin, JohnnyGuitar NVSE Plugin, New Vegas Anti-Crash, New Vegas Tick Fix, New Vegas Heap Replacer, and Mod Limit Fix.



#4
dubiousintent

dubiousintent

    Resident poster

  • Premium Member
  • 8,471 posts

I get the impression you are trying to use both ENB and NVGE at the same time.  Last time I looked into it, those two were incompatible as they are two different approaches attempting to do the same graphics "thing".  Try removing one or the other.  If you did so and are still having problems, recheck your various "shaders" for compatibility with your primary graphics enhancement solution.

 

-Dubious-



#5
jhx96

jhx96

    Journeyman

  • Premium Member
  • 37 posts

Uninstalled both NVGE and Improved Lighting Shaders, still immediately ctd's.



#6
dubiousintent

dubiousintent

    Resident poster

  • Premium Member
  • 8,471 posts

Back to "basics" then.

 

You should always start troubleshooting from any error messages you can see.  (They are your best "clue"; and why they exist at all.)  Reporting such messages accurately is an essential first step.

Anytime the game "Crashes to the Desktop" (CTD) it's typically going to generate an error message in the Windows Eventlog because the game engine was not able to predictably handle the error.  Please see the "Windows Error Messages" section of the wiki "How to read most Bethesda game error logs" article.

Logs generated by the game itself (not Windows) are found in the game folder, where the "FalloutNV.EXE" file is located.  They generally have the ".log" file extension, or a filename with "_log" in the name and a ".txt" extension.

A "CTD" is a "fatal" error, meaning the program/game did not know how to handle the error, nor how to proceed from that point; and shutdown to let the Windows Operating System (OS) take over again from the "desktop".  The only thing worse is the so-called "Blue Screen of Death (BSoD)", which means the OS itself encountered a similar fatal error and entire computer has to be "rebooted" ("reset" switch or "power off-for-10-seconds-and-on-again")  to return to function.  DO NOT attempt to resume the game again from the point of a CTD, as your system memory is in an unpredictable state and make cause "save game" corruption even if it does get past the point where it crashed before.  Reboot first.

"NVAC - New Vegas AntiCrash" error log entries are described on the "Description" page.  This an important log for "in-game" errors.  Some are intended to assist mod authors; while others are there to help "you, the player" trying to resolve a problem.  You are interested in the entries which are NOT automatically handled successfully by NVAC, and records which do NOT begin with "00" (which are in the vanilla game files and not typically going to be fixable by yourself).  Key entries to look for are the following "letter codes":
* "e" entries are Exceptions handled specifically by NVAC's targeted code changes
* "h" entries are exceptions identified Heuristically by NVAC's "global" exception handler, sometimes handled unsuccessfully.
* "m" entries are "Middle of nowhere" exceptions, sometimes handled unsuccessfully.
* "ñ" entries are Null instruction exceptions, sometimes handled unsuccessfully.
* "n" entries are Null pointer call exceptions, sometimes handled unsuccessfully.
* "o" entries are stack Overflow exceptions, usually handled unsuccessfully.
* "q" entries are program self-termination information; these are effectively crashes.
* "u" entries are Unhandled exceptions reported from the Unhandled Exception Filter; these are crashes (and the NVAC author wants to hear about them).
* "v" entries are unhandled exceptions reported by NVAC's "global" exception handler; these are crashes.
* "w" entries are informative, relaying exception information as it passes through New Vegas's final exception handler.
* "x" entries are critical errors in Windows exception data; these entries should never occur.
* ":" entries are output from OutputDebugString calls.
* ";" entries are output from the game's own error checking.
Other codes may be of interest, but are not things the player is likely to be able to resolve,  They are useful for informing the author of the mod to aid them in fixing their plugin.  In particular, pass along the:
* "_" entries are informative, relaying that NVAC was loaded and the base address of various DLLs
* "!" entries are informative, relaying human-readable text for the user entries.
Any error codes found in the log but not listed on the mod "Description" page should be reported to the NVAC comments page.

'Expression Error: SYNTAX' is not uncommon, even in vanilla without any mods loaded.  These are basically "typos".  Such errors are reported by NVAC but ignored. Those lines of script code do not get executed, but also are not "fatal" to the game.  They are the sort of thing mods like "Yukichigai Unofficial Patch - YUP", "JIP LN NVSE", "JohnnyGuitar NVSE", "lStewieAl's Tweaks" etc. are designed to fix or supplement if possible.
---
"Windows Exception code: 0xc0000005".  The "Faulting Application" is often the victim of another program rather than the actual culprit, making it virtually impossible for the user to trace the source.  In at least one instance it appears to be caused by VWD/LOD files that had not been regenerated (when caught by NVAC as "DISABLED _LOD_ERR").  Any recent update since the last time it was working correctly is suspect, as are viruses even if you have anti-virus (AV) running.  Run AV from multiple sources when checking for infections.  There are a number of free online scanners on the internet (though they are all going to try to sell you their services after the first time).

You may need to exclude FNV from "Data Execution Protection (DEP)" and configure " Windows Defender Exploit Guard (WDEG)" (or Microsoft's "Enhanced Mitigation Experience Toolkit (EMET)" for Win7).  Please see "Issue - NVSE - fails to load after update KB4058043 to Win10 FCU v1709" under the 'Solutions to Starting the game problems' section of the wiki "Fallout NV Mod Conflict Troubleshooting" article.

Try turning off any unnecessary background processes, such as "anti-virus" or "anti-malware" programs (unneeded if you are running your game in "offline" mode once you have scanned since the last connection), multiplayer "overlays" like "OverWolf" (this is single-player after all), the Steam overlay, etc., at least on a temporary basis to see if they are interfering.  There are also tools (often called "Game Boosters") to help you determine "unnecessary when offline" Windows services you can temporarily shut down.

It is also possible that any recent change to your mods (such as updates) or your existing "load order" (such as additions or removals) has caused a corruption of the current save game file.  Try going back to a save game from before the problem started.  Often starting a "new game" with a vanilla test character can help confirm if the problem lies in the current load order.

-Dubious-



#7
jhx96

jhx96

    Journeyman

  • Premium Member
  • 37 posts

There's no windows system error that pops up. I go to launch FalloutNV.exe from MO2 executables dropdown menu, it loads up a black screen with a tiny window also featuring a black screen in the top left corner, then after a few seconds it closes back to desktop with MO2 unlocked. The only overlay I have on is the steam overlay, but whether it's on or off doesn't really seem to make a difference.

 

And I'm not seeing any errors in any of the .log files. Unless I'm blind/stupid which is likely, but here's my nvac.log:

Spoiler

 

does a capital "M" letter code mean anything?



#8
dubiousintent

dubiousintent

    Resident poster

  • Premium Member
  • 8,471 posts

The "black screen with a tiny window also featuring a black screen in the top left corner," is a "command prompt" window, indicating that a "command line program" has been launched.  A "command line program" is technically different from a "windows" program and the OS automatically detects that and launches them differently. Which indicates to me that you have something other than a normal game configuration.  That is likely something to do with how you are telling MO2 to run FalloutNV.exe, but that would best be addressed by that support team.  Most likely it is something as simple as a "syntax" error or a "typo" in the command.

 

You can try posting an image of how you have configured FNV in the "MO2 executables dropdown menu" and I will see if I can spot anything, but I caution you that I do not use MO/MO2 and can only deal with something obvious.  Which is why I recommend you bring the problem to that support team.

 

As for the NVAC log, I don't know any more about it's codes than are listed on the description page.  But given the "command line prompt" window, I assume your problem occurs before the game actually launches, so worry about NVAC errors later on.

 

Finally, Windows "system errors" don't always "pop-up" messages.  Most are logged to the system "EventLog" without other notification, so you have to manually search them out and compare the date-time stamps to known events (like a game CTD).  Please accept that a CTD will always create an eventlog entry.  It is considered a "serious" event.

 

-Dubious-



#9
jhx96

jhx96

    Journeyman

  • Premium Member
  • 37 posts

Ok well, this is what it's giving me in the Event Viewer and my executable tab:

Attached Files



#10
dubiousintent

dubiousintent

    Resident poster

  • Premium Member
  • 8,471 posts

I would put both the "Binary" and the "Start In" field paths in double quotes, i.e. 'Binary: "D:\SteamLibrary\steampapps\common\Fallout New Vegas\FalloutNV.exe" ' because of the folder named "Fallout New Vegas".  If MO2 assumes quotes, then it will tell you.  But assumptions are a dangerous practice and I doubt it.

 

"Windows Exception code: 0xc0000005".  The "Faulting Application" is often the victim of another program rather than the actual culprit, making it virtually impossible for the user to trace the source.  In at least one instance it appears to be caused by VWD/LOD files that had not been regenerated (when caught by NVAC as "DISABLED _LOD_ERR").  Any recent update since the last time it was working correctly is suspect, as are viruses even if you have anti-virus (AV) running.  Run AV from multiple sources when checking for infections.  There are a number of free online scanners on the internet (though they are all going to try to sell you their services after the first time).

You may need to exclude FNV from "Data Execution Protection (DEP)" and configure " Windows Defender Exploit Guard (WDEG)" (or Microsoft's "Enhanced Mitigation Experience Toolkit (EMET)" for Win7).  Please see "Issue - NVSE - fails to load after update KB4058043 to Win10 FCU v1709" under the 'Solutions to Starting the game problems' section of the wiki "Fallout NV Mod Conflict Troubleshooting" article.

Try turning off any unnecessary background processes, such as "anti-virus" or "anti-malware" programs (unneeded if you are running your game in "offline" mode once you have scanned since the last connection), multiplayer "overlays" like "OverWolf" (this is single-player after all), the Steam overlay, etc., at least on a temporary basis to see if they are interfering.  There are also tools (often called "Game Boosters") to help you determine "unnecessary when offline" Windows services you can temporarily shut down.

It is also possible that any recent change to your mods (such as updates) or your existing "load order" (such as additions or removals) has caused a corruption of the current save game file.  Try going back to a save game from before the problem started.  Often starting a "new game" with a vanilla test character can help confirm if the problem lies in the current load order.

But it might be as simple as needing the double quotes as pointed out above, so try that first.

 

-Dubious-


Edited by dubiousintent, 02 December 2020 - 12:21 PM.






Also tagged with one or more of these keywords: enb, mod organizer 2, mo2, fallout new vegas, fnv, viva new vegas

Page loaded in: 1.159 seconds