oaabdellatif

Try deleting the shortcut, then recreating it. Keep in mind you don't need to launch SKSE from Vortex for your mods to work; Vortex is not MO.

This has already been discussed by Tannin in his stickied post over in the feedback forum here. In short, DO NOT install your mods to Vortex's installation directory, as it's deleted every update. I figured this would've been obvious, but for some reason people have been changing the defaults. Future versions of Vortex from 0.13.5 on will prevent you from doing this.

The bug is in the new Morrowind plugin management extension specifically. Modding Morrowind itself still works fine.

Exact same thing happened to me when it tried to auto update. I've already gone ahead and reported it. I have had any issues with it timing out though; logging out and back in could help.

One thing Vx doesn’t always do well is give feedback when it’s doing something or when it’s finished. Did you wait a bit after Purging or immediately Deploy? I’m not sure if these ops are queued or if they can be left incomplete. But I’d try purging and then after a short wait examine your data directory to see if it looks clean. There are occasional bugs where it doesn’t clean up properly after a purge. I’m also unclear on whether deploying on a dirty data dir will overwrite existing links? I wish we had another more aggressive purge option. When Vortex is doing something there'll always be a notification shown, such as when it's deploying mods. I haven't had any issues with them not showing up when something is happening personally. I'm not sure what was going on in OP's case though, to be honest. It's more likely that he set his rules incorrectly than anything else. Purging your mods is only necessary if you need to get back to a clean data directory. Vortex should automatically deploy any changes you've made. If it doesn't, make sure to file a bug report.

The ENB mod type extension exists but is currently disabled due to some problems. It'll like be fixed and pushed out when the full release rolls by.

Make sure the plugin is enabled under the plugins section in Vortex. Also, if the game is being launched through SKSE64, you should see a command prompt window come up and close immediately before it launches.

Being able to see a list or some visual representation of all the rules you've set would definitely be a useful feature, since as of now you would have to check each mod that have conflicts to see them. I was thinking of having a graph like in the original post just showing the mods involved in the cycle be shown in the error messages, rather than making the user search through a graph of all their rules, although I would like to see both included.

To be honest, I always use LOOT and I have never actually managed to do this regardless of the size of my load order. For example, from the graph, it looks like more rules are being set up then is actually needed. If I am understanding this correctly. RCI comes before NSM, SMIM, and ELFX SMIM comes before NSM, and ELFX NSM comes before ELFX What appears to be 6 rules in total. But could you not just set it up in the same order with these 3 rules? RCI before SMIM. SMIM before NSM. NSM before ELFX. Or am I misunderstanding something here? Edit: Also, keep in mind if LOOT's automatic sorting puts it in the correct order by itself, you don't need to create rules. So just in case, I would always check to see where LOOT places things first before creating rules and only create the rules that are absolutely necessary while doing it in the least amount of rules. Obviously, if RCI needs to load before SMIM and SMIM needs to load before NSM, that means RCI can never load after NSM anyway because that would be contradictory, so you don't need a rule. The more unnecessary rules you create the more likely you will accidentally create a cycle. I suppose for the average user this could be a problem, but I would reckon for the average user, they probably wouldn't be creating rules in the first place unless absolutely necessary. Granted, I do think there needs to at least be a way to track these things down more easily. It would be nice if Vortex can point out specifically which mods are the issue. My original post refers to loose file rules, not LOOT rules. Apologies if that wasn't clear. I imagine it would be much more difficult to create a cycle like this with LOOT rules.

Note: I'm referring to loose file rules in this post, not LOOT rules. So, I ran into a bit of an issue while setting up my mod list in Vortex for Skyrim. In setting up the mod rules in the proper order, I had created a rather difficult cycle between four different mods: SMIM, ELFX, RCI, and NSM. The problem is that Vortex's description of the cycle is completely useless. It only lists the mods involved, and doesn't give any indication of where the cycle is and how to resolve it. To address the issue, I had to draw out the rules and see what was going on. Each node or circle represents a mod, and the arrows represent a rule. The direction of the arrows represents the overwrite order, so the mod being pointed to loads after the previous mod. The cycle is very easily seen in this graph; there is one between SMIM, ELFX, and RCI, and another between ELFX, RCI, and NSM. To resolve the cycle, I reversed the rule between ELFX and RCI. Problem solved. Now there is no circular dependencies between any of the mods. Essentially what I'm asking is for a better visual representation of issues like this. The average user would've been pulling their hair out to figure out how to fix it. In MO, when I encountered a cycle like this, I would've noticed while trying to set up the priority that there was no way to arrange them to satisfy the first graph.

The problem with the ads is on your end. You have an option to not see them anymore. True. Its called Adblock. :smile: You seem quite proud to freeload off of Nexus' servers. Maybe they should make downloads premium only. Last time i checked it was a free service. Maybe they should make downloads premium only. Would be interesting to see members and visitors count if that happens. Funny how i start helping with finding program bugs and issues as a non-premuium or "non-supporter" and i get told by "supporters" that i should give my hard earned money to one site on the internet so that i don't see ads in a program im helping to fix. Not to mention i already said i dont mind ads but the amount of ads. But why bother reading when you can pretend to be higher. That was not my intention. As you can see, I'm not a premium user either. My point is, free to use does not mean free to operate, as Tannin has already made clear. Ads allow Nexus Mods to support itself without charging every user who wishes to use it. In addition, they've hired two new developers and are looking to hire a third, so they need to expand their revenue to compensate. This is probably the rationale for the ads inside of Vortex. While I agree it could be a little bit less intrusive, ultimately I don't have much of a right to complain.

Yes, but at the moment you'll have to do it manually after you install a mod. Under the mods section, if you click the "open with file manager" button, it will open up the folder that contains the data folders for each of your installed mods. You can then either rename or delete the files you don't want to have active in each mod.

The problem with the ads is on your end. You have an option to not see them anymore. True. Its called Adblock. :smile: You seem quite proud to freeload off of Nexus' servers. Maybe they should make downloads premium only.

I had a quick look at the code for the archive invalidation extension, and I can confirm that it currently only supports backdating BSAs for Skyrim, Skyrim Special Edition, and Fallout 4. Hopefully Tannin will implement the rest of the functionality required for older Gamebryo games soon.

It sounds like archive invalidation isn't working properly. I remember reading another thread where someone was having issues with a texture pack not showing up in game with Oblivion. Vortex should've given you a prompt to reset the archive dates, but it may not be doing anything more than that. Try setting up ArchiveInvalidation Invalidated and see if that fixes it.