DoubleYou

Try this: 1. Click the profile button in the toolbar 2. Click Create 3. Enter a name and select Default Game settings and OK 4. Ensure that Overwrite is empty. 5. Launch in this new profile without any mods and see if that doesn't remove the lag 6. Report back

On that note, I have already moved some things outside the Advanced tab. The ini tweaks I have moved into the Mod Information discussion under the Left Pane. I'm thinking of breaking out the Information pane into its own tab because of its importance.

I noticed an edit by Z wherein he has showed us it might be smart to make these articles go to subpages of the MO guide, linked to inside the Advanced section. This is a good idea, as the Advanced section is including quite a lot of content and difficult to navigate. Making subpages like this will help keep it organized.

What version of Mod Organizer are you using?

Basically, if it is a vanilla Skyrim bug, just run the game without using Mod Organizer. Go to the location, see if it is the same. It seems likely to be a vanilla Skyrim problem. If it is, either you will have to mod the thing into submission, or just go kill some draugr and forget about the glitchy graphics.

I'll have to evaluate it a bit more, but we probably can make this become focused on all games in general, rather than discussing it as Skyrim, and I see you have noted that. BTW, is it really 64 bits? Normally I hear people talk about 64-bit programs and 32-bit programs, or x86 and x64, not really "bits," but that is a minor thing. I revised the first paragraph slightly.

Does it happen in vanilla Skyrim? If so, you'll have tough luck fixing it.

I agree. Do a Brodual and not a Gopher.

That Sounds AWESOME! Sign me uP!PM sent Â

Perhaps not use those features?

Or you can just use the modlist.txt inside your profile in the profiles directory. Only thing is, that is normally backwards of your priorities. You can generally load up the csv file in Excel.

I think the reason why categories are somewhat strange is because Tannin has tried to make them applicable to all games, not just Skyrim.

I haven't actually installed or used the mod, but from Gopher's video, it does sun damage, with triple damage to undead, does the whole scare the draugr explosion thingy, adds a light effect so you can see in dark places that is almost brighter than a torch, is craftable up to Legendary, and is same damage rating as daedric sword.

Greek word kakos means 'bad' in old Greek like used in the New Testament. Don't know if it still carries that connotation in modern Greek.

I have several profiles that I use for various states in the game. Step 1 is my first profile. This is for the beginning of the game and includes the unofficial patches and various mods that should be loaded at the start of the game. After I exit Helgen, I load up the save with Step 2. This adds a bunch more mods that have more to do with gameplay, etc. This normally takes me to Riverwood. Then comes Step 3 profile, where I add most mods that have a MCM menu and then set those up. This takes me to Whiterun. Step 4 profile adds anything else, and that's pretty much complete. Step 5 is there to add experimental mods. I very much follow STEP! LOL.

It doesn't appear to get rid of the undead explosion. I agree that Dawnbreaker is quite underwhelming, but would recommend the no stagger version.

I try to keep my online identity as nonspecific and private as possible. That said, I'm in my early twenties, in college, love playing games, love playing with code, and enjoy all kinds of music. And that's about all you need to know :P

You shouldn't need to Revo Uninstall. The only registry keys made by Fallout NV wouldn't cause this (indeed there is very little other than the game files that it installs). From what you have said, it simply has to do with the 4GB patch not working or something. There has to be a reason, and I'm very sure a Revo uninstall isn't going to fix it.

If you load up Wrye Bash, do any of the esps (Requiem - Dragonborn, Requiem - Sic Patch...., RequiemDB - Sic patch) appear as being any color other than green? Are any of the masters out of order?

Nvm on the FalloutNV.exe. I just realized that unless you modified those, they never are put in the ini, and are just detected upon startup. Nothing wrong there. I think the problem lies somehow with the interaction between MO and the modified executable. I'll have to research this a bit more.

This normally happens to me when Wrye Bash decides that I don't need any esps activated except its own. I've learned to backup the loadorder.txt and the plugins.txt. Thankfully, I use BUM so putting it all back in the correct order isn't hard. It's putting all the esps active that I was using that is most difficult.

Python should be installed to default location, not ModOrganizer folder. While theoretically the 2.7.6 release candidate version should work, I'd personally wait until it is complete to update, or simply stay with 2.7.5 as it isn't broken.

Neovalen has stopped his previous method of altering the conflicting esp directly to a method where we create a single patch for the whole guide. Basically, load up your entire load order in TES5Edit and follow conflict resolution guide into create one big patch.

I'm going to have to attempt to reproduce the problem probably to be able to solve it. Perhaps the 4GB thing messes with the SteamAppID? What I'm wondering though, is why in your custom executables, you do not have FalloutNV.exe, and the script extender is marked as custom. They are supposed to be detected automatically and nonremovable. Try this: 1. Make a backup of ModOrganizer.ini onto your desktop or somewhere else safe. 2. Delete ModOrganizer.ini 3. Now load up Mod Organizer and see if you can't run the game.

You need to run Boss and Wrye Bash through Mod Organizer. See https://wiki.step-project.com/Guide:Mod_Organizer#tab=Third_Party_Programs