nt5raham Posted June 3, 2020 Author Share Posted June 3, 2020 So, is the final answer there is no way to correct Example 1 in Vortex? It will only work in MO2? Link to comment Share on other sites More sharing options...
Pickysaurus Posted June 3, 2020 Share Posted June 3, 2020 Vortex is not generating your bashed patch, so if it has masters you feel it shouldn't have, that's most definitely a Wyrebash problem. Link to comment Share on other sites More sharing options...
nt5raham Posted June 3, 2020 Author Share Posted June 3, 2020 When you hide a plugin in MO2 it's effectively invisible to the game, as if it was deleted.When you disable the plugin in the Plugins Tab of Vortex it is simply not enabled but technically the game can still see it. In Oblivion, having a lot of disabled plugins in the game directory could apparently cause performance issues (I never observed that myself) but to my knowledge this is not a problem with the newer games.So yeah, while disabling the plugin isn't technically the same for all intents and purposes it should have the same effect. Vortex is not generating your bashed patch, so if it has masters you feel it shouldn't have, that's most definitely a Wyrebash problem. What I'm doing is looking for clarification. Tannin42 said that hiding the .esp in MO2 is not the same as disabling it in Vortex. As I understand it, the documented procedure I am following does not create a Bashed Patch that is dependent upon the .esp hidden by MO2 because the game can't "see" it. That is a guess, and I'm looking for someone who knows. Apparently, since the game can still see it when disabled in Vortex, it is being included in the Bashed Patch. Again, a guess, and I'm looking for someone who knows. My lack of understanding is two-fold (maybe more, I'm still learning here): A. Is the inability of Vortex to hide the .esp causing it to be included in the Bashed Patch? B. If so, will I have to switch to MO2 to have the desired result, or is there an alternative in Vortex? Link to comment Share on other sites More sharing options...
HadToRegister Posted June 4, 2020 Share Posted June 4, 2020 When you hide a plugin in MO2 it's effectively invisible to the game, as if it was deleted.When you disable the plugin in the Plugins Tab of Vortex it is simply not enabled but technically the game can still see it. In Oblivion, having a lot of disabled plugins in the game directory could apparently cause performance issues (I never observed that myself) but to my knowledge this is not a problem with the newer games.So yeah, while disabling the plugin isn't technically the same for all intents and purposes it should have the same effect. Vortex is not generating your bashed patch, so if it has masters you feel it shouldn't have, that's most definitely a Wyrebash problem. What I'm doing is looking for clarification. Tannin42 said that hiding the .esp in MO2 is not the same as disabling it in Vortex. As I understand it, the documented procedure I am following does not create a Bashed Patch that is dependent upon the .esp hidden by MO2 because the game can't "see" it. That is a guess, and I'm looking for someone who knows. Apparently, since the game can still see it when disabled in Vortex, it is being included in the Bashed Patch. Again, a guess, and I'm looking for someone who knows. My lack of understanding is two-fold (maybe more, I'm still learning here): A. Is the inability of Vortex to hide the .esp causing it to be included in the Bashed Patch? B. If so, will I have to switch to MO2 to have the desired result, or is there an alternative in Vortex? Using WryeBash, especially when merging mods that WryeBash needs to disable is problematic, because WRYEBASH keeps the data in the Bashed Patch, that the ESP is still in the Load order,so when you hide it in Vortex, it causes a problem. So, when Vortex loads a bashed patch with a hidden esp, it still finds the dependency. The problem is with WryeBash and how it stores the hidden/disabled ESP within the Bashed Patch They both work together to a certain extent, but not when you get into the deeper aspects I just leave them enabled in Vortex and don't noticed anything odd. Link to comment Share on other sites More sharing options...
Zanderat Posted June 4, 2020 Share Posted June 4, 2020 I agree. I understand the question better now. Leave them enabled in Vortex. Wrye will disable them as part of creating a BASH Patch. If you back to Vortex after the BASH Patch is created, you will see the individual merged mods are now disabled. Note that Wrye no longer creates a merged patch for SSE and FO4 because they are unnecessary. Link to comment Share on other sites More sharing options...
nt5raham Posted June 4, 2020 Author Share Posted June 4, 2020 Awesome! Thanks to all for the info! I see that I've done all that I can, and I like Vortex and don't want to switch to MO2. LOL I need something that is more idiot proof to protect me from myself! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.