red46

Hello, Throughout the last couple days I've followed the STEP guide for new Vegas and managed to get almost everything working correctly, almost because I have this annoying LOD issue I can't seem to fix: In game, on far away mountains that have rocks on them, they will be displayed in that fashion when I am far away, once I approach them however and the LOD switches, they will look perfectly fine. I've followed those instructions verbatim: I've downloaded the resources archive installed and checked it, before I even attempted to run FNVLOD for the first time, I've also placed it above the JIP NVSE plugin on the left side (I have also tried placing the output of FNVLOD above it with no success), on the right side in the "plugins" tab. The auto sorting places the "FNVLODGen.esp" file next to last, just above nevada skies. I am not even using that many plugins, LOOT says I am up to 47 so I don't think its that loading issue that occurs when too many plugins are loaded either. Unchecking the output archive of FNVLOD in MO, makes the issue disappear. Anyone has any suggestion on how to fix that?

Hey, over the past few days I decided to replay new vegas and so I reinstalled it along with some mods, I then stumbled across the step guide for it and became aware of MO, downloaded it and it ran without problems, however due to half of my mods being installed manually plus, my game being installed in Program Files (x86) which was causing issues with UAC, I decided to start fresh. I uninstalled the game and wiped any leftover with CCleaner and then reinstalled it in the root of my C: hard drive. Then, I downloaded the MO 1.3.11 manual installation file and placed the "ModOrganizer" directory in the root of the New Vegas installation, I also downloaded the 4gb patcher and placed that in the new vegas root directory as well. Then, following the instruction on the STEP guide I proceeded to set up the various external executables to launch through MO (FNVEdit,NVSE,FNVLOD,wrye flash, etc) once that was said and done I decided to test everything so far was working correctly. I first opened the new vegas launcher by using FalloutNVLauncher.exe, the game auto-detected the graphic settings and then I ran the game, everything worked great. I then ran the launcher through MO to check the video option were consistent and they were. So, I tried to run the game by launching the 4gb patcher through FO, crash. The screen gets black, then I can see the borders of a window in the top left corner and then in the middle of the screen the message fallout NV stopped working. Tried to start NVSE through MO, again crash in the same way as above. It also crashes when I try to start the vanilla fallout exe. The only thing I am able to run through MO is the launcher and even that results in a crash when I click play. I am running windows 10 x64 pro and this happens wherever I run MO normally or as admin. If I run the exes without using MO everything works perfectly. At this point my installation of the game is as clean as it could be. There's no mod installed whatsoever but what comes with the ultimate edition and NVSE 5.0b2. I am pretty sure as well that it has little to do with my previous installation as I cleaned it thoroughly including any leftover registry key. Checking MO log it appears that the issue is with the NV.exe, looking at the MO log the last line is this: Windows Exception (c0000005). Origin: "C:\Fallout New Vegas Ultimate Edition\FalloutNV.exe" (a087e5). Last hooked call: unsigned long __stdcall GetFileAttributesW_rep(const wchar_t *) but I can't figure out as until yesterday on my old installation, the game worked brilliantly and the exe was obviously the same. I've uploaded the MO log here for review: https://pastebin.com/Lykf2RYa Thanks in advance for any help resolving this.