I know from personal experience that installing too many mods, removing them, messing with NVSE, and then throwing in body/texture replacers can cause issues no matter how careful you are. Steam errors need to be addressed at the Steam forums. Nexus would probably assist you a little better, but from your description it sounds like you improperly installed a shitload of mods, and Steam is fucking up somehow, maybe your executable was changed, so Steam won't recognize it anymore. Honestly this isn't the best place for these sorts of questions. NVSE loader can work with the 4GB enabler too, you just have to set the path in the options, of course I use Nexus Mod Manager so it may be slightly different. Your files are probably so fucked up from installing so many different mods improperly. Pro Tip: Install one mod at a time, always read the readme documents, use Nexus Mod Manager, uninstall everything, and start over from scratch. I'm not sure what problem you are having, since you appear to have borked everything up in an attempt to fix it. With non steam version I would have no fckin problems. There are 0 mods up in the game atm, becaouse of the NVSE problem, so mods couldnt cause it and Its a Steam error, so that would make no sense. I watched youtube videos, tried google and I didnt find anything that would help me.
I had like 60 mods up, I have 50 hours in the save. Now my FNV4GB enabler works, but NVSE doesnt and I cant play. Back, then my 4gbenable did this, I dont know how I fixed it, maybe with the SteamApId thing, but that doesnt work at NVSE loader. I managed to fix that somehow and now I get steam error Application load error P something, there were error 5's and error 80's too, but now Its error P. First, when I started NVSE It was something like error 740, this happened if I wanted to start with FOMM too. I reinstalled Fallout NV 2 times already. Like 1 week before I had like 60 mods working and, so NVSE was working, but, becaouse of body replacer head/body mismatch I somehow fucked up the game, while tried to fix it and, then I tried to reinstall the whole game.
0 kommentar(er)
