(SSE) Vortex sporadically doesn't detects some plugins (SkyUI, patches for incompatibilities, etc.)

[ExodusTransonicMercury]

I manually install only the mods that are required to (like the part 2 of SSE Engine Fixes), all other go through Vortex.

 

I don't think it's relevant, but I manually remove from /Data the plugins that Loot messages told me to delete (for example Hunterborn installed a iNeed patch plugin that I did not require).

[Guest deleted34304850]

that's entirely relevant.

how do you think vortex is going to know if you've manually installed a load of stuff?

[HadToRegister]

I manually install only the mods that are required to (like the part 2 of SSE Engine Fixes), all other go through Vortex.

 

I don't think it's relevant, but I manually remove from /Data the plugins that Loot messages told me to delete (for example Hunterborn installed a iNeed patch plugin that I did not require).

 

 

There's your problem.

 

NEVER, MANUALLY remove something.

 

WHY didn't you just uninstall the mod with Vortex?

Now Vortex has no ideas where that mod is, or what to do about it

[ExodusTransonicMercury]

how do you think vortex is going to know if you've manually installed a load of stuff?

 

I install manually what is required by the mod author to be installed manually.

 

 

 

There's your problem.

NEVER, MANUALLY remove something.

 

WHY didn't you just uninstall the mod with Vortex?

Now Vortex has no ideas where that mod is, or what to do about it

 

 

Like in the case of Hunterborn and its unwanted iNeed plugin that kept popping, because the plugins were added regardless of any options (I never delete the "main"/"core" plugin that way. Another example is a vampire amulet fix or whatever with Gemling Jewelry, IIRC. A lot more are unwanted/obsolete patches added erroneously while going through a FOMOD (such as installing the WACCF patch for some mod when the up-to-date CCOR patch is available/enabled).

 

There is also the case when Vortex doesn't remove plugins despite mods (though I expect it could be an error from the user, I haven't been through such problem recently). In the few posts/threads I've read on such problems, the community often advice to delete said plugins manually.

 

But none of the plugins deleted are related to the mods where Vortex issues messages and notifications about.

Vortex updates the list of plugins after the removal of the unwanted or obsolete plugins, ask me if I want to save that version of the mod (delete the unneeded files, as asked by Vortex), and the up-to-date patch (if one is needed) does his job. Vortex knows perfectly what's going on on that point, and doesn't ask about them once they're gone because they aren't needed (the mods are patched in an update or a better patch).

[Guest deleted34304850]

okay, you're not getting this.

 

do NOT install anything manually and expect your mod manager to know about it. No mod manager on the planet works like that.

If you mess about outside of the mod manager, then it's working as designed when it tells you something is missing because as far as it's concerned - it IS missing.

 

Your issues are because you are manually messing about outside of your mod manager. Don't do that, and your "problems" go away.

 

right now, what you're describing, how you've described it, the problem is your activity which is undermining your mod manager.

[HadToRegister]

 

how do you think vortex is going to know if you've manually installed a load of stuff?

 

I install manually what is required by the mod author to be installed manually.

 

 

 

There's your problem.

NEVER, MANUALLY remove something.

 

WHY didn't you just uninstall the mod with Vortex?

Now Vortex has no ideas where that mod is, or what to do about it

 

 

Like in the case of Hunterborn and its unwanted iNeed plugin that kept popping, because the plugins were added regardless of any options (I never delete the "main"/"core" plugin that way. Another example is a vampire amulet fix or whatever with Gemling Jewelry, IIRC. A lot more are unwanted/obsolete patches added erroneously while going through a FOMOD (such as installing the WACCF patch for some mod when the up-to-date CCOR patch is available/enabled).

 

There is also the case when Vortex doesn't remove plugins despite mods (though I expect it could be an error from the user, I haven't been through such problem recently). In the few posts/threads I've read on such problems, the community often advice to delete said plugins manually.

 

But none of the plugins deleted are related to the mods where Vortex issues messages and notifications about.

Vortex updates the list of plugins after the removal of the unwanted or obsolete plugins, ask me if I want to save that version of the mod (delete the unneeded files, as asked by Vortex), and the up-to-date patch (if one is needed) does his job. Vortex knows perfectly what's going on on that point, and doesn't ask about them once they're gone because they aren't needed (the mods are patched in an update or a better patch).

 

 

 

You don't need to manually DELETE any plugins, just DISABLE it on the plugin tab.

 

You messing around in the Data Folder manually Deleting and Adding ESPs is what's screwing up Vortex.

 

 

Just DISABLE the iNEED Patch in the Plugins Tab, along with any other Plugins that you didn't want added.

 

WHAT are the names of the Mod/patches that Vortex is saying you Need?

 

If it's telling you it needs something, go download and install it

 

 

 

[ExodusTransonicMercury]

This is going into circles.

 

Please read my answers, I'm repeating myself here (English is not my first language so I hope everything is ineligible here).

Though, I should have precised it from the start because an example (SSE Engine Fixes) wasn't enough: I don't add esp/esm/esl plugins, the only mods added manually are other kind of files ("utilities"), who need to be installed manually, virtually all authors stating it can't be installed via a mod organizer (or with a little tweak on Vortex to be applied during the deployment, can't remember on which mod/utility I've read that, but in the end it's safer to do it manually).

The plugins (such as a lot of WACCF patches are obsolete because of CCOR patches) have Loot messages (on Vortex) stating "Delete this".

Vortex knows about it (he detects the change). It doesn't care for them afterwards, because the needed patches are presents and the unneeded patches have been removed, and the intermittent messages are never about the deleted plugin. If they appears on the related core mod, Vortex will instead ask for the up-to-date plugin/patch, not the obsolete (that he asked to delete).

The notifications and Loot messages aren't related to the mods added manually nor to the plugins removed manually.

So no, Vortex isn't telling me something is missing because it is missing, because it isn't missing, that's two separate things as far as evidences tells me.

About the mods and patches, as I previously said:

- no patch (recently, WACCF_Armor and Clothing Extension.esp, but it doesn't appear anymore, though I have made no changes, such as deleting/ reinstalling/ updating/ disabling-enabling/ changing rules of order)

- Notifications mentions incompabilities between mods (JK's Skyrim + Dawn of Skyrim, and now LotD + Solitude Skyway) that are patched for compatibility.

I forgot to mention all messages and notifications almost always comes and goes together.

 

And for the final point, it's actually the issue of the first message: Vortex tells me to go and download something that is already installed, enabled and (seemingly, that's one of the reasons I'm asking if anyone knows what's going on and if a real problem is under those intermittent messages) working correctly. Installing it back with or without deleting it first doesn't changes anything.

 

I understand that you're both saying removing (adding isn't a concern here, for reasons mentioned previously) plugins is harmful to Vortex. But so far, the problem occurred BEFORE I learned it was (allegedly) safe to remove some stuff manually and started to do it when needed. I would have been inclined to believe the idea that the intermittent messages could be originating in a breaking of Vortex caused by removal of plugins, but the timeline doesn't fit.

Disabling might indeed make the trick, but for some reason, my Wrye Bash has some disabled -because they were obsolete- plugins to be enabled when creating the patch, despite being unchecked when starting the patch's creation (same happens for plugins disabled because part of a merged plugin)). Additionally, no problem has plagued the mods involved in the unneeded plugins' deletion. And as I said, Vortex is fine with them.

[HadToRegister]

17 posts later and we just now learn you're using WryeBash as well.


I assume you're making a bashed patch?
And the Bashed Patch is 'ghosting" or disabling some esps, so that when you load it back into Vortex, vortex no longer know what's going on and complain that ESPs are missing because they've been disabled by Wryebash or Ghosted.

[ExodusTransonicMercury]

I didn't brought up because it doesn't seem related or relevant to the issue I'm pointing out.

The false intermittent warnings (as far I know, they're just that) occur with an enabled obsolete bashed patch (minus its own relevant warnings), with an enabled up-to-date bashed patch, with the bashed patch disabled, and even before I started using Wrye Bash (for some reason, I've passed on using it for a couple years).

 

The plugins relevant to that problem are naturally disabled by zMerge, because that's how zMerge works. Vortex seemingly simply process Wrye Bash changes : the unchecked plugins, unchecked because zMerge unchecked them, are enabled by Wrye Bash. Vortex consequently re-enables (I'm not saying I know how Wrye Bash and Vortex work, I'm describing the process I've verified step-by-step. Plugins that sometimes prove problematic include Serana.esp and Telegendard.esp (who aren't related in any way to the false intermittent warnings in Vortex).

But please really read my messages : You and 1ae0bfb8 keep stating "you removed this, Vortex can't find it, its warnings are correct". As I said, I understood you're saying that removing manually plugins is (or at least can be) problematic. But I keep telling you "Anything Vortex asks is unrelated to the removed plugins and nothing is wrong with them and their related mods, Vortex issues warnings for mods and patches already installed". And again, as far as I know, everything is fine, except for the false intermittent warnings, and none of those plugins has anything to do with the mods where Vortex makes those false intermittent warnings.

Vortex knows what's going with them as well, except he doesn't mention the fact the enabled plugin is also part of a merged plugins (that could be useful to spot zMerge errors in the plugins disabling, if any) and Wrye Bash and manual accidental re-enabling).

 

If that is of interest (but it seemingly isn't), I use Bodyslide, FNIS, SSEdit and SSEdit Autocleaner, and zMerge. I quit using Loot standalone (on your advice) and dropped Merge Plugins (and re-created all merges in zMerge)