GrantSP

I don't know what further to advise you, if you are following the instructions to the letter then it should be working for you. As for Windows 10. I have no issues. My laptop is an updated OS, from Windows 7 but my new desktop is a brand new Windows 10 install and both of them run all the games and tools I have installed flawlessly.

Well when you posted the FNIS output in a spoiler tag labelled "NMM" what was I expected to believe? Still, even if you don't "use" NMM it may be possible that its use has left some leftover files in the Data folder and this is conflicting with MO. I'm still perplexed by the numerous reports of FNIS being difficult to install and run with MO. Have you followed the instructions I posted in the first post of this topic? Finally, if all you are doing is wanting to mod Skyrim for gaming use there really is no need to keep NMM installed and used for "testing". I can assure you the problems in doing so outweigh the perceived benefits.

Purely coincidentally @Sacremas PMd me on my Nexus account today on another matter and I happened to mention you to him, so he will be expecting someone shortly to ask him something. I'm assuming you had to make an account on LL to download those files so doing a forum search for his name will get you in contact with him.

I'll state straight away that my skill level with the CK is 0, zero, nada, nil. Having said that I think I have a firm enough grasp on the workings of this issue to say that ICAO does exactly what it is intended to do and does so rather well. I might actually say it is an inspired piece of work. From what I can see the "issue" with the average modder trying to make a compatibility patch for this mod comes from the fact that you can't just load up xEdit and look for conflicting records since the real art to this mod comes from the navmesh placement. Since this means examining every single mod against ICAO I reckon a lot of modders just see too much work and look for an easier fix. Sadly it comes down to the fact that the only real success comes from hard work and until all the "so called incompatible" mods are checked against this, there will always be concerns and questioning. On a purely technical basis this mod should be considered a 'must have' mod as it addresses a very real problem: pure AI implementation. As far as STEP is concerned I hope we can continue to showcase these great mods and offer as much support for it as possible.

Is there any specific reason for the move? Issues with posting them or such like? It would be good to have everything here in STEP without the need to view anything in another window/browser tab.

Just ask him for assistance in setting the correct order for your mods. He's also very good with FNIS so any issues you may have in the future with these mods he might be able to help.

modlist.txt.2016_01_02_15_42_25 is not the same thing as ModOrganizer_16_01_05_22_42.log! What you have provided is the modlist from your profile, which is what I also wanted to see, but what I asked about is the full log generated by MO which is in the same place as the last log you posted. Now, straight away I can see that you aren't using MO correctly. You have a number of mods installed into the Data folder and not via MO. *Unmanaged: dd - realistic ragdoll force - realistic *Unmanaged: improved container names *Unmanaged: More Hair Colors (ANGRYZES IS ORIGINAL OWNER!)--- *Unmanaged: PS_StandingStones *Unmanaged: sksetester *Unmanaged: unreadbooksglowThese will cause issues with unresolved conflicts. Assuming the order presented is actually what MO is working with then no doubt you will have issues with FNIS and any mods that need it to work. It should be loaded high in the order before any mod that needs it, including those mods you have from LoversLab. I have next to no experience with those mods but the little I did have wasn't easy, so I'm probably not going to be of any help with those. The FNIS log shows many mods are not being read by FNIS with "file not found" messages all through it. You will need to move the necessary mods around so FNIS will see them correctly. There is a user on the LL forum by the name of "Sacremas" I suggest you search him out and ask for his assistance in this matter. He and I corresponded on this matter a while back and knows more about LL mods than I do.

Welcome to STEP @refmon Assuming you still have a working MO installation, including all the mods and downloads from before, it's just a matter of running MO with a profile you previously created that includes the installed mods and run FNV from MO. Since MO can, and should be, installed outside of the game installation folders. This means removing/repairing your game will have no impact on the mods you have installed

No sorry, no idea. You may be able to get a better idea of any errors if you ask this in the General section.

The modlist is in a folder under another folder called "profiles" in the MO installation. In your case it is called "solo game". Were there no other logs in the folder where you found this log? Anything called something like: ModOrganizer_16_01_05_22_42.log? At this stage I haven't seen any diagnostic material about what is/isn't happening with FNIS. Can you post a screen shot of the FNIS screen showing the error message, or after you run FNIS can you post this file: D:\steam&maybe other game stuff\steamapps\common\Skyrim\Mod Organizer\overwrite\tools\GenerateFNIS_for_Users\temporary_logs\GenerateFNIS_LogFile.txt

@Tomack13 You should be able to run multiple copies of MO on the same game and have no issues with any of them interfering with the others. Since MO uses a method of "Mod isolation" when managing mods, what you do in one install can not have any impact on the other. The only time there might be an issue is when a mod/tool is installed/executed in the actual game folder structure, outside of MO. Regarding your question about why the list of mods in the left-hand pane doesn't match with the modlist, it is because that list shows only the plugins, ESM or ESP files, and the left-hand pane is showing the mods you have installed, some of which may have no plugins at all, ie. texture replacements etc.

Welcome to STEP @patchling From I can see in you post the problem may be exacerbated by the fact you are running both MO & NMM. MO must be installed with a clean Skyrim folder, that means no mods are allowed to installed outside of the MO VFS. The files managed by NMM may be interfering with the load order being set with MO and thus messing up the running of FNIS. You will need to completely remove all the NMM installed mods, and NMM itself, and then use only MO to manage your game.

They are not papyrus logs, as these are saved in an entirely different location. At first reading I will also say they aren't any other logs generated by some mods. Those are usually found in the Skyrim folder but will have a *.log extension. Do you have Windows set to show the file extensions? You should, it makes things a lot easier to diagnose. The fact you mention a fresh install of Skyrim and yet they keep appearing worries me. I would do a thorough check of your system for both viruses and malware, just to be sure!

You've changed the sorting method to "Categories" by choosing that option with the middle/bottom button of the left-hand pane. Notice the diagrams in the MO wiki showing the difference between the sorting.

The recommended method of handling this issue, ie. cleaning the ESMs and not having Steam remove them, is to make a mod from the cleaned ESMs and have MO load them after the "unmanaged" ones. See the STEP guide on how to do so.

It might actually be helpful if you post your "modlist.txt" from MO's current profile folder. Both the mods you mentioned as being active shouldn't leave any files in the Overwrite folder and that text file is most often associated with FNIS, as @Greg pointed out.

I was a bit harsh in my comment wasn't I? My apologies for that and thank you for your clarification on your point of view on the topic, I guess there are different ways to come at an answer.

Perhaps you could add a large banner heading to the old one directing users to the new one?

If you can post your MO logs please so we can examine them. Also your modlist.txt will help determine which mods might be misplaced.

Really!? You spent days searching and haven't found the answer despite posting in a topic that answers the question! It is quite simple, ALL mods must be managed by MO to avoid the "unmanaged" indicator appearing next to them. You must remove them all, whether installed via Steam, NMM or manually and re-install them with MO. Until you restore your game folder to a clean "vanilla" state you face the problem of conflict and possible CTDs.

Your logs will be helpful before you do anything drastic.

If you run MO as a regular user, as you should, and it is telling you it can't find certain files or executables that's because they are restricted by Admin privileges. As soon as you run MO with Admin privileges it will fix those issues but then impose other errors on your setup, possibly the one you have now. So firstly you can safely disregard the Python error messages. MO only uses Python for a few small plugins in its tools and it also comes with a bundles subset of Python when you install it. Easiest thing to do if those messages annoy you is to disable the Python Proxy in the settings: Settings -- Plugins -- Python Proxy / enabled == false. Now, as to the "Creature Pack" error. When you installed this mod did you ensure it was installed into a mod all its own and not merged into the FNIS main mod? If it is a separate mod ensure it is both below the FNIS main mod and checked in the left pane.

The joke part of @GSDFan's comment here is the wording, suppository instead of repository. Google the definitions and you will see why having a suppository isn't always a pleasant thing.

All done.

Your MO logs will be helpful in this matter but "off the top of my head" I'd say you may have changed to a profile that perhaps has read-only settings on the files, but that's just guessing.