ESL flagging with Wrye Bash being removed by Vortex

[Hatchet101]

I have been using Wrye Bash for quite a while now, and generally build my bashed patches without issue. When I start Vortex to install or deploy, it will run a first time deployment and notify me of the changed ".ESL" flagged files and prompt for acceptance of "Externally Modified" as usual.

Once deployed, Vortex then strips all the .esl flags and tells me that I have exceeded the 255 limit. I currently run around 245-248 .esp/.esm and about 125 .esl / .esl flagged. Flipping through Wrye Bash works much faster than Vortex for flagging, but with Vortex removing those flags it is extremely annoying. I foresee myself beginning to merge mods in xEdit fairly soon, so as to not have to deal with so many flags, but being stable comes first.

I have also used Vortex' flagging as a test with 2 files that were previously flagged in Wrye, and Vortex still recognizes those 2 files as being "Externally Modified". I am now attempting a full .esl flagging with Vortex where applicable, and maybe will have a clearer answer in a day or two when Vortex finally finishes.

 

Is there a patch I am missing that makes Vortex and Wrye Bash play nice with each other?

 

 

[Pickysaurus]

Could you give a step-by-step process to replicate this? I know you sort-of did, but a simplified list of instructions would be handy.

 

I'm fairly sure this is more of an issue with how Wyrebash changes the files, than anything else. Vortex would only revert the changes if you told it to via the "external changes" window.

 

If you didn't already know, you can batch mark plugins as light with Vortex. Click one plugin, then hold Ctrl and click on each of the other ones you want to include. (You can also do Shift+Click for groups or Ctrl + A for everything). Once you have the plugins highlighted use the "Mark as Light" option on the toolbar that appears at the bottom of the table.

 

Note: In 1.3.17, Vortex doesn't reload the table after doing this, so click "Sort now" to update the details of the plugins.

[Hatchet101]

Could you give a step-by-step process to replicate this? I know you sort-of did, but a simplified list of instructions would be handy.

 

I'm fairly sure this is more of an issue with how Wyrebash changes the files, than anything else. Vortex would only revert the changes if you told it to via the "external changes" window.

 

If you didn't already know, you can batch mark plugins as light with Vortex. Click one plugin, then hold Ctrl and click on each of the other ones you want to include. (You can also do Shift+Click for groups or Ctrl + A for everything). Once you have the plugins highlighted use the "Mark as Light" option on the toolbar that appears at the bottom of the table.

 

Note: In 1.3.17, Vortex doesn't reload the table after doing this, so click "Sort now" to update the details of the plugins.

I have my entire mod list installed and managed by Vortex, with exception of ENBs and Mem manager installed to the exe root. After installing a new mod with Vortex and running a deployment, I shut down Vortex and launch Wrye. All esl flags that may have existed previously are automatically reset and only non-EFesp' show as esl. I manually go through the list of mods, checking each file for flag compatibility, and flag appropriate files to bring my esp plugs to under 250ish. Then rebuild the patch. Exit WB, start Vortex again, and wait for the prep phase to complete, then run Deployment to completion with confirmation of using newer files that have all been esl flagged. After the "Snapshot" step, Vortex reverts ALL esl to esp (even non EF) and warns that plugins exceed the max 254 with the whole mod count showing as if esp/esm were the only types. Re-deployment will then show true .esl as light plug in, but all EF are reverted back to esp and the warning continues. Closing Vortex and going back to Wrye yields the over-limit warning, and subsequent disabling of random plug-ins to get back to 254 esp/esm. In essence... start all over.

 

I just finished with flagging all esl in Vortex, and am deploying 244 esm/esp and 135 light as I write this, with hopes of getting about 6 more esp in for Cities of the North mods or Epic cities, and maybe a follower or two, before I begin to merge where possible. Load orders already sorted, bashed patch last, etc.

Fingers crossed on being stable.

[HadToRegister]

When using WryeBash and Vortex together, the most you should be using WryeBash for, is to load up and make a bashed Patch.
Then exit and manage your load order etc with Vortex.

I use WryeBash as a "Utility" in Vortex.

 

I believe the problem now is, Vortex is detecting the file changes that WryeBash is making, and then when it notifies you that Files have Changed OUTSIDE of Vortex, you're telling Vortex to REVERT rather than SAVE the changes or USE NEWER FILE.

[Hatchet101]

When using WryeBash and Vortex together, the most you should be using WryeBash for, is to load up and make a bashed Patch.

Then exit and manage your load order etc with Vortex.

 

I use WryeBash as a "Utility" in Vortex.

 

I believe the problem now is, Vortex is detecting the file changes that WryeBash is making, and then when it notifies you that Files have Changed OUTSIDE of Vortex, you're telling Vortex to REVERT rather than SAVE the changes or USE NEWER FILE.

I was saving the changes from Wrye in Vortex, and the Deploy appears to work at first onset, but as stated, as soon as the "snapshot" is done being saved, the plugins are disabled and all manual changes get reverted. I have set everything with Vortex now, and am in for 4 good save game files, no dirt or issues reported from re-saver, and only one CTD since scripts were loaded at onset. I will look at installing the next couple mods in esp, esl, and FeEsp and see how it goes. I have not looked at anything with Wrye since, and suppose I won't if all goes well in Vortex and xEdit.

[Zanderat]

Just tested this. Not user error.

 

Steps taken;

• Open Wrye (through Vortex)
• Select a qualified mod (WACCF_BashedPatchLvlListFix.esp) and change it using the "Add esl flag" option in Wryte.
• Close Wrye
• Check Vortex plugins tab. The change is recognized.
• Deploy mods in Vortex.
• Select the "newer file" option in the External Change Dialogue prompt.
• Check Vortex plugins tab again, after deployment completes.
• Plugin has been reverted back to its original state.

[HadToRegister]

 

Just tested this. Not user error.

 

Steps taken;

• Open Wrye (through Vortex)
• Select a qualified mod (WACCF_BashedPatchLvlListFix.esp) and change it using the "Add esl flag" option in Wryte.
• Close Wrye
• Check Vortex plugins tab. The change is recognized.
• Deploy mods in Vortex.
• Select the "newer file" option in the External Change Dialogue prompt.
• Check Vortex plugins tab again, after deployment completes.
• Plugin has been reverted back to its original state.

 

 

 

Now, convert it to ESL in Vortex, load it up in Wrye, close wrye and load it back up in Vortex.

 

Does Wrye Convert it back?

[Zanderat]

 

 

Just tested this. Not user error.

 

Steps taken;

• Open Wrye (through Vortex)
• Select a qualified mod (WACCF_BashedPatchLvlListFix.esp) and change it using the "Add esl flag" option in Wryte.
• Close Wrye
• Check Vortex plugins tab. The change is recognized.
• Deploy mods in Vortex.
• Select the "newer file" option in the External Change Dialogue prompt.
• Check Vortex plugins tab again, after deployment completes.
• Plugin has been reverted back to its original state.

 

 

 

Now, convert it to ESL in Vortex, load it up in Wrye, close wrye and load it back up in Vortex.

 

Does Wrye Convert it back?

 

I will check. But Vortex is putting back the staging folder version. Wrye should just recognize whatever is there.

 

edit: did above steps (made change in Vortex, opened/closed Wrye (shows correctly in Wrye), opened Vortex (redeployed, choose "use new file" option). This time the change was kept.

 

So definitely a bug with changes made outside Vortex.

[HadToRegister]

 

I will check. But Vortex is putting back the staging folder version. Wrye should just recognize whatever is there.

 

 

edit: did above steps (made change in Vortex, opened/closed Wrye, opened Vortex (redeployed, choose "use new file" option). This time the change was kept.

 

So definitely a bug with changes made outside Vortex.

 

 

Definitely one for the report function then.

[Zanderat]

^^^Already done. :cool: