Greg

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.

I just started downloading it as well. ModDb is a bit annoying in that it pops up a download frame and then throws an "error" over the top saying the server is overloaded and to try again later or to try another mirror -- but the link to other mirrors is hidden behind the error. Even when I click other mirrors, it takes me to the home page instead of to the specific mod page I want to download. Just seems to be a poor design choice. I had to close the download frame and click the Download button again (with a bit of a pause between) several times to finally get the file to start downloading. Just saying because we may want to add a note about this if we add SRO back into STEP.

https://www.youtube.com/embed/e-LE0ycgkBQ

I have used spaces in the paths in the past with Mod Organizer, Loot, etc. installed in a folder with a space in it and it made no difference.

You should also disable Papyrus logging because this isn't a crash log and can cause other issues due to script lag.

Probably just something wonky going on with Steam making the game think Steam wasn't running is my guess.

As I understand it, the general format/idea was originally used in Oblivion Mod Manager then completely revamped into the FOMOD format for Fallout Mod Manager. It was later included in Nexus Mod Manager and hasn't changed much since then. I think Mator says it best, though.

I just compared in-game and this screenshot matches my STEP Extended profile.

Upload your images to an image-sharing site like https://postimage.org/ and then include a link to the image in your post here. To include the link, click the Image icon in the toolbar and paste the link into the popup.

6. It makes more sense to use the latest LOOT standalone than to embed a version that's quickly outdated.

If you are using Mod Organizer 1.3.11 with Skyrim, you should see Unmanaged: Dawnguard, Unmanaged: Hearthfires, and Unmanaged: Dragonborn provided dawnguaard.esm, hearthfires.esm, and dragonborn.esm exist in Skyrim's Data folder (usually Steam/SteamApps/Common/Skyrim/Data). If you don't see them anywhere in the left pane, click Settings (the wrench/screwdriver icon) and uncheck Hide Inactive ESMs/ESPs in the last tab. If you still don't see them, ensure Filter at the bottom of the left pane is blank.

You might consider Simple Multiple Followers. The link is to the forum topic discussing the mod and you'll see a link to the mod on Nexus in the first post.

You need to run Skyrim Special Edition once from the launcher so it adds the configuration to the registry and creates the default ini files.

Fortunately this mod is included in the STEP Compilation so it shouldn't effect any users.

Can you tell us how you fixed this in case someone else runs into this same issue in the future?

For what it's worth, I do not consider this a valid stability test of the game. Basically all this does is to floor the engine loading and rendering assets (meshes and textures) and pegs the Papyrus engine as you run through trigger points so you cannot definitively say the issue is with the mods installed, any of the patches, or any assets. The Bethesda engine is not designed to hold up under this stress so this "stability" test doesn't prove anything. If this test crashes the game using 4K landscapes but doesn't crash using 2K landscapes, does it prove the 4K landscapes are causing a problem during a regular playthrough?

This is my load order as exported from LOOT, although you really need to pay attentions to the mods installed (and the options selected for these mods) in the left pane.

I hope you're right that this might prod Intel into making a new leap in the next generation, but I imagine this depends on whether AMD is finally creeping close to Intel's performance. Intel has been conservative since AMD was so far behind.

My first suspect is to disable any antivirus/malware detection applications and any "gaming" apps that might use overlays in the game. These have been known to cause issues of the weird and wacky sort like this. Have you tried deleting everything in the Data folder and verifying cache to get "clean" copies of the vanilla masters and archives? I would also use BethINI to ensure the INI files are cleaned and optimized.

No, you can use XP32 Maximum Skeleton Extended instead without any issues.

Set the global priority to 97 (basically dropping the last four zeros).

Are you using the x86 version of the Java Runtime Environment? You'll get this error if you use the x64 version of the Java Runtime Environment from Mod Organizer.

I thought we already had NSUTR for No Snow Under the Roof, but apparently not.

If you are using Mod Organizer, you need to use the x86 version of the Java Runtime Environment. The x64 version of the Java Runtime Environment is not compatible with Mod Organizer's virtual file system.

You may need to ensure all updates have been installed with Windows Update before the Universal C Runtime can successfully install. Apparently this installer can be a bit of a beast unfortunately.