tighearnachcreag

I've reinstalled it with MO in a bunch of different ways, I've installed it with NMM, I've isntalled it with FOMM, and I've instaleld it manually. No dice. archiveinvalidation is active, and the archiveinvalidation bsa is firs tin the bsa list. When I say "present in my load order", I mean when ILO is ticked. The game runs fine if ILO is installed but not active.

I wish I could say I was really stupid and hadn't, and then fix this easily, but yes, it is checked.

As the title says, my computer seems to not like Interior lighting overhaul. Every other mods has been installed and merged and bashed tagged and cleaned and so forth, but it seems no matter what I do, if Interior Lighting Overhaul - Core.esm is present in my load order, regardless of how I install it, or what mods are running with it, NEw Vegas will refuse to run at all; when I launch it with ILO in the load order the process starts, and then nothing happens. The process seems to run normally in the background, but the game doesn't actually start, and after a minute or so Windows will tell me that FNV isn't working, and I can either wait for nothing to happen, or close it. Does anyone here have any idea what might be causing this, and how I can fix it?

Definitely a mods issue, as deactivating a few that I figured would be performance heavy fixes it. Now I just need to fiddle around till it works. Edit: Specifically, it appears that for some reason Interior Lighting Overhaul is causing this. Pity, I guess I won't be using the mod then.

I already said that I already did this. Tried, didn't help.

Yes (I've even tried the older version, just in case), and yes. I kind of figured it was something mod related, although I wasn't aware that texture load could be a factor. https://www.mediafire.com/view/i4edoh2r34e640j/plugins.txt https://www.mediafire.com/view/vc8kfal3ez7wcpv/DxDiag.txt I could run a roughly similar mod load out with, IIRC, the exact same graphical mods, back when I was using fallout mod manager, so while my computer isn't very powerful, I'm not sure why it would suddenly be unable to run it

I've tried that, and it doesn't seem to do anything. FalloutMO.exe appears in my NV directory, and runs briefly, according to Task Manager, but the game doesn't actually start, which is the exact same thing that happens without the the argument, just with Fallout.exe instead of FalloutMO.exe

I have it hooked up through the Mod Organizer, but when I try to get it to run, nothing happens. It works fine when I use my lightly modded (bug fixes+UI mods) or not modded at all profiles, or without Mod Organizer entirely, but not with my heavily modded Mod Organizer profile. I'm not sure what to do to get it to work, since the only advice I've been able to find has been to add "-laaexe .\FalloutMO.exe" to Mod Organizer's 4GFNV access, and that doesn't seem to work for me.