GrantSP

Perhaps this is down to LOOT providing different, yet working, plugin orders that when run through the script provide different results. I too had different initial results to SRB.

Purple textures mean whichever mod that is supposed to be supplying that texture... isn't. You can bring up the console and click on the item to see which plugin should be providing it and then examine your load order to see where you messed up. Steam verification ALWAYS says that, it's a file used to see which files are missing and if anything needs to be re-acquired it will do so immediately. You'll see a download happening in your Steam UI.

Welcome to STEP @DassiD, and you come bearing gifts! Nice work. I love Morrowind but as you say it is showing it's age. Perhaps add a section in the beginning describing the system requirements needed for this modded setup, not strictly necessary considering most modern systems will run a game that old, but a nice touch nonetheless.

So... do you really need the HDT Physics Extension mod installed? I note that that mod also has a version of Sheson's memory patch included, or at least some code that purports to do the same thing. If you are getting fatal exception crashes from that DLL why not remove it? I'm not even sure if you have the Memory Blocks Log installed, so if you haven't please do so and edit the INI according to the guidelines in this thread.

I'm fine with removing it.

If no-one's missing it that's a fairly good indicator to drop it, isn't it?

The instruction to make copies of the DLC and move them back into the Data folder is solely for those plugins. That way Steam will not complain about missing files and the cleaned DLC, that are now in mods of their own, will be used by the game and will not be replaced if you do a 'Verify game cache' in Steam. None of that is applicable to any mod that you clean and xEdit will simply create a backup copy in the mod's folder.

Saying his mod is only supported for 1.2.9 of Arthmoor's mod does not say it won't work for any future versions. If this does the job that it says it does and we all like it, I say keep testing, and if it can be included then do so. Any future issues with mismatched mods can be addressed in the future.

Your screenshot may actually be showing the reason: Comodo AV package. As noted in this topic, most AV packages do not like the MO 'hooking' mechanism and sometimes mess up badly with their "safety". Try placing MO in its exclusions list or whatever Comodo's version of that is called.

True, but I actually think the inclusion of BASH as a native commandline will be a great boon. This means installs can be automated with advanced file/folder manipulation by simply using Windows own tools with no 3rd party software needed. For those that package tools or mods that need to do verification of existing software this may mean an easy way for new users to get all the requirements checked BEFORE they stuff up their games.

The file "cef_extensions.pak" is part of the Steam installation. Have you run the game at least once outside of MO so that the correct registry settings are established?

No. Just to be sure check that ALL BSAs are enabled in the 'Archives' tab.

That's good, Windows errors are hard to track, Super-mutants are easy!

Have you doctored the screenshot at all to remove details about the calling programme, or is this just another example of how "helpful" Windows error messages are? Without knowing what programme is making that error message it is going to be very hard to determine how to fix it. I'm assuming FO3 is fine as it would most likey crash if it suffered a C++ error. Are you running an ENB and is that still active after the message? Any tools on your system running in the background? GPU enhancers or overlays, game boosters, messaging apps or anything really, probably those apps that may need to make refresh calls to the screen, since you mention a transition from inside to outside happened. (That may be just coincidental though.)

Is your game in English? As @Greg noted if your game is not in English or you have a mod that has text in another language and it hasn't supplied those strings, you will see that error. Verify your game with Steam.

I'm saying that in my system there are *.DLSTRINGS & *.ILSTRINGS for each ESM that is loaded: Skyrim, Update and each DLC. Which is a vanilla install only months old.

You should also have those for the DLC: Dawnguard, Dragonborn and Hearthfire

Did you have a Steam update at any time inbetween this? That may cause problems if the game is not started at least once outside of MO before using it, something to do with the registry entries.

Haven't you merged that along with all the other Yuki mods?

So, if it isn't a lighting issue the effect can be seen in other locations? Since you mention the use of other magic mods the issue may be the result of the spell's effect interacting badly with the ENB you use or with another of those mods. Are you able to pull up the console and examine the effect? What texture it is using etc.

Yes it does, as part of the Creation Kit install, which means they are used for mod creation. Why it is included as part of the general guide I'm not sure, I know of no process including those using patchers or xEdit scripts where this is needed. Perhaps @Neovalen can add some inforamtion as to why that step is necessary. As an aside, the guide is very clear, in my view as to where and how to extract this archive. If that is not clear for you perhaps you can highlight the ambiguous part and that can be modified.

If you just extract the entire file, then yes, both folders. Are you intending to do some scripts modding, because if your are not you are better to just leave it alone?

Yes, but only if you intend on doing modding that use scripts. For general mod use there is no use for them. These aren't the compiled scripts that are referenced by mods, they are the source files of those scripts.

If you're not too attached to your current game and are really looking for a stable and enjoyable game, it is always easier to work from a known stable base and add mods than to go the other way, removing mods from a broken game looking for stability. You may want to try STEP or one of its derivatives to get your game to an acceptable position and then add specific mods that you want.

It would be preferable to have the first instance in any guide where xEdit is mentioned to describe this and then ALL further instances of its use to be xEdit. STEP is trying to gwet users to understand this concept that the executables are interchangeable, and hence most of the documentation on the web can be applied to any version. I've been going through a lot of guides over the months and making this change, possibly it gets changed back for this reason.