Greg

It's available now so it was probably hidden while the mod author uploaded the newest version.

The blue color indicates you are missing the texture for the mesh and I think the pink means you are missing the mesh. The tricky part is that the record in the plugin tells the game which mesh to use and the data in the mesh tells the game which textures to use. For the missing texture issue, you may have a mod installed (such as Static Mesh Improvement Mod) that overwrites the mesh and provides new textures without touching the data in the record.

You may want to report this to the xEdit developers: https://github.com/TES5Edit/TES5Edit/issues

You should rebuild the bashed patch and make a new Dual Sheath Redux patch any time you change the load order. You should rerun FNIS any time you change mods that affect the skeletons or animations. You should rerun DynDOLOD any time you change mods that affect the landscape or terrain.

The steps you've outlined above should work fine and I think the only reference you'll find is Weapon\0009F25D SkyforgeSteelDagger if I'm not mistaken. After you've removed the aMidianBorn_ContentAddon master and aMidianBorn_ContentAddon plugin from your load order, you may want to load everything into xEdit once more to resolve the conflicts with SkyforgeSteelDagger. In my load order, AOS overrides Weapons & Armor Fixes Remade so you may want to carry forward the changes from Weapons and Armor Fixes Remade into the patch. I think this is primarily the two additional keywords and the DATA - Game Data value should be 110.

The way I understand it, using uGridsToLoad=7 with DynDOLOD is overkill so you might consider backing that down to uGridsToLoad=5.

The June 2010 runtimes linked in the guide you you linked in your original post is the correct version you need to download and install. When you install the runtimes, it should install into the default location. I think this is C:\Windows\System32 and/or C:\Windows\SysWOW64 by default. Do not install the runtimes into the Steam or Skyrim folder because it won't work. When you download ENBSeries, you'll need to extract the files in the WrapperVersion folder into the Skyrim folder (the same folder with skyrim.exe and skyrimlauncher.exe). You should also note that this includes a d3d9.dll. This is a "fake" DirectX9 DLL that hooks into Skyrim.exe and then loads the real d3d9.dll from the system folder. Edit enblocal.ini in the Skyrim folder and ensure UsePatchSpeedhackWithoutGraphics=true is in the [GLOBAL] section near the top of the file. This basically enables the memory optimizations and disables the new graphics stuff. You can change this to false later if you decided to install an ENB preset. For now, keep it simple. Also read the guide on the settings you should change in enblocal.ini since some of these depend on your graphics card. When you run Skyrim, you should see red text at the top saying graphics has been disabled (although I don't remember the exact text). This is perfectly normal and lets you know ENBSeries is working.

Windows 10 comes with DirectX 12 installed, but I don't think the DirectX9 runtime files are installed and this is required for ENBSeries so install it. Also keep in mind that Skyrim was released way back when DirectX 9 was the new kid on the block. We've since gone through DirectX 10, 11 and 12 but Skyrim is still set in its ways. If you are using Skyrim Legendary Edition, click the link provided and scroll past the release notes. At the bottom of the page you'll see a lot of older versions listed, and you'll want the newest version. These all look like plain text but these are links so click v0.389. You'll land on a page containing more release notes. Scroll down to the bottom of the page and you'll see an icon with "download next to it. Click the icon. At this point your browser should ask you to save the file.

Installing Steam and Skyrim in D:\Program Files (x86) should be fine provided you created the folder yourself. I've done pretty much the same thing on my system except I named it D:\Program Files. To be honest, I'm not see anything here that stands out as a possible issue other then the nagging Windows 10 update. I do remember some of the folks here ran into issues with Wrye Bash that required forcing an update to Windows 10 build 1809 or later, but I think this is an issue with Wrye Bash that's most likely unrelated to Creation Kit. (see https://forum.step-project.com/topic/14158-cant-use-wrye-bash-from-mo2/?hl=force+update&do=findComment&comment=236549) The only thing I can think of is to enable debug logging and to go through the log file to see if anything there stands out. To do this, delete everything in the Mod Organizer\Logs folder to start clean. Run Mod Organizer. Click Configure Settings and Workaround (the screwdriver/wrench icon a the top left), go into the Diagnostics tab and change Log Level to Debug. Click OK to close the dialog. Now run Creation Kit and wait for it to exit. Close Mod Organizer and upload mo_interface.log and usvfs-*.log to somewhere like PasteBin or a cloud drive and include a link to it here.

I don't know which game you are trying to play or which voices are in German, so here's some generic information for Skyrim. The language of the main game is controlled by the sLanguage setting in the General section of Skyrim.ini: [General] sLanguage=ENGLISH The voice files are specified in the Skyrim - Voices.bsa and Skyrim - VoicesExtra.bsa files in the Archive section of Skyrim.ini. [Archive] sResourceArchiveList2=Skyrim - Voices.bsa, Skyrim - VoicesExtra.bsa For Skyrim Special Edition, the voices are in Skyrim - Voices_en0.bsa and are loaded via the same setting shown above. If these voices are coming from a mod, you need to ensure you downloaded the English version of the mod.

This message in the Mod Organizer log is completely normal so you can ignore it. I know you say you've used LOOT to sort the load order, but have you used xEdit to resolve any conflicts in the plugins? Unfortunately, there are about 10,000 different reasons Bethesda games magically crash to desktop that range from out of memory, out of GPU memory, missing meshes, possibly corrupt mesh or texture files, certain conflicts in plugins, and the list goes on.

Have you tried running SKSE from a pure vanilla profile without any other mods activated? You can do this fairly easily by creating a new empty profile and running skse_loader.exe from this new profile. Assuming this works fine, you may either slowly rebuild the profile you want to use or deactivate the mods in your existing profile in chunks (say 5 or 10 at a time) to narrow down which mod(s) are causing the issue.

This is how I do it... * Download SKSE and ensure SKSE is compatible with the version of Skyrim Special Edition you currently have installed. * Right click on the SKSE file you download, click Properties, click Unblock, and click OK. * Extract skse*.dll, skse64_loader.exe, and skse64_steam_loader.dll to the Skyrim Special Edition folder. * In Mod Organizer, install mod, select the SKSE file you downloaded, and install it as a mod. This installs the Scripts folder in Mod Organizer. * In Mod Organizer, add a new executable for skse64_loader.exe and name it something like SKSE. You might also verify that ModOrganizer.exe isn't blocked if you are on Windows 10 because Windows 10 and antivirus software may block the virtual file system. Also verify all installed plugins that require SKSE are compatible with the version of SKSE you have installed.

https://forum.step-project.com/topic/14182-skse-for-sse-will-not-launch-through-mo2/?p=236772

Generally you want to manually order the mesh and texture mods in the left pane in the order you want to win the conflict and let LOOT sort the plugins in the right pane. If you need to keep plugins in the right pane in a specific order, you can use LOOT rules to do this.

I'm not aware of any easy way to keep the mod order synchronized between multiple profiles other than to select each profile and reorganize the mods by hand. I imagine such a feature was discounted as a bad idea because there may be legitimate reasons to have some mods in a different order. I typically do this when comparing mesh and texture mods to determine which I want to eventually use in the game.

This is the first time I've heard about anything remotely like this happening, so I have no idea what might cause it. Just to be clear, you are referring to profiles listed when you click the Configure Profiles button at the top and not the mods listed in the left pane?

You have a couple of obvious issues here. The first one is that you shouldn't install Skyrim in the C:\Program Files or C:\Program Files (x86) folder because Windows restricts access to these folders. It's rather unfortunate that Steam defaults to installing games here, but you can use Steam to move Skyrim pretty much anywhere you want (say something like C:\Games). The second issue is that a lot of older guides and tutorials recommend installing utilities directly into the Skyrim folder but these are incorrect. You should install mod managers, DynDOLOD, and other tools in their folder in something like a C:\Tools folder. You should run Skyrim Launcher at least one (from Windows or a command prompt) so it creates the initial INI files and creates the registry entries so DynDOLOD and other tools can determine where Skyrim is installed.

There are a number of pitfalls that can prevent SKSE and the game from working correctly so I suggest using a vanilla profile with no mods installed to work through these: Do not install Skyrim or Mod Organizer into C:\Program Files, C:\Program Files (x86) or any other UAC protected folder. Note that Windows 10 adds extra layers of protection on these folders that may prevent Mod Organizer's virtual file system from working. Do not install Mod Organizer into the Steam or Skyrim folder because the virtual file system will not work correctly. Using File Explorer, right click on ModOrganizer.exe and click Properties. If you see an Unblock button or checkbox, you need to click Unblock and click OK. If you are on Windows 10, you may need to repeat this for every DLL in the Mod Organizer folder and its subfolders. The recommended solution is to download Mod Organizer from Nexus, immediately unblock the file you downloaded, and then install or extract the files to the appropriate folder. Run SkyrimSE.exe from Mod Organizer to verify you can run the base game without any issues. Ensure you are using SKSE 2.0.16 and Skyrim SE 1.5.80. You can find the version number by right clicking SkyrimSE.exe, go to the details tab, and look at Product Version. If this is not 1.5.80, you'll need to run Steam and let it update Skyrim SE to the latest version. In your vanilla profile (without any other mods installed and with a clean Data folder), install the SKSE scripts and try to run skse_loader.exe from Mod Organizer. You can do this my clicking install mod and select SKSE in the folder you downloaded it to. If you see a red "No game data", right click on the Data folder and click Set data folder. When you install SKSE, you should copy only skse64_1_5_80.dll, skse64_loader.exe and skse64_steam_loader.dll to the Skyrim Special Edition folder (the folder containing SkyrimSE.exe). All of the scripts should be installed as a mod in Mod Organizer using the steps above.

That only ones I can think of off the top of my head that really matter are the smashed/bashed patch, FNIS output, Dual Sheath Redux patch, TextGen and DynDoLOD. These should all go towards the bottom in the order generated. The files created by SKSE are basically log files so I usually just move these into the SKSE mod since order doesn't matter.

Generally you want to move files out of Overwrite into either the mod that generated the files or into a new mod immediately after the files are created. When you create the bashed bash, the files in Overwrite should go into a Bashed Patch mod. When you run GenerateFNISForUsers, the files should go into a mod named something like FNIS Output. When you run the game the first time, you may find some files in Overwrite created by SKSE and these can be moved into the SKSE mod or into a new mod of your choice. Whichever option you chose isn't that important and I seem to recall that some files from SKSE continue going into Overwrite each time you run the game so I wouldn't worry too much about cleaning these out after every playthrough. It's really more important to ensure Overwrite is clean before generating files that should be moved into a mod (like Bashed Patch, FNIS, etc.) so you don't end up with a mixture of files in Overwrite that's difficult to manage. It's been a while since I've generated the FNIS animations, but I think you're doing it right. I remember the last time I installed FNIS, I ran into similar issues and finally set the option to create files in mod instead of Overwrite.

Which saves the game sees depends on how your profile is configured. If you have "Use profile-specific Save Game" checked for this profile, the game sees only the saves stored in your profile. This is my preferred choice because it prevents me from accidentally loading a save for another profile. If you do not have "Use profile-specific Save Game" checked for this profile, the game sees only the saves stored in the global location (C:\Users\[username]\Documents\My Games\Skyrim Special Edition). You can use this if you want, but you''ll see saves for all profiles and it can be difficult to manage if you use multiple profiles. Go to Profiles, select the profile you want to use, ensure "Use profile-specific Save Games" is checked and click Transfer Saves. The characters and saves in the left box (under Global Characters) are the saves in C:\Users\[username]\Documents\My Games\Skyrim Special Editiion The characters and saves in the right box (under Character for profile Default) are the saves stored in selected profile Select the character that is used in this profile in the left box and click Copy to copy the saves (or Move to move the saves) for this character to the right box. This moves all of the saves for this character into your selected profile. If you run the game now, you should see only the saves for this one character. Note that if you uncheck "Use profile-specific Save Games" for this profile, Mod Organizer asks if you want to delete the saves stored in the profile so don't uncheck this and select yes to delete or your saves may be permanently deleted.

You could copy all the saves in "C:\Users\[username]\Documents\My Games\Skyrim Special Edition" to a safe location first, then run Mod Organizer and copy the appropriate saves into your profile. Although this should be a relatively safe thing to do, you have the backup copies as extra insurance just in case.

Run Mod Organizer, click the Profiles button. Select each of the profiles and verify Local Saves is checked for all three profiles. It can be a bit confusing because it looks as if Local Saves applies to all profiles, but it really applies only to the selected profile.

I think the first clue here is that you have Skyrim Special Edition installed in C:\Program Files (x86) so you're likely running into UAC and permissions issues. You can use Steam to move the Skyrim SE to another folder (like C:\Games) that is not protected by the operating system. I can't tell where Mod Organizer is installed in that snippet, but ensure Mod Organizer is not installed in the Steam or Skyrim SE folder because the virtual file system will not work correctly. You can install Mod Organizer pretty much anywhere you want (say C:\Games or C:\Tools) provided it is outside any UAC controlled folder (like C:\Program Files and C:\Program Files (x86) and outside the Steam and game folders. Finally, when you download Mod Organizer you should unblock the file you downloaded (File Explorer, right click the zip or exe file you file downloaded, Properties, click Unblick, click OK). if you don't do this, Windows 10 may block the virtual file system and make it look as if Mod Organizer isn't working correctly. Also note that some overly aggressive antivirus software may also block Mod Organizer's virtual file system so you might consider adding the Mod Organizer folder to the exceptions list.