Fallout New Vegas: installing NVSE creates two "mods", NVSE not deployed

[javic666]

Fallout New Vegas, Windows 7 64-bit, Vortex 1.2.17. Fresh Vortex installation, fresh game installation.

 

Following Gopher's video on installing script extenders, I used the built-in method via Notifications to install NVSE as the first step in modding FNV. No other mods except "Vortex Archive Invalidation". After installing NVSE, on the Mods tab I now have two new entries:

 

1. New Vegas Script Extender (NVSE) - Enabled

2. nvse_5_1_beta6.7z - Never Installed

 

That's right, the NVSE archive I just downloaded appears in the mod list alongside it's installed cousin.

 

I clicked "Remove" for #2 and now it's gone. On the Dashboard, I made NVSE primary and launched the game through Vortex. I get a message saying deployment is pending. (No notifications about deployment appear at top-right in the main window.) Clicking "Deploy" allows things to continue but I see the FNV launcher come up so I already know NVSE isn't running. Continuing into the game and trying "getnvseversion" in the console confirms this.

 

My Vortex mod deployment folders contains "nvse_5_1_beta6" with the expected content, so that part looks correct. However, I have "Settings > Deploy Mods When Enabled" turned on but the game folder shows no trace of any NVSE file.

 

So I figured I'd try again. I removed the NVSE mod in Vortex, then reinstalled via "Install From File". This time, I get only one mod listed ("New Vegas Script Extender") but other than that, the behavior's the same. When I launch the game, I get the "deployment pending" message again. Clicking "Skip" or "Deploy" starts the FNV launcher, and NVSE isn't running. No NVSE files appear in the game folder.

 

In short, I'm unable to get NVSE deployed or running regardless of how I install it. Any help?

[HadToRegister]

I always install script extenders by hand, I don't care how many methods and workarounds they make for Vortex installing the script extender, the fool proof way, that takes less time is to just install it manually.

[ Installation ]

1. Copy the .dll and .exe files to your Fallout NV directory. This is usually in your Program Files folder under Steam\SteamApps\common\fallout new vegas\. If you see files named FalloutNV.exe and FalloutNVLauncher.exe, this is the correct folder. Do not copy these files to the Data folder as with a normal mod. The "src" folder is only useful for modders, most users can ignore it.

2. Launch NV via running nvse_loader.exe. Enabling the Steam Community option (enabled by default) will allow you to launch the game via Steam's standard UI.

[javic666]

Yeah, I can always do that--done it many times. It would have saved me time in this case. But I'm trying to give Vortex a fair shot so I can decide if I want to switch. In this case, it seems I might have encountered a bug (Gopher's video makes it look so easy) so I thought I'd let the devs know in case they want to pursue it. (Or I might have encountered a stupid user error, in which case *I* want to know about it. :-)

[HadToRegister]

Yeah, I can always do that--done it many times. It would have saved me time in this case. But I'm trying to give Vortex a fair shot so I can decide if I want to switch. In this case, it seems I might have encountered a bug (Gopher's video makes it look so easy) so I thought I'd let the devs know in case they want to pursue it. (Or I might have encountered a stupid user error, in which case *I* want to know about it. :-)

 

Where is your NVSE_Loader.exe located right now?

Along with the DLLS?

 

If they're in their own folder inside the game folder, then you did the Vortex conversion wrong.

The exe and dll should be right alongside the FalloutNV.exe

 

As I said, I've been using Vortex since Alpha, and I do not like using Vortex to install Script Extenders, it's easier to install them by hand, and using Vortex to install an incorrectly packaged Script Extender (if SilverLock just zipped up everything instead of putting it all inside another folder named after the Script Extender version) it would work right out of the box.

But it's a TERRIBLE Litmus test to base your opinion of Vortex on.

 

Although, If you downloaded the latest NVSE from GitHub, version 5.16, it's zipped up properly and doesn't need any repackaging

 

DO NOT FOLLOW GOPHER'S VIDEO if you're using the NVSE if you downloaded it from GitHub, it's already set up properly

[javic666]

Just to be clear, I'm very familiar with how NVSE should look in the game folder. I've manually installed it and other script extenders dozens of times.

 

That being said, things have gotten weirder because after going through this about 8 times, it's suddenly started working, so I guess I no longer have an issue.

 

For the record, I originally let Vortex download NVSE (as per Gopher's instruction) and it does indeed fetch 5.1.6 from GitHub which is not the one I want to use (I want to stick with the stable version). I also manually downloaded 5.1.4 from Silverlock and installed that in Vortex via "Install From File". As I said in my initial post, I got the exact same result with both techniques and versions: two "mods" in Vortex's mod list, deployment yielding no NVSE files in the game folder, a message about needing deployment when launching the game, and no NVSE running in game (obviously).

 

In summary, it appears that by mucking around with this for a few hours, I've cleared whatever bit was initially set that prevented it from working. So I can continue, but it's not an auspicious introduction to Vortex. :-/

[Zanderat]

To install SKSE (or NVSE) with Vortex 1.2.17, simply install it and deploy like any other mod. Your mucking around is not the fault of Vortex.

[javic666]

If you read me original post, you'll see that's exactly what I tried to do, and it didn't work, as I described in detail. That's the reason I posted this note in the first place.

 

It's only after "mucking around" (undoing and repeating the process 8 times) that it finally started to work as advertised (for reasons I cannot explain but would like to understand).

 

I know my original post was a bit long--I tried to provide as much information as possible, anticipating questions folks might ask--but c'mon. Is this not the correct forum for seeking help with Vortex issues?

[Pickysaurus]

The only reason for anything to get two entries in the mods table is if you staging folder is inside your download folder (or vice-versa)

[javic666]

My staging folder is "D:\Vortex\mods\falloutnv". My download folder is "D:\Vortex\downloads\falloutnv".

[Pickysaurus]

Try completely removing NVSE, then restart Vortex and follow the prompts to install it again?