Jump to content

An Issue with Mod Counts Between Vortex and Wrye Bash


Skinjack

Recommended Posts

OK, since Wrye Bash states they cannot help with Vortex issues, I'll try to get everything you requested here.

 

I started a new install for Skyrim SE 1.5.80. I downloaded Vortex 1.0 to make the switch from NMM. Right now it says I have 192 Active mods & 79 Light mods on the Plugins Tab. The Dashboard says I have a total of 480 Active mods (I run a lot of graphic texture/mesh, interface, etc that don't have an .esp). At this point everything is right in the world. I use Wrye Bash to make a patch and it is happy. The game runs fine (so far) and the content of the Light mods that I Mark Light with Vortex seems to be in there (so far).

 

The problems start occurring with mod 193. Vortex is happy to Enable it, but when I run Wrye Bash it says I have too many files and removes the last one in the list (usually Modern Brawl Bug Fix). Yesterday it was giving me a warning to the effect that my load list is full. Sorry, I didn't think at the time to take a snapshot of that and its not giving me that warning this morning, just removing the last mod in the list.

 

I generally try to stay below 250 mods to not hit the limit wall, but Vortex is not even close to that limit, while Wrye Bash disagrees with it. With the game running fine at 192 Active and 79 Light I'm still at 271 total mods (which is over the limit), so I don't think it is counting all of the Light mods towards that count. The only thing I can figure is that it is counting enough of them to make my new Active mod limit as 192 .esp/.esm. I know .esl's aren't supposed to count against the count limit (within reason). Are the Lights somehow getting counted? Are they true .esl's/espfe's/etc? Am I using Mark Light wrong and I should forget it exists? I know I didn't mark 50+ mods as Light, maybe 10-15.

 

I'm running this on Window Pro 64 bit, with 24 16GB ram (Looks like I may have loose or bad memory there). GTX 780 with 8GB VRAM.

 

Any idea at all what might be going on?

 

I don't know if this is a Vortex issue or Wrye Bash issue, but the plugin counts definitely do not match between the two programs. I'm just not sure where to post this issue for Wrye Bash since their post says they can't help with Vortex issues.

 

EDIT: I don't know the results of this with Vortex, but can I take .esp patches not marked light and merge them with zEdit? I know they used to like them right after mods A & B, while some people said to merge them. I don't think there was ever a community consensus on that. What is the best advice to follow with Vortex? Should I just start compacting ID's to eslify the mods? Or is that generally frowned upon as well?

Link to comment
Share on other sites

I had thought he said he had fixed that with the latest version. Maybe that was my mistake and I downloaded it off the Nexus site instead of Github or Source Forge. I'm going to check my other version on another hard drive and see what version that is. (Crap, I deleted it)

 

Any work-around for this? I can't be the only one having that problem, right?

Link to comment
Share on other sites

I had thought he said he had fixed that with the latest version. Maybe that was my mistake and I downloaded it off the Nexus site instead of Github or Source Forge. I'm going to check my other version on another hard drive and see what version that is. (Crap, I deleted it)

 

Any work-around for this? I can't be the only one having that problem, right?

 

 

I only use WryeSmash to make a Bashed Patch.

I use WryeSmash standalone 307.201712232300 for Skyrim SE

 

I don't get any errors about too many files, but I only have 262 mods installed

 

 

Link to comment
Share on other sites

I only use Wyre Smash to make a patch as well, but I have 307.2018.0704.0057. Maybe that's the difference, because I didn't have this issue with Wrye Bash before. And I really only have the big number (480) when I include the mesh/texture/interface/etc files that don't have .esps.

 

I wonder if I could "downgrade" to the version you are using (if I can find it) to see if it makes a difference? How would I do that? Just completely uninstall it and run the older .exe, just putting it in the same place? Just asking because one of the Wrye Bash articles I was reading today was mentioning left over files that could mess with functionality.

 

EDIT: On a side note:

 

Something that has always bothered me (with NMM and Vortex). If I use Wrye Bash to merge these patches, NMM/Vortex has always said they can’t find them after that. Which meant I always have had to skip those in the Bashed Patch.

 

EBT - skyBirds Patch.esp - Enhanced Blood Textures SE

Obsidian_TS_Patch_Luminous_WaterFix.esp - Obsidian Weathers – True Storms Merged Compatibility

Obsidian_TS_Patch_Luminous.esp - Obsidian Weathers – True Storms Merged Compatibility

Qw_ACE_CRF Patch.esp - QUASIPC – Unified Patch Compendium v2_5_0

Qw_ArsMetallica_SMIM_MergedAll Patch.esp - QUASIPC – Unified Patch Compendium v2_5_0

Qw_BijinAIO_AIOverhaul Patch.esp – QUASIPC – Unified Patch Compendium v2_5_0

Qw_BijinAIO_CRF Patch.esp - QUASIPC – Unified Patch Compendium v2_5_0

Qw_PANNPCs_AIOverhaul_CRF Patch.esp - QUASIPC – Unified Patch Compendium v2_5_0

Qw_WACCF_OpenFaceGuardHelmetsSE Patch.esp - QUASIPC – Unified Patch Compendium v2_5_0

 

Why is that? Is there a way to fix that, or am I doing it wrong?

Link to comment
Share on other sites

I only use Wyre Smash to make a patch as well, but I have 307.2018.0704.0057. Maybe that's the difference, because I didn't have this issue with Wrye Bash before. And I really only have the big number (480) when I include the mesh/texture/interface/etc files that don't have .esps.

 

I wonder if I could "downgrade" to the version you are using (if I can find it) to see if it makes a difference? How would I do that? Just completely uninstall it and run the older .exe, just putting it in the same place? Just asking because one of the Wrye Bash articles I was reading today was mentioning left over files that could mess with functionality.

 

EDIT: On a side note:

 

Something that has always bothered me (with NMM and Vortex). If I use Wrye Bash to merge these patches, NMM/Vortex has always said they can’t find them after that. Which meant I always have had to skip those in the Bashed Patch.

 

EBT - skyBirds Patch.esp - Enhanced Blood Textures SE

Obsidian_TS_Patch_Luminous_WaterFix.esp - Obsidian Weathers – True Storms Merged Compatibility

Obsidian_TS_Patch_Luminous.esp - Obsidian Weathers – True Storms Merged Compatibility

Qw_ACE_CRF Patch.esp - QUASIPC – Unified Patch Compendium v2_5_0

Qw_ArsMetallica_SMIM_MergedAll Patch.esp - QUASIPC – Unified Patch Compendium v2_5_0

Qw_BijinAIO_AIOverhaul Patch.esp – QUASIPC – Unified Patch Compendium v2_5_0

Qw_BijinAIO_CRF Patch.esp - QUASIPC – Unified Patch Compendium v2_5_0

Qw_PANNPCs_AIOverhaul_CRF Patch.esp - QUASIPC – Unified Patch Compendium v2_5_0

Qw_WACCF_OpenFaceGuardHelmetsSE Patch.esp - QUASIPC – Unified Patch Compendium v2_5_0

 

Why is that? Is there a way to fix that, or am I doing it wrong?

 

 

Do you have Auto-Ghost turned on?

 

The way I use multiple version of Wrye Smash is just to keep everything in their own MOPY folder

 

Mopy1 Mopy2

Link to comment
Share on other sites

 

I had thought he said he had fixed that with the latest version. Maybe that was my mistake and I downloaded it off the Nexus site instead of Github or Source Forge. I'm going to check my other version on another hard drive and see what version that is. (Crap, I deleted it)

 

Any work-around for this? I can't be the only one having that problem, right?

 

 

I only use WryeSmash to make a Bashed Patch.

I use WryeSmash standalone 307.201712232300 for Skyrim SE

 

I don't get any errors about too many files, but I only have 262 mods installed

 

 

 

That's waaaaay out of date. I am on 307.201907230210. Fully supports ESL (can use to ESPify if you want).

Link to comment
Share on other sites

If Vortex is working as expected, then it must be a Wyrebash problem, it does sound like it doesn't support ESLs or ESL flagged ESP plugins.

Current versions (since early 2019) do.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

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