DoubleYou

Yes, Firefox does sync. Almost all browsers sync nowadays.

I can't really see how that would be helpful in MO.

Or it could be your video card graphics settings.

Switch to Firefox. That's what I did.

I'm assuming you are referring to the 255-character string limit thing. Nitpick fixes that issue, and so does Mod Organizer, which is why we removed Nitpick (see some relevant discussion on this thread). I have never witnessed an issue where MO failed to load a BSA using its methods. If such an issue exists, I would question the BSA's integrity before I would question there being a problem with MO's BSA-loading mechanism.

No problems should be caused.

/Fixed.

Sounds like Creation Kit files. I have them too from Creation Kit.

Is it not possible to 4gb patch the executable directly and not have to worry about launching an additional 4gb injector? I've never really bothered about it since I never had trouble with it, but seems it could be advantageous if possible.

So, now that The Elder Scrolls Skyrim: Goat Simulator has become a reality, I got another idea. You know how that when you die in Skyrim, you respawn at your last save? Well, let's make a rationale to that, but not the same as the No Death Mod or any of the other ones that change death. Imagine this: You are the dovahkiin. You can absorb dragon's souls. You can become a werewolf. You can become a vampire. You can pledge yourself to any number of daedra. Guess what? The daedra all want you! So when you die, they all get in a big fight over who will claim you in the afterlife. Hircine wants you to hunt forever. Mephala wants you to become her evangelist. Molag Baal wants you to wreck havoc and collect souls for him. Boethiah wants you to turn the world upside down. Nocturnal wants you to be a statue guarding her sepulchre. And so on! So, whenever you die, at random, a quest thingy transports you to this place where all the daedra are fighting and whatnot. In this havoc, somehow time shifts, and you get sent back to your last save. You would need to remove autosave functionality for this probably. Then there would be the ways you could change this, and not respawn. Perhaps because you're a vampire, you turn into a vampire lord and devour them. Or perhaps, if you have defeated Alduin, Alduin storms in and devours the daedra, you kill Alduin, and somehow get transported to your reward in Sovnguard. Or perhaps you could accept one of the daedric offers. Or perhaps you could become reincarnated as a dragon. Or a goat.

And.... someone actually created this mod! https://steamcommunity.com/sharedfiles/filedetails/?id=322474805

Yes.

AFAIK MO is compatible with XP, but really, you should upgrade your OS.

This mod is merged into the STEP Patches, so if you use any of them, this file is not needed.

I have checked. Never did it find anything. My teeth don't ache

Am I to understand that we should be giving manual installation instructions for fomods? Is that not even harder to understand?

The permissions on the mod page were strictly not to reupload it if my memory serves me right, because I checked it immediately after it went down using a Google-cached page. Files themselves don't appear to have any mention of permissions. Might have to drop it.

A lot of misinformation in this thread, but thankfully Tannin has dispelled most of it. First, C# installers are supported by NCC, and although NCC did have errors in a number of old versions, it works correctly currently AFAIK. Secondly, installation of .NET 4.5 does not provide support for all versions of .NET. For some older application you will also have to install or enable the older versions including 3.5, 2, 1.1, which are all allowed to be enabled at the same time. I was rather certain that Mod Organizer uses version 4+, but it might actually be 3.5. If you are managing Skyrim, I believe 3.5 is installed automatically for you since it is one of the redistributables it gives you. Now the reason for the error most likely is a permissions issue and not .NET although I could be mistaken. The reason why Nexus Mod Manager will work for you is it forces you to run it as administrator, which places a huge band-aid on the permissions problem. Most likely if you ran Mod Organizer as administrator, you wouldn't have any trouble with the installation. This, however, we do NOT recommend, as it can become a security issue. I believe that NCC extracts its files to %localappdata%/temp (copy-paste into Windows Explorer), so I can only guess that it is there that the permissions issue lies, although sometimes it finds more eccentric hiding places.

Skyrim Memory Patch 3.0 is the name of the memory patch that is integrated within SKSE that you use. There is no conflict between SKSE and ENB over memory. The Memory Patch was integrated into SKSE since SKSE already injects code into Skyrim game executable, and the patch needed to be injected into it as well. It modifies the TESV.exe on the fly so to speak to have the patch which is injected using code withing skse_steam_loader.dll which is activated by the skse.ini file settings noted on the Skyrim Script Extender wiki page. Running SKSE will then inject the memory patch within the steam loading part and will be able to call a larger stack of memory and not crash. ENB fixes the problem of texture loading over 3.1gb by creating a separate process to share the load. It is injected through DirectX, so no conflict. Completely different memory problem. Your issue is the memory patch is set up right. You need to create or add the skse.ini as shown on the wiki page. When it is working, Memory Blocks Log will indicate 512 and 256 instead of 256 and 256. Most likely your skse.ini is a text document, in which case you need to remove the txt file extension. Edit: Okay, the other guess is maybe somehow the patch is failing to inject. Most have reported adding the -forcesteamloader argument to SKSE fixes that.

No, we do want the Greatsword sheathes. It adds some that the other mod doesn't.

The mod in my signature sorts it correctly.

They do not do the same thing. Use both.

Exactly, but STEP doesn't use all vanilla textures.

Normals that do not fit the texture used may look glitchy.

1. A 2. B 3. B 4. A 5. B 6. B 7. B