Cannot specify custom Mods directory for NMM when trying to import mods

[OMC37]

I'm trying to import mods from NMM but the default directory shown below no longer exists, and instead is on a separate drive. It won't let me interact with the file path here, and no other paths are listed in the drop down menu. How do I point this import tool towards the correct directory? (In my case: D:\Nexus Mod Manager\FalloutNV\Mods)

I read elsewhere that it's reading this path from something related to NMM, so it's possible there's an outdated file in appdata that was left over from moving my computer to an SDD that contains this file path. NMM currently works and is running off of the most recent community version, so I know that the NMM install itself is not corrupted. If I could simply modify this field somehow it would solve the issue.

 

 

 

[HadToRegister]

Then you need to find the NMM config file that Vortex is reading from.
It sounds like you moved your NMM folder without moving it properly using NMM.

I would advise against having Vortex import your NMM mods, because NMM has a habit of corrupting the config file that Vortex needs to successfully do the import.

Try Vortex on a different, unmodded game first to familiarize yourself with it

 

Does clicking the drop down shown in your screenshot show another install of NMM?

[OMC37]

Then you need to find the NMM config file that Vortex is reading from.

It sounds like you moved your NMM folder without moving it properly using NMM.

 

I would advise against having Vortex import your NMM mods, because NMM has a habit of corrupting the config file that Vortex needs to successfully do the import.

 

Try Vortex on a different, unmodded game first to familiarize yourself with it

 

Does clicking the drop down shown in your screenshot show another install of NMM?

 

I just solved it, I finally found the config file under the badly named folder Black_Tree_Gaming. The problem stemmed from my install of NMM requiring admin permissions, causing the installer to only update the config file of the admin side without installing for all users, which left the outdated config file on my user side alone. I was running vortex without admin permissions and NMM with admin permissions, which meant NMM functioned as I would expect while vortex was reading from the outdated normal user side. I updated the config file to match the admin config file and now the correct file path is showing in the dropdown menu.

[HadToRegister]

 

Then you need to find the NMM config file that Vortex is reading from.

It sounds like you moved your NMM folder without moving it properly using NMM.

 

I would advise against having Vortex import your NMM mods, because NMM has a habit of corrupting the config file that Vortex needs to successfully do the import.

 

Try Vortex on a different, unmodded game first to familiarize yourself with it

 

Does clicking the drop down shown in your screenshot show another install of NMM?

 

I just solved it, I finally found the config file under the badly named folder Black_Tree_Gaming. The problem stemmed from my install of NMM requiring admin permissions, causing the installer to only update the config file of the admin side without installing for all users, which left the outdated config file on my user side alone. I was running vortex without admin permissions and NMM with admin permissions, which meant NMM functioned as I would expect while vortex was reading from the outdated normal user side. I updated the config file to match the admin config file and now the correct file path is showing in the dropdown menu.

 

 

Excellent!

Glad you got it working