Jump to content
  • 0
martincscheele

Missing plugin from FNVedit list (Tweaks & Fixes section)

Question

Hey all, I started on the modding guide this afternoon, and I'm running into trouble after creating the merged Tweaks and Fixes. I merged them like the guide says, and checked/unchecked the correct files in the left pane of the MO. But when I open FNVedit, "Tweaks and Fixes.esp" does not show up.

 

I'm not sure whats wrong. I'm not running FNVedit through MO, and thats the only thing wrong that I could think of since my time away from the computer today.

 

This is my first time modding a Bethesda game in years so any help is appreciated!

Share this post


Link to post
Share on other sites

6 answers to this question

Recommended Posts

  • 0

Welcome!

 

First things first:

 

This is my first time modding a Bethesda game in years so any help is appreciated!

This glourious, amazing work of art called Fallout - New Vegas is an Obsidian game my friend ;)

 

Now let's get serious, regarding your question:

 

Did you follow this step:

 

7. The mod now resides in the Tweaks and Fixes folder, inside the install>ModOrganizer>mods folder.

  • It may not show in MO's left panel, so click the small tool icon dropdown above the left panel and select "Refresh".

 

For me it's always the above. After merging stuff I have to "Refresh" MOs left panel and the new folder appears way down at the list. Activate this and you the .esp file should be there.

 

Looking foward for your feedback ;)

Edited by Gogan

Share this post


Link to post
Share on other sites
  • 0

I did do that - although it wasn't a folder, just a single option "Tweaks and Fixes" that if I check, the .esp appears on the right panel. However, when I go into FNVedit to generate the bash tags, the .esp is no longer in the list.

 

And of course, you're right! Pretty insulting to Obsidian for me to have said that, forgive me haha.

At this point I'm worried that I installed something wrong and should do a clean reinstall X.X

Share this post


Link to post
Share on other sites
  • 0

Does the .esp appear in LOOT?

 

Is FNVEdit correctly set up? Do you see the other plugins you installed?

Share this post


Link to post
Share on other sites
  • 0

I linked FNVEdit through MO (like the guide suggests) and this solved my problem. I've made my way through several other steps now, and have come across a few concerning things. None of the New Vegas Uncut mods had any errors in FNVedit and LOOT didn't say there were either.

 

 

Additionally, the Cut Content Merge didn't come up with any errors either, so I'm a bit wary as to whether or not I installed correctly. The bash tag "C.Light" was missing and "C.Acoustics" was in the list instead. 

 

I can start a new game without CTD so there's that. Thanks for all the help! 

Share this post


Link to post
Share on other sites
  • 0

I can start a new game without CTD so there's that. Thanks for all the help! 

 

Glad to hear and you're welcome ;)

 

The "missing errors" and different bashes could have to do with newer versions of FNVEdit/LOOT. Maybe they handle stuff a little bit different nowadays.

 

The F&L isn't the most up to date, so some stuff could be little different. But I personally think it's nothing too serious.

 

Eventually someone with more understanding of the matter could explain this better or correct me.

 

If you'll encounter some problems, just give a quick shout out.

Edited by Gogan

Share this post


Link to post
Share on other sites
  • 0

[...] I'm not running FNVedit through MO [...]

 

That is exactly what you are supposed to do. Configure FNVedit in MO to run through MO. Are you using it that way already?

Share this post


Link to post
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

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.