Jump to content

Plugins do not deploy in Fallout New Vegas


sensei23
Go to solution Solved by showler,

Recommended Posts

Windows 11 with latest Nvidia game ready drivers.

Vortex 1.11.5

Fallout New Vegas

Mods that will not deploy:

Johnny Guitar NVSE

JIP LN NVSE Plugin

Engine Optimizations

Mods that do deploy:

Yukichigai Unofficial Patch - YUP

The mods all show enabled in the Mods Screen. But when I go to the Plugins screen they are not  there. YUP does deploy to the Plugins screen, but I still must manually enable the plugins.

  Reveal hidden contents

Link to comment
Share on other sites

Ditto, similar for last 2 updates of Vortex and my 2 Bethesda games,  Fallout 4, and Skyrim. In every case all of the plugins (.esm and .esp files)  remain LISTED,  but about 9 times out of 10 ALL show as DiSABLED status every time I first look at them after opening Vortex (win 10 and Steam editions). I have over 120 mods in each list and typically run about 100 enabled selected. It makes no difference whether I deploy mods or not. Doesn't even matter if I click the refresh circle arrow icon under Plug-ins  tab or not.  They still show up gray deselected. I ALWAYS leave them selected enabled (active) EVERY time I exit Vortex. Then rarely for about 10% of the instances when I start Vortex, everything will appear correctly just as it was when it last closed.  It's frustrating and unacceptable. To avoid this,  whenever I'm NOT making any mod edits, I  can just avoid Vortex and launch modded games through desktop shortcuts to the respective script  extenders and play normally with all desired mods and plug-ins active. Seems like a bug to me that needs fixing. 

Link to comment
Share on other sites

First, your issue is unrelated to the OP's issue so you should have started a new thread.

Second, what you describe is most often the result of trying to use the in-game Bethesda mod menu at the same time as using Vortex.  They are not compatible.  If you have been using it, then please stop and see if the issue persists.

If it's not that, then there may be a permissions issue or configuration problem.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...