GrantSP

It can safely be changed/removed or ignored, it only points to the old installation file.

The only purpose of FNIS Spells is to showcase what can be done with FNIS animations. It serves no purpose in the game aside from making certain annoying NPCS moonwalk or do other outrageous dance moves.

That's correct. Do exactly as you have described.

Also make sure that the BSA that, ordinarily is loaded by that plugin, is in fact checked and loading. This is in the "Archives" tab.

I'm going to sound heretical here, but I don't think that makes as much an issue as we are led to believe. Having all the cleaned ESMs in one mod still means they are listed separately in the plugin list so that each is passing on edits to records correctly.

I have a question about one of the stated goals: Work on Legendary intially and then split it up to it's individual DLC's and main part(Skyrim.esm, Update.esm).Why? Now that every man and his dog has all the DLC and even the glacially slow USKP team are combining all the work into just one.

Success!!

MO pulls the version number from the Nexus page, not from each download which is why each optional file shows as "out of date". Now I've just set my MO profile to match yours exactly and the FNIS Spells work as expected for me so the next questions might seem obvious. Have you selected a spell with the FNIS Spell Selection spell first? I went through all of them and they are all working for me.Are you sure you have actually targeted the NPC correctly? They must be bathed in a bluish cloud and there is an audible hit noise to show they are hit.

Welcome to STEP @SirTwist MO2 is in an early alpha development stage and as such it shouldn't be used as your general game manager. If you wish to assist with the development then please do so, keeping in mind that it only handles 64bit applications at this stage.

I just assumed they were as I have never yet installed STEP as a complete guide. Well if that's the case that pretty much kiboshed that idea. Oh well, not to worry. It was just because there have been a few very new users lately having trouble with either DDSOpt or the guides in general.

It sounds like you have fallen into the trap that @Greg was highlighting to you. Let's say you have two profiles: Profile1 & Profile2. You organise the first profile and run the various patchers and the results from these are found in the 'Overwrite' folder. Most likely you have FNIS output and you should create a mod from the folder and name it FNIS--Output--Profile1"". Then you might run a 'proccer' patcher and likewise the resultant files that are in 'Overwrite' should be created into a mod named according to that profile. Repeat for all the patches you make. Now with Profile2 you add in the extra mods and order them correctly and again run all the needed tools to patch this set of mods. Each time naming the created mod from 'Overwrite' specifically to match the profile name. The thing to remember with MO is this: any file that DID NOT EXIST when any of the tools were run, is saved into the 'Overwrite' folder. This is because MO's VFS only works for file that exist at runtime, any new ones it doesn't know where to place them, hence ALL new files are dumped into this 'Overwrite' folder. What this means is, if you have already ran a patcher and it is still active in the left-hand pane, those files now DO EXIST in the VFS and the tools will see them and assume they need updating, which they happily do. Remember none of these tools were made with the knowledge that at some point another tool, MO, will trick the file-system into thinking there is more than one set files in the Data directory. So to avoid this you must always uncheck all mods that contain patched files in any new profile you are working with. It sounds confusing but makes perfect sense when you stop and think about what MO is doing. Profiles are a collection of files with the same names and structures that are switched around by MO so our games see them. The files they contain are exactly the same when they are from a mod downloaded from Nexus. SkyUI contains an ESM and a BSA and in every profile you have the EXACT same files are used. However when YOU patch a game with FNIS or RSPatch or whatever, the files created are not the same in each profile, they are dependent on the mods YOU HAVE ACTIVE. That's what these patchers are designed for, custom sets of mods active together. As soon as you switch profiles, that set of mods is completely different, the patches you just made are for another set. Imagine you and your friend have differing tastes in mods and he patches his game and then says: "Hey do want my patches, I just made them?" Basically the same thing happens when you switch profiles, they won't work.

Not sure what you mean by Your screenshot shows it is still in the Data folder and, from the message from LOOT, you probably missed that one during your cleaning stage. It is still in the Data folder and it is still dirty therefore it wasn't cleaned. At this point you should have three cleaned DLC plugins, each in their own mod active in the left-hand pane of MO and they will show in the right-hand pane with the name of the mod (this is just the name of the folder that contains it) in the column to the right.

Excellent choice for SSDs. Highly recommended.

Because it is such an odd occurrence, I've added it as a question to the FAQ in the wiki. Couldn't have done that without your input so thank you.

That is very interesting to know, thank you. As I have never used that setting (any reason why your syatem needs to have it, or why you had it checked) , I have never seen this behaviour.

Shouldn't make too much difference with the MO program installed on the SSD, as once it starts it releases the code to the game engine and no further disk activity from MO takes place. However you can place the "mods" folder, which holds all the files used by the game on a SSD and that might help... a little. TBH though, I don't reckon it will be that much.

STEP guide has them listed here. There are the "Unofficial High Resolution Patch" and the "STEP Optimized Vanilla Textures"

@Neo what do you think of providing a link in your guide to the pre-rolled optimized textures STEP is hosting in addition to the steps to DDSOpt your own?

Just to be clear on this matter. The TinyUrl link in the first post is not the same as the one just posted. https://tinyurl.com/z56a2ee takes me to the Bethesda Hi-Res DLC Optimized page. https://tinyurl.com/z4b84yn takes me to the Optimized Vanilla Textures. As for the VB script, well now that's a different matter altogether, that's specifically for NMM users and since you are using MO, you don't need it.

Hmm... maybe @Neovalen can provide a link to the STEP pre-rolled versions of the optimized textures for users that don't want to/or can't use DDSOpt? I didn't even realise he didn't, since it should be based on the initial STEP install.

Nope.

Those are not part of the STEP install. You also didn't answer my question about the "Hotfix". Any download that says you need to run a VB script to make textures work on games installed on the D: drive, is just ridiculous and I advise you to NOT RUN those VB scripts. Are you following the STEP guide as the title of your topic seems to indicate?

Welcome to STEP @amourfou A very odd situation you have. Could you open the MO.ini in a text editor such as Notepad and find a line that looks like this: window_geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x2\0\0\0\0\0R\0\0\0~\0\0\x6\x8c\0\0\x3j\0\0\0Z\0\0\0\x9d\0\0\x6\x84\0\0\x3\x62\0\0\0\0\0\0\0\0\a\x80)Copy that line and paste it into a new text file called anything you like and save it. Now open MO and resize it to something you want and then close it. Reopen the MO.ini and copy that same line into the text file you made and compare the two. If they are different then MO is saving the needed window geometry correctly and all is fine on MO's side. If they are the same then there is a problem we need to solve. Either your INI's are read-only, not likely as you can save the executables you set. Or something is making changes to your MO window in the background. If you have any anti-virus software make sure to set an exemption for MO in the settings. Likewise for firewalls or similar. On start up there is a brief check made by MO for an active network connection so that the status of your Nexus account can be made. If there is any issue with that connection there might (very slender) be a chance this is related, and that "Activating Network Proxy" message might be significant. At any rate your INI and the logs from the logs folder will assist us.

Ok so looking at the 2nd scenario, if you examine the Update.esm in the Data folder and it is smaller, this is the one you need to keep. Now at this point you have also run ahead a little and we need to do a bit of house cleaning to get things in the same shape as the STEP guide. After EACH cleaning step you needed to create a mod from the contents of the 'Overwrite' folder so that they can be enabled, each in its turn, after the "Unmanaged" versions. So, in an Explorer Window navigate to the MO 'Mods' folder and create folders named after each of the cleaned ESMs. Cleaned Update ESM, Cleaned Dawnguard ESM, etc. Move each of the cleaned ESMs into the folder of the same name being careful to also move the Update.esm from the Data folder. Next you can either move all the backup copies of these folders back into the Data folder and remove the "backup" extension or just use the Steam app to verify your cache to restore the original files to their correct place. If you had read the next paragraph in the STEP guide all you would have needed to do was right-click on 'Overwrite' after each clean and "Create mod..." and you'd be set. Repeating after each clean. Nevermind, the same result is had.

What is this? Where did you see it? As for the Optimized Texture Packs, either/or not both.