Greg

Have you tried disabling your antivirus software temporarily to determine whether it is locking the files?

All I'll say on this topic is that Nexus is not the place to have an intelligent, civilized discussion and I doubt it ever will be.

Please post your request in a new topic. This topic is about the MipMap - Reboot mod and has no bearing on your request.

If you look inside the Mod Organizer folder you'll see the profiles folder. You can elect to store the downloads and mods folders elsewhere in the configuration, but the profiles folder is always in the Mod Organizer folder.

I've been using this on a test playthrough since I created the topic and haven't had any issues with it.

These are just size variations for the same mod so this topic should be sufficient to cover both mods.

Agreed. I've been using this in one of my testing profiles and it looks really good.

This is how I do it and I think it's a lot cleaner and less confusing when profiles don't share a significant number of mods. The obvious disadvantage is that it requires more disk space because mods used in both setups aren't shared as a common mod.

If you mean using profiles in Mod Organizer, it's fairly straight-forward but you need to ensure any generated files are stored as separate mods in each profile. Generally the bashed patch in one profile is unique to that profile and can't (or shouldn't) be used in another profile. Looking at this from the Skyrim Legendary Edition (the old x86 version of the game) persective, FNIS generated animations, DynDoLOD generated files, bashed patch, reproccers (like Dual Sheath Redux) are all unique to a given profile so be sure new profiles you create don't use existing versions of these from another profile.

You've added quite a lot of mods on top of STEP Core, so you need to load all the mods into TESVEdit and check for anything that's overriding or conflicting with Improved Closefaced Helmets. I see you've already posted on the Improved Closefaced Helmets topic on Nexus, so scroll up above your post and carefully read the post from Nazenn.

In your case it should be 6E, although I should point out that 6E hex is 110 decimal. If you look in the right pane of Mod Organizer (the plugins tab), it shows the mod index in hexademical so you should see 6E here as well..

The one reason I might consider keeping this mod is that it allows a first person view while riding dragons and horses instead of being forced into an asinine third-person view, but this is somewhat of a limited feature since I don't ride horses and there is only one place in the game in which the player can actually ride and control a dragon and this sadly feels like a poorly designed mini-game that I try to get through as quickly as possible so I can get on with the game. Realistically the only reason I use it is because it's in the guide and I need to have the full guide installed for comparisons and screenshots. The build in which I actually play the game uses STEP Extended as a base without this mod, and I think it makes sense to move this into a pack at some point for users that want the first-person view while riding.

This is usually defined by the font itself so you might try using the vanilla font or one of the other alternative fonts on Nexus. I don't know of any other way to change the size of the font.

I think your best bet may be to use Skyrim Performance Monitor to watch VRAM usage to see it might be hitting the VRAM cap while loading all the meshes and textures. I suspect you'll see some stuttering in some areas while walking/sprinting if you're hitting the VRAM cap. This is typically more of an issue with Windows 8/8.1/10 due to the 4GB VRAM cap where Windows 7 can expand VRAM well beyond 4GB.

Not to be a contrarian, but behind is the wrong preposition to use here. Below, beneath, or after are more appropriate.

Note that STEP prohibits sharing mods without the explicit consent of the mod author.

You might compare the placement of Skyrim Realistic Overhaul in the STEP 2.2.9 Guide versus the placement of mods in the STEP 2.2.9.2 Guide to get an idea where it might be placed. In general it was placed between Static Mesh Improvement Mod and HD Misc in Conflicting Graphics. I agree with TechAngel85 on the 4K textures with the caveat that my eyes are old as dirt and I'm not a graphics artist so I don't see a lot of blemishes that others might see. I just let the 20- and 30-somethings do the looking for me. :-)

Interesting... I wonder what this might entail? I haven't really been keeping up with the SSE updates, but I hope this includes a fix for the issue Sheson reported a while back assuming it hasn't been fixed yet.

I've been searching and download a variety of mods that retexture clutter most of the day and I haven't noticed any issues with Nexus so far.

All but one of the disabled mods are merged into the bashed patch so you do not need to enable these mods. WM Trap Fixes.esp is the only mod that needs to be enabled after you create the bashed patch.

There may be another way, but you can add a link to your existing page and save. Once the changed page is rendered, click the new link to create the actual page. [[User:Greg/SomeRandomPage|Some Random Page]]

Just let LOOT place it where it needs to go.

I noticed that you are providing a list of assets in the mod analysis section of each mod. I realize this may be asking for a bit much, but do you have any plans in the future to allow searching for mods that contain a named asset (e.g. mesh or texture)? Right now I'm searching Nexus for mods that contain retextured clutter and it's somewhat of a bear because Nexus search isn't all that great and mod authors don't always list everything that's included in the description. While I was going through some mods in Mod Picker, I couldn't help but think how easy it might be if I could get a list of all mods that contain say basket01.nif or barrel01.dds. I know it's definitely feasible using a search engine like Lucene or Elastic (based on Lucene), but I imagine the effort will push this on down the road quite a bit. I know... I know... but I can dream, can't I?

I think he meant torches.

I'm not familiar with Amahi specifically, but this seems to be somewhat along the lines of Microsoft's older Windows Home Server that I used for a while along with the storage pool technology. The "storage pool" basically writes files to a "random" drive in the pool and may also store a duplicate copy on a secondary drive. The basic issue with this approach is that the directory structure is stored in a "file" so if you lose a drive, you have to run a recovery tool to recover the structure. The files are still on disk and (depending on how the storage pool works) may be accessible from Windows Explorer, but it can be a bit complicated to recover everything since you'll have to weed through all the duplicates (assuming everything is correctly duplicated across more than one drive). The other choice is to build your own desktop PC (using say a mini case/motherboard or a standard tower case) with Windows or FreeNAS or to purchase a diskless NAS and to add drives as you can afford them. I originally used a Netgear 4-drive NAS that was a piece of crap and migrated to a Synology DiskStation five years ago that has been solid as a rock. If you decide to use a RAID array, I recommend going with one disk redundancy if you have two to four drives in the array or two disk redundancy if you have more than four drives. The DiskStation shines in this area because it can dynamically rebuild the array as you add disks, although I think FreeNAS can do this as well. True RAID is a pain in the keester since it may require tearing down and rebuilding the array. The choice of drives with a RAID array is important as well. Don't use desktop or media drives in a RAID array since they won't hold up well, but you don't need expensive "enterprise" class drives either. I use WD Red drives since these have much the same benefit as enterprise drives with a 5400-RPM rotational speed so the cost is reasonable. Disk speed isn't all that critical for a NAS since network bandwidth is the real limiter. It certainly doesn't hurt to let the drives sleep when they're not needed. A big disadvantage with RAID is that the array is at risk when a drive dies so it's a good idea to keep at least one spare drive on-hand. Regular monitoring the health of the drives is really important as well so you can detect potential drive failures before they fail.