xxx696 Posted July 29, 2016 Posted July 29, 2016 Hello Guys, I've already made a couple of new threads here and each time I do I get some wonderful help from the community which then finds a new root cause for the problems I'm having with modding Skyrim. My latest problem is FNIS. First time I installed it via MO it seemed to work fine, but I had problems elsewhere. I then went to NMM and that was even worse, so I went back to a fresh install of MO. Now, when I try to add FNIS for Users as an execuable file, every time I hit the 'Add' button it simply does nothing. I'm on Windows 10 if that makes it worse. Has anybody got any ideas for a fix?
srayesmanll Posted July 29, 2016 Posted July 29, 2016 While the video guides are helpful, I found the STEP guide (link in my sig) most useful (it's the official documentation for ModOrganizer). Go to the FNIS section and make sure you've done the steps EXACTLY there. If I remember correctly, if FNIS is installed (AND ACTIVATED - you do have FNIS checked on in the left pane, correct?) then the screen where you add executable files like FNIS Generator (and LOOT, WryeBash, tes5Edit, etc) already had FNIS listed. But again, double-check the steps in the STEP guide.
xxx696 Posted July 29, 2016 Author Posted July 29, 2016 Thanks for the link, srayesmanll. I'm afraid it only told me to do what I've already been trying. FNIS is definately active in the left hand window. Is this an MO settings problem? When I open the 'Modify Executables' tab there are only three already listed - SKSE, Skyrim and Skyrim Launcher. All are listed in faded text and cannot be modified. Got it - I was one update behind on MO. I updated the version and now it works. I feel very stupid and I'm sorry for wasting people's time, but I figured that I won't be the only person to ever do this so best to post here and try to help out somebody else who looks for answers to the same problem.
majorfreak Posted July 30, 2016 Posted July 30, 2016 i wonder why you needed an update for MO to make the executable work for...nvm, i remember that error well. the binary was inputting "/" automatically when it should have been a "\" (or visa versa; i forget)
Recommended Posts
Archived
This topic is now archived and is closed to further replies.