Greg

I may be mistaken on this, but this looks somewhat like a shadow glitch and your shadow settings in skyrimprefs.ini are somewhat odd to me. Have you tried using BethINI to establish known good ini files to see if this solves the problem?

If you are using Mod Organizer 1.3, you can use the Manage Archives feature to load assets in BSAs even if they don't have an associated plugin or master. If you are using Mod Organizer 2, you may need to extract the files from BSAs that don't have an associated plugin or master.

STEP 2.10 recommends ELE_Light_v0_95c_Only IL STEP Specific (in old files) that does not have any UDR or ITM records. I briefly looked at ELE_Lite_v0_95e_Only IL STEP Specific and xEdit removes 197 ITM records, but these all modify the XCIM image space so I don't know whether these should be considered ITMs or not. I'll have to defer to one of the experts like TechAngel85 or zilav on this.

Are you installing the correct file? If you click the link in the guide on STEP Optimized Vanilla Textures to get to the Nexus mod page, click the Files tab, and scroll to near the bottom of the page to find OPTIONAL FILES. You should be download and install either "STEP Optimized Vanilla Textures - Performance Version 1.2" or "STEP Vanilla Optimized Textures - Standard Version 1.2" depending on your system. This mod just installs the optimized textures and does not have an FOMOD. It sounds like you may be trying to install the "STEP Compilation Installer" under MAIN FILES and this should be installed when you get to the Patches section of the guide.

If I'm not mistaken, I think the GOG version already has the 4GB patch applied.

There have some discussions on this by the MO2 devs and I don't think they've found a reliable workaround for it yet. I seem to recall the issue may be that obseloader or something is completing before the hooking process can even start, but this happens only with the Steam version. I seem to recall it works fine with the retail and GOG versions of Oblivion.

I usually run the game launcher to create the appropriate registry and ini settings first to ensure everything is setup and ready to go. If you are using Mod Organizer 1.x or Mod Organizer 2.x in portable mode, copy the entire Mod Organizer folder to your new PC. If you are running Mod Organizer 2.x in instance mode, you'll need to copy the Mod Organizer folder and %AppData%\Local\ModOrganizer folder. After this is finished, edit ModOrganizer.ini and ensure all the paths are correct. This include gamePath in the General section, and binary, arguments and workingDirectory settings in the customExecutables section. I also suggest running LOOT once on its own so it downloads the current master list.

My first guess is Windows 10 just because Windows 10 updates are always breaking something or antivirus software is interfering with the virtual file system. My first step would be to open the Mod Organizer folder to verify usvfs_proxy_x64.exe, usvfs_proxy_x86.exe, usfvfs_x64.dll, and usvfs_x86.dll are all present. If these are missing restore them from the ZIP file and add an exclusion to your antivirus software. If these are present, right click ModOrganizer.exe in Windows Explorer and click Properties. If you see an Unblock button or checkbox, click it to unblock Mod Organizer and click OK. One of the later Windows 10 updates does not allow the virtual file system to work if ModOrganizer.exe is blocked. If this doesn't solve your problem, add an exception for Mod Organizer to your antivirus software. Also ensure that you are not running any of the tools (like LOOT) or the game as administrator because Windows does not allow non-admin processes to hook or interact with admin processes.

I assume you mean A Modern Morrowind. if this is the case, you might try the Discord link near the top of the guide since the authors of this guide apparently don't browse the forums much.

No, this is not quite correct. Papyrus scripts are always interpreted by the game engine and are always stored in a BSA archive or as a standalone .pex file. SKSE DLLs files basically expand the capabilities of Papyrus by adding new commands that can be called from a Papyrus script.

Moved to Support and Troubleshooting / General Scripts in a BSA are interpreted by the Papyrus interpreter in the game engine. DLL files are compiled to machine code (so they are not interpreted) and usually extend the scripting ability provided by SKSE to add additional commands and such that can be used from Papyrus scripts.

It looks as if the discord link in the guide is your best bet. I went over the revision history of the Morrowind guide and see that it's created and edited by DassiD and gigan2, but they haven't been on the forum in a while.

If I'm not mistaken, I think that limitation applied only to 32-bit DX9 games on Windows 8 and 10 (before it was fixed in 10).

You way want to review the INI Tweaks section in the Clear and Present Danger guide that links here.

Skyrim is in C:\Program Files (x86) so you'll run into a lot of UAC issues. It's best to install Skyrim in a folder that's not subject to UAC issues.

I think you need Automatic Archive Invalidation checked, but do this to double check. Open Profiles, click the profile you are currently using, and ensure Automatic Archive invalidation is checked. The layout of the dialog makes it look as if this is a global setting, but it really applies to the currently selected profile. I assume you are using Mod Organizer 1.3.x, so do you have the "Have MO manage archives" checkbox in the Profiles tab (right pane) checked and are all of the BSA files checked? Do you have a "Fallout - Invalidation.bsa" at the top of the archive tab?

I can completely relate to this. I started using discord as much as I could to keep up with Mod Organizer development and a few other things, but it really started eating into time that I don't have to spare and the time zone differences didn't help much. I finally just had to shut down discord to get back to work and family.

Are you using the latest Mod Organizer 2.1.5 on Nexus? The reason I ask is because this version fixes a lot of download issues with Nexus. You can also browse through any later dev builds in #builds on the Mod Organizer discord server to see if any of the 2.1.6 builds may fix issues you are experiencing.

As far as I am aware, you can't run two instances of Mod Organizer at the time same.

I wouldn't obsess over it... these things happen and it hasn't caused the universe to crash yet. If you include links to mods or images that reveal the naughty bits, just add a note that the link is NSFW so people know what to expect.

I added NSFW just above the link to hopefully alert time travelers from the future.

You can post the images on an external file or photo sharing site and include the link to the images in your post.

Mod Organizer 2 works fine with Skyrim Legendary Edition.

SKSE plugins are not shown in the right pane or in LOOT so this behavior is completely normal. To get SKSE and SKSE plugins working properly, you need to install SKSE binaries into the Skyrim or Skyrim Special Edition folder (where skyrim.exe is located). You can follow the instructions in the STEP 2.10 guide to install SKSE.

Thanks for the pointer the prerequisites, berndaroy. I remember one of the options in CCleaner bricked Mod Organizer 2, but I couldn't remember specifically which option did that. Event logs... Hopefully if I forgot it again I'll remember it's clearly documented here in the prerequisites page.