search

Nexus-Mods / Nexus-Mod-Manager

GNU General Public License v2.0
991 stars 165 forks source link

NMM 0.80.14 Will not install FNIS files to SkyrimLE #1156

Open Weatherbee9 opened 3 years ago

Weatherbee9 commented 3 years ago

Tried to install "FNIS Behavior 7_6" and "Creature Pack 7.6" to SkyrimLE on 6/09/2021 and 6/10/2021 using NMM 0.80.14 . None of the txt or script files were installed. Had to install the mods manually. Had the same problem with "AddItemMenuLE320_SKSE173". Also, NMM did not install any files to SKSE. Only the "esp" files were installed.

Re-installed NMM and tried to add FNIS mod to a new install of Skyrim and had the same problem. None of the script or txt files were transferred to any Skyrim Folder.

Any help would be greatly appreciated. I do not like to use MO2 or Vortex. Have been using mostly NMM since 2012 and would like to continue using it.

DuskDweller commented 3 years ago

It looks like you made some manual edits to your NMM or game install, and NMM is unable to install files that are not .esps. One possible cause is that you moved the game to another HD (not the same as where NMM downloads mod archives and creates the "Virtual Install" folder).

Weatherbee9 commented 3 years ago

Thank you very much for responding.

NMM was installed on both my I: and M: drives. The version on M: was the most recent version and the one I used. My Skyrim game, which I hadn't played for more than a year, was installed on I: drive. I was updating FNIS and other outdated mods (e.g., AddItem), but otherwise hoping to play my old modded game on drive I:.

The mods' esp's had been updated (judging by date modified in file manager). But, for example, "FNIS Behavior" adds many txt. files to its "TOOLS" folder. After trying to update with NMM not one txt file was transferred to "Tools" or any of its subfolders. The same was true for all other folders that should have had txt files installed. Likewise scripts were not installed. In the case of "AddItem", SKSE files as well as text and script files were not installed.

I have since uninstalled NMM from both drives. Before I reinstall it on M-HD where most of my games are installed (Fallout 3, 4 and NV; SkyrimSE, Witcher3, Far Cry 3,4,5& New Dawn, Assassins: Black Flag, Odyssey and Origins, etc.) I would like to know how to prevent this problem from recurring. Is it simply a matter of having NMM installed on the same drive as my games? Then I should move Skyrim to my M-drive. In the absence of advice from NMM experts, that is what I plan to do.

On the other hand, does my experience reveal a more fundamental problem with NMM? I hope not since I much prefer to use NMM rather than either MO2 or Vortex, regardless of what the naysayers claim are its many faults. I find it more intuitive and easier to use.

I used MO2 to play TTW and all worked well until I one day TTW would not start even though nothing had changed; nor could I discover how to fix it. Had a similar experience with Fallout 4. With NMM, starting over from scratch (if necessary) is a matter of hours (depending on the number of mods used) but with MO2 it would take me days. Vortex's dependence on LOOT which also has it faults, made Vortex a struggle I didn't want to deal with.

This is my way of saying how grateful I am that others continue to improve on NMM. Unless I'm told otherwise, in a few days I'll move Skyrim to my M-drive and do a clean install of NMM.