Andy14

Removing the mod causing this will be difficult, as there are multiple mods involved. However, here's a quick note about the script errors. Often, IDs can be found in the log, for example, the ID of a quest that a specific script can't locate. The IDs in Bethesda games always follow this format: The first two digits represent the position in the load order, and the last six digits are the sequential ID in the ESP/ESM/ESL. The IDs are displayed in hexadecimal. Therefore, you need to convert the first two digits from hexadecimal to decimal – this can be done with a Windows calculator. Simply switch the calculator to programmer mode, select HEX, enter the two values, and then switch to decimal. You can then search for the mod in the plugins.txt file. Or, even easier, use Loot to find the mod, as Loot displays the load order (left window) directly in hexadecimal. Once you have identified the mod, go to the corresponding mod page and read everything carefully, including all dependencies and posts.

I looked at the Papyrus.0.log file. None of the problems I identified are related to Dyndolod.

Omg. Quick feedback on Papyrus.log You have 35 invalid calls, apparently due to missing script files. You have 38 direct warnings indicating that scripts are definitely missing. You have numerous indications of missing ESP and even the wrong Skyrim version. Start at the top of the log with research and a correct installation. My advice: 1 - Do not install or uninstall mods in an existing save. If absolutely necessary, clean the save afterward with Fallrim. 2 - Do not install mods without carefully reading the description. This also applies to "required" mods. 3 - Check the load order with Loot. Loot will also show errors if master files are missing, etc. 4. - Run FNIS and read the warnings.

That's utter nonsense.

This isn't a texture problem, it's a mesh problem. It's clearly visible that the shapes on the left and right are different.

Make sure that not only the shape fits, but also that the bone weights and morphs are transferred.

Yes, try to fix the errors anyway. Most of them aren't from ZAZ/ZAP or Estrus, but rather "Cannot open store for class dfm_..." I have no idea what dfm stands for.

Far more important than the warnings are the errors caused by missing scripts (Connot open store... etc). Loot only checks mod dependencies at the Master->ESP level. No internal check is performed at the script level. Therefore, my advice is to try to find out which mods are trying to call these scripts and can't find them. I'm not familiar with many of these mods, so you'll need to thoroughly read all the mod descriptions to find out which software dependencies are listed. This also applies to these additional mods—they may have further dependencies as well. Once the scripts are in place, not only will the errors disappear, but many of the warnings will also disappear.

What does the Papyrus.log say? Especially after you entered "ski_configmanagerinstance 1" in the console. That command should cause MCN to reload all mods.

Did you have your load order checked with Loot?

To display windowed programs in full screen, I use the program linked below. I use it for The Sims 3 because otherwise, with my AMD graphics card, the full screen is far too dark and overly saturated. But I'm sure there's another way to solve this problem. I hope Steam/Skyrim isn't installed in C:/Program Files. Link

The script should generally work if you include a gender query.

Let Loot sort your mods. Loot also checks if all required mods (i.e., prerequisites for mods) are met. https://loot.github.io/

For the old DirectX Version (Skyrim LE) is GIMP fine.

GIMP is not suitable for BC7 compression of FO4 textures. However, you don't need Photoshop for this; PaintDotNet can handle the DDS files in the current DirectX version of FO4. The textures can be found in the 9 Texture BA2 archives, not in Materials.