Jump to content

Question

Posted

Following L&LNV STEP guide, it's great. I installed Wrye Flash NV and set it up with MO, as instructed.  At first it had worked to make a bashed patch.

 

Now at some point Wrye Flash stopped seeing the bash tags (empty box in the lower right corner of the main screen when you select a plugin in the list), and there is no empty bashed patch that I can click on to rebuild it.  I created a new profile at some point, and it might have happened around that time, but going back to the original profile doesn't fix it either.

 

LOOT still shows them in green in the detail list it produces after sorting the plugins.

 

 

Anyone knows a solution for that?

I thought I saw something about that on the forum, but kept searching and can't find a solution.

 

11 answers to this question

Recommended Posts

  • 0
Posted

That is a weird bug. Delete the bashed patch, 0.esp and get a new one from the mopy/template folder (I believe that is the right one). There will be some error the first time you try to use it, so ignore it.

 

Also, what version of Wrye are you using? Version number and python or standalone?

  • 0
Posted

Thanks for looking at this.

 

Wrye Flash version: "16.0 (Standalone): Default [1.4]" standalone, I had the requirements already installed, probably from Wrye Bash for Skyrim or Oblivion.

 

What I did through the installation is:

- installed the game under the "default" MO profile

- followed the STEP guide, made a new "Fear and Loathing" profile by copying the default one (step 1.2 of Setting up Mod Organizer)

- created a "TTW" profile from copying the "Fear and Loathing" profile to install TTW, but this time I used the 'Local Savegame' option

 

So I have:

- from MO Saves tab, in the right pane, if in "default" or "Fear and Loathing" profile, I see those 17 first saves

- from MO Saves tab, if in the "TTW" profile, I see the new ones

- in Wrye Flash, launched from MO, I only see the 17 default/F&L saves

- in the whole SteamApps/common/Fallout New Vegas there is only one bashed patch: 'Bashed Patch, 0.esp" in Mopy/templates, no clue how the other disappeared

 

Where do I put the copied bashed patch from the mopy/template folder?

  • 0
Posted

Put it in the Data folder. And, if the Bashed patch, 0.esp is already there, then rename it Bashed Patch, 1.esp. Then see if it takes the bash tags.

 

If it doesn't you may need to report it to the Wrye thread on the FNV nexus or the Wrye thread on the Beth forums for Skyrim.

  • 0
Posted (edited)

Worked, thanks a lot.

 

- Copying the 'Bashed patch, 0.esp' from template to the Data folder fixed the 'no bashed patch' problem.

- still no bash tags in Wrye Flash, so I put them manually based on LOOT, and they seem to be sticking there

- I'll see what happens the next time there's a new mod with a bash tag, if I have to do it manually or not

 

If I find out something new/interesting about it, I'll post it here.

Edited by Acheos
  • 0
Posted (edited)

I have the same problem after updating from BOSS to LOOT. With LOOT bash tags suggestions do not update automatically in wrye bash for new mods. If i reinstall boss back to normal.

 

Are you sure that loot is working with wrye flash? or do i have to put them manually?

Edited by coldbyte
  • 0
Posted

Do you have the latest version of Wrye Flash because it should take the tags? I don't really have problems with that. Maybe Wrye has just carried them over from all the times I used to run BOSS. I know that Wrye is going through it's updates for LOOT right now, but there is no ETA on that.

  • 0
Posted

I was using Wrye 15.9 when i started to notice this, the missing tags were only on new mods. For exemple New Vegas Bounties II in wyre flash didn't have relations, ADAM that was fixed in loot also didn't have the tags...Then i deleted all the files from Wrye flash 15.9 and installed Wrye flash 16, and now i have no bash tags at all.I can put back the bash tags manually or use BOSS

  • 0
Posted (edited)

Yes, except the Unrecognised mods.

Wrye Flash from i can tell reads from:

SteamAppscommonFallout New VegasBOSSFallout New Vegasmasterlist.txt
SteamAppscommonFallout New VegasBOSSFallout New Vegasuserlist.txt
SteamAppscommonFallout New VegasDataBash Patchestaglist.txt

LOOT keeps the files in:

C:Users<user>AppDataLocalLOOTFalloutNVmasterlist.yaml
C:Users<user>AppDataLocalLOOTFalloutNVuserlist.yaml

I don't think that Wrye Flash reads from them.

 

The reason why i had no bash tags in Wrye Flash 16 was because taglist.txt was empty by default.

 

Since order works well with loot, i copied masterlist.txt to "Fallout New VegasDataBash Patches", renamed to taglist.txt, removed BOSS and the unrecognised mods i added manually to Wrye Flash using LOOT as a guide.

I don't think loot is working for bash tags especially for new users.

 

Correction:

I was looking at the taglist.txt from Wrye Flash 15.9 and the file  masterlist.txt file needs to be clean, use the one in Wrye Flash 15.9 or download the script folder from https://github.com/Wrye-Bashers/Wrye-Flash-FalloutNV/tree/master  and run "Build Taglist.bat"

Edited by coldbyte
  • 0
Posted

That's really weird. I haven't had a lot of problems with LOOT except for some weird stuff going on with cleaning info for the alpha version. I may have to look into this and see what's going on. I've been so focused on gettin gthe LOOT master list updated that I forgot to look into the actual list working at all.

  • 0
Posted

Sorry to necro this thread, however to keep people in the know... Both of Valda's versions don't have LOOT support, only BOSS support. The BOSS master lists are locked and can't be changed. Manually tagging the mods or adding the bash tags to the plugin header are the built in ways to add tags without LOOT or BOSS.

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 Guidelines, Privacy Policy, and Terms of Use.