Charlie86

Since I have that ugly purple on my screen right now, too - did you ever manage to fix it? EDIT: I don't know what to say. MO 1.3.8 totally fails to install this (version 2.7.1 - the only one Nexus) correctly for me, tried another time to no avail. It does not install the fullsize meshes, and does not install any textures at all with the FOMod version. Here's what I did to fix it: I opened the mod 4x (four times, really) in manual mode. First, I chose "05 Fullsize" as data directory, and on the next runs "06 Fullsize DG", "07 Fullsize DB" and "08 Fullsize Textures" respectively and merged those. Now I think it looks the way it should :)

It is interesting that you asked that. I am using SFO 2.3 + 2.3b Update, while the guide explicitly states to use the 1.87. Neither of the two included ESPs seems to require cleaning any more - both have no removed identical to master records, and both have no references. It'd be curious to know why 1.87 is recommended over 2.3, but sadly the whys are not mentioned in STEP ;) In 1.87 the main ESP (Skyrim Flora Overhaul.esp) has one entry that is deleted, while there are non such in SFO - Dragonborn.esp. EDIT: I suppose it's about the tree changes in in V2 - note the version selection guide on the mod's page.

Well, I am on Win 7 - and TES5Edit manages to overwrite the original file despite being run from MO. My suspicion is that MO might catch the creation of the new file, but misses the later action when TES5Edit moves the newly created file in place of the old. Maybe this behavior is new in TES5Edit 3.1.1, and earlier versions directly create the file in place?

Since I posted the same thing yesterday in the bug reports: the update.esm in your skyrim folder should now be smaller than the one you backed up. Do the following: 1. Go to your MO mods folder (you find the location in MO's Settings -> Common -> Mod Directory, loose translation from the autoenabled translation in my version) 2. Create a new directory, e.g. "STEP Cleaned Update" 3. Move the smaller update.esm from your Skyrim\Data directory into the new directory 4. Move your backed up file into your Skyrim\Data directory 5. Restart Mod Organizer You will now have the new mod listed, just as if you had created it according to the current docs. Hope it helps!

In step 2.c (update.esm cleaning) I did not get the new update.esm in my Overwrites "mod" (Mod Organizer 1.3.8). Instead I found that the update.esm in my Skyrim folders was smaller than the backuped one (despite having the same timestamp as before), and Mod Organizer only had the TES5Edit (TES5Edit 3.1.1) backup folders. I had to manually create a mod and move the update.esm there to achieve the same as the guide described. Is this something I did wrong, or did mod organizer detect TES5Edit's actions (delete old file, create new file, move new file in place of old file) wrong?