If you’re not, click the “Log in” link at the top-right corner of the web page. If you’re logged in, you’ll see “’s account” at the top-right corner of each web page.
You can now head to the Fallout 4 Mods category page to browse and search the available mods. You’ll then see a “Logged in” message here, informing you you’re logged in.
Enter your Nexus Mods username and password here.
To do so, click the profile icon next to “You are not logged in” at the bottom-left corner of the Nexus Mod Manager window. You’ll want to sign into Nexus Mod Manager with your Nexus account for easy mod installation. Click “OK” to save your settings and Windows will always launch Nexus Mod Manager with Administrator permissions. To always run it as Administrator, right-click the shortcut and select “Open file location.” Right-click the “Nexus Mod Manager” Shortcut, select “Properties, click the “Compatability” tab, and enable the “Run this program as an administrator” checkbox. Alternatively, keep the default folders and run Nexus Mod Manager as an Administrator. To do so, right-click the Nexus Mod Manager shortcut and select “Run as administrator.” To solve this, set the folder paths to something like C:\Users\YOURNAME\Documents\Nexus Mod Manager\Fallout4. If you run it normally, you’ll see an error informing you that Nexus Mod Manager is “unable to get write permissions for” the directory. It won’t work unless you run Nexus Mod Manager as Administrator.
There’s a problem with these default folder settings. By default, Nexus Mod Manager will store these files under C:\Games\Nexus Mod Manager\Fallout4. Click “OK” to continue and you’ll see a Fallout 4 Setup screen. You’ll be informed that you need to set up the paths where Nexus Mod Manager will store mod-related files. Select “Fallout 4” in the list of installed games and click “OK.” If you always want to use this program to manage Fallout 4 mods, click the “Don’t ask me next time” checkbox here. Just click the checkmark to confirm Fallout 4 is installed at that location and then click “OK.” If you have Fallout 4 installed, it will find it.
Launch Nexus Mod Manager after you install it and it will search your PC for games.
You’ll be asked to sign up for a paid supporter membership during the sign-up process, but you can just scroll down to the bottom of the page and click “Create Account” to continue.
If you don’t yet have a Nexus Mods account, you’ll be informed you need to register for a free account to download it.
However, we recommend using the Nexus Mod Manager tool to make this process easier and reduce the risk you’ll break something while installing a mod.ĭownload Nexus Mod Manager and install it on your PC. It’s possible to manually install mods for a lot of games, or use Steam’s built-in Workshop (for games that support it). How to Install and Configure Nexus Mod Manager
Fallout 4 will now accept and use the mods you install. Add the following lines to the end of the file: Ĭlick File > Save to save the file, and then close Notepad. Add the following line below it: bEnableFileSelection=1Ĭlick File>Save to save the file, and then close Notepad.ĭouble-click the Fallout4Custom.ini file to open it in your default text editor. My guess is either av was scanning and locked the file temporarily, or becasue I enabled multiple mods quickly, fnis tripped over itself somehow.Scroll down to the very bottom of the text file and you’ll see a section. I was deploying multiple mods quickly, none should have required fnis to run as they didn't contain animations. I would expect since vortex is calling fnis that it would pass the error (when there is one) and request feedback on what to do (exit or run again) rather than hang forever with no indication of what's wrong.įirst time I've seen this, so I don't know how to reproduce. Exited fnis manually and the deployement completed with no further interaction. This is odd because I had nothing open that would be accessing that file, nor did the mods I was enabling require fnis. There I found fnis had an error that it couldn't complete because a file was in use. Opened task manager and found the fnis process and switched to it. Deployment wasn't proceeding and there was no feedback other than it was on the fnis step.