Majorman

Never mind, I had the injector version up an running. Here is some info to the other unfortunate guys out there , that have the same problem as me: to install the Injector version you only need enbhost.exe, ENBInjector.exe, enbinjector.ini, enblocal.ini, and enbseries.dll from the bundle. In enbinjector.ini write: [LIBRARY] LibraryName=enbseries.dll [TARGETPROCESS] ProcessName0=FalloutNV.exe ProcessName1=FalloutNV_Launcher.exe This is missing in the ENBoost STEP Guide.

My specs are in the signature. I've been trying to get the ENBoost v0.278 running on a new rig with Win 10 x64 (build 14393). Installed the DX June 2010 Runtime. Got only the enblocal.ini, enbhost.exe & d3d9.dll in the FNV root folder. Enabled HDR. Disabled Steam Overlay. Set the E:\Steam\steamapps\common\Fallout New Vegas as an exeption in Avast, applied the recommended STEP tweaks to the enblocal.ini, then booted the game through MO (I'm using the FalloutNVpatch, so I start the game through FalloutNV.exe) - and I get a black screen of death. Music is still playing though and I don't get an immediate CTD (so I made a little progress since last time). ENB Patch v0.203 however works like a charm. AMD driver is 17.2.1. I guess d3d9.dll is the culprit, as deleting it gets the game up and running. I've read that AMD is no longer supported n the ENB forums. I've also read that I might not an ENBoost at all. Can I do something else? PS. It's the wrapper version I'm using.

Hi there. The answer to your questions is: do not untick any merged mods on the left pane of MO unless specifically instructed to. To reduce the plugin count of Advanced Recon Merges follow the instructions provided in the FNLE guide: As a rule of thumb, whenever you merge mods with the "Copy General Assets" ticked, you can safely untick the mods after the merger is complete. Whenever you merge mods with the "Copy General Assets" unticked, you do not disable the mod on the left pane of MO, but you move its .esps to "Optional ESPs" in order to reduce the count. You can use "Copy General Assets" (ticked) only when mergin small mods wihich add no additional recources (like meshes, textures, BSAs) to the game.

As I am a total ENB noob, but am also struggling with it, I can recommend reading https://forum.step-project.com/topic/11348-fnv-quirks-and-possible-fixes/?hl=%2Benboost before someone more experienced comes to answer. According to the post linked, SMAA should work for FNV.

Another question, if I may: any reccomended system specks for F&LNV? I was wondering whether going for the mid-res texture packs wherever possible will grant me stable performance. The question is also valid for mods adding lots of NPCs in interior cells (like Populated Casinos). I know the game is old, but my CPU (Core i5 7400 @3.0 GHz) might bottleneck the performance and the 5+ hours of adding mods thus far will go to waste.

Fallout 2 is my personal #1. Main reason why: I'm old! Now seriously: main reason: funniest NPCs and best-quality dialogues of all Fallout games thus far! Typhon, Renesco "the Rocketman" or the chess-playing radscorpion were all great and hilarious, to name a few. All NPC had individuallity and effort put into them. The pop-culture references were also great. The game never took itself too seriously, which I find is a minor flaw of FO 3 and a MAJOR flaw of FO4. Also FO2 had a distinct RPG-feel and was primarily a game about choices: it was impossible to max out every single stat and/or skill, so plaaning ahead and careful perk picking were important. Battles were also very tactical and did not rely on reflexes, which suits me better, as I am not that good at reflex-heavy games (like FPSs). That being said, I relly enjoyed FO1, FO3 and espcially FO:NV, which I view as the spiritual successor of Interplay's Fallout series. I haven't played BoS and I don't plan to play FO4 in the near future, as I don't like the direction it has taken.

All right! I've been through the UI section and everithing works well together (for now)! Thanks, EssArrBee, for the fantastic guide! I found no comments on Sortomatic Safehouses, so I decided to give it a shot. I could not gather info on weather it is compatible with latest version of Sortomatic, but I guess I'll figure it out once I get a safehouse. Didn't like the total number of plugins it creates, though (7 in total). No info on Nexus either. I only hope I can delete if it doesn't work correctly. Any ideas on that? I will also go for the FNV Uncut but only after I get to the weather mods. Thus I can uninstall it if it causes trouble. I will provide feedback on Uncut 8/RWLE compatibility.

Is this the correct topic for guide suggestions? I would like to point out that Nexus now hosts a Merged Version of FNV Uncut: https://www.nexusmods.com/newvegas/mods/61121 I think that might be listed in the next update of F&LNV for those that prefer not to create a Merged plugin themselves. Also, has anyone tested FNV Uncut 8? I was looking for a mod that replaces the vanilla low-res, low-quality intro and was wondering if this mod has conflicts with anything in the F&LNV. Lastly, any thoughts on Sortomatic Faction Safehouses? Sortomatic is already on the guide's list, but this mod strangely enough isn't. Are there any bugs/conflicts caused by it? link: https://www.nexusmods.com/newvegas/mods/41238/

@FuzzRocket - Use the following BethINI guide: https://wiki.step-project.com/User:Kelmych/Fallout3_INIs It's made for Fallout 3, but the ini-tweaking works the same way. After all both games use the same engine.

Thanks, Double You, but I think my previous post was a bit unclear. I had already ran BethINI at the point I installed ENBoost. Thus I suspect ENBoost in screwing up my MO profiles, as everything was OK beforehand. Anyways, if anyone has ever had the same issue or will have it in the future, please try the following: 1. Re-apply the 4GB Patcher - delete the patched FalloutNV.exe and run the patch once again. 2. Switch profiles in MO and hope that this will refresh the path to FalloutNV.exe in the Tools tab. Manually "re-building" the path did not work in my case. I did the steps above simultaneously, so no idea which one actually did the trick. Bottom line is, ENBoost is somewhat sensitive, so always try to run the game after installing it. The ENB Patch v0.203, which is not mentioned in the F&L guide, solves some issues with d3d9.dll, so use it if you have CTDs. Then hope it runs with MO. Always have at least 2 different MO profiles just in case. Well, of to installing other MODs I go!

I've been following the F&L Guide up to the part where I had to install ENBoost. Everything was peachy, NVSE working, the 4 GB patcher apparently working and through BethINI I edited the .inis. The most noticeable effect of the tweaking was the quick boot of the main menu. However, after installing ENBoost and getting it to work (evident by the text in the main menu) it seems to have screwed up the INI tweaks (and maybe other things as well). Thus far there are 3 issues currently: 1. When running FalloutNV.exe through MO it always runs the launcher. When Running FallountNV.exe from the installation folder, it runs normally. 2. INI tweaks apparently do not work - booting the main menu is slow. I also feel that the resolution has changed to the default one 1280:720 (please tell me how I can check that in-game?). 3. Around 50% of the time whenever I exit FNV, I have a performance issue - the game stays listed on the taskbar for around 2 minutes. Can someone help? As a side note, if anyone is having issues installing ENBoost under the latest generation AMD video cards (I have an RX 460) - download the ENBoost patch as well.

I would say yes. According to its author it fixes/corrects many wrong entries in the INIs. For me the best features are the automatic backups and the option to set up the files differently for each MO user, thus allowing to work around a bit and find the best configuration for your system.

Thanks! All I needed to do was to manually point BethINI to the correct profile. Now it works like a charm.

Hi all, I've been following the F&L in New Vegas modding guide and reached the ini-tweaking part. There I ran to the issue where BethINI will not work correctly with MO 2. To be precise, it "sees" existing MO profiles, but not the location of MO on my disk (displays “ERROR†instead). Simply pointing to that location and then manually selecting the profile I want to modify causes BethINI to restart and “revert to defaultâ€. I’ve read that a new version of BethINI should solve the issue, but Nexus will need some time to upload it. Is there a workaround I can use in the meantime? What will happen if I generate new .inis avaible to all profiles (I keep a backup of vanilla inis just in case)?