Vortex 1.13.3 is NOT using conflict override rules when displaying deployed mods on Plugins screen

[metalheadhr]

I am having a weird issue where conflicting mods are deployed either in random or most recently installed order rather than using the conflict override rules when deploying. I have tried redeploying; disabling "after mod" -> deploying -> re-enabling "after mod" -> deploying; purging -> deploying; reinstalling -> deploying. Only the reinstalling -> deploying method seemed to work but even that was overridden with the "before" mod being listed as mod archive in Plugins screen when I started Vortex today.

In the last month I have had system instability issues which required multiple Dell apps and XBoxApp reinstalls, System Restores and finally a Windows Update Repair-Reinstall. The Vortex issue began to be noticed late last week. I also made two significant hardware changes which was upgrading RAM and getting a FireCuda external game drive to which I moved both my Skyrim SE and Vortex's Skyrim mods directories. I also recently had to repair my Vortex install using Vortex-1-1-13-2-1733232693.exe after the System Restores and Windows Update Repair-Reinstall.

Current Specs:
 

Spoiler

    Vortex: 1.13.3 (12/10/2024)

    Skyrim SE: Best of Both Worlds Downgrade to 1.5.97

    Enabled Mods: 1782

    Disabled Mods: 71

    Uninstalled: 1114

    Never Installed: 4

    Windows Type: 11 Home x64

    Windows Version: 23H2

    Windows OS build: 22631.4602

    Windows Feature Experience Pack: 1000.22700.1055.0

    RAM: 64 GB (DDR5 5600 / PC5 44800)

 

[Pickysaurus]

Can you provide an example of two conflicting mods and how you can tell the rules aren't being respected? 

[metalheadhr]

Initial mod name: Sofia - The Funny Fully Voiced Follower - Sofia Follower v.2.51 (Loose)

Initial mod id: 2180

Initial mod file id: 29078

Initial mod deploy order: 8

Overriding mod name: Sofia Bug and Patch Hub - .esp replacer

Overriding mod id: 70950

Overriding mod file id: 297684

Overriding mod deploy order: 9

File being overridden is SofieFollower.esp which should be showing Sofia Bug and Patch Hub - .esp replacer for mod on the Plugins screen but instead shows the original mod Sofia - The Funny Fully Voiced Follower - Sofia Follower v2.51 (Loose)

 

I just double checked which file is currently deployed using BeyondCompare4 in the actual Skyrim directory and it is overridden there but still shows in Vortex what is shown in the screenshots. After redeploying again without changing anything, only doing file comparison between each mod's Vortex directory and the Skyrim Data directory, it still displays as shown below.

Edited December 12 by metalheadhr
Updated with more information to avoid double post

[7531Leonidas]

Did you try to set those rules while the mod is still installing?  I have found that if you do that on 1.13.3, that the rule does not really save.  If this is the case, try clicking on the conflict bolt, getting the rule window, and clicking on 'Save'.  Maybe it will help.  Good luck!

[metalheadhr]

25 minutes ago, 7531Leonidas said:

Did you try to set those rules while the mod is still installing?  I have found that if you do that on 1.13.3, that the rule does not really save.  If this is the case, try clicking on the conflict bolt, getting the rule window, and clicking on 'Save'.  Maybe it will help.  Good luck!

Unfortunately that isn't where my problem is since it doesn't matter when I view, set and save the rules it still acts as described above, even when I go and check them after several deployments where there are no changes and then deploying again.

[metalheadhr]

@Pickysaurus After doing an uninstall of Vortex and then installing from updated 1.13.3 download file, but leaving settings files in place, I am still getting the same issue displayed in my screenshots above where it doesn't display the deployed mod correctly in the Mod field of the Plugins screen. But when I go to do a file comparison on the deployed Skyrim\Data directory it is has the correct version of the file from the correct mod deployed.

So for the example in the above screenshots, the displayed mod on the Plugins screen is Sofia - The Funny Fully Voiced Follower - Sofia Follower v.2.51 (Loose) but the deployed version in Skyrim\Data is from Sofia Bug and Patch Hub - .esp replacer. This is happening with other mods as well, both downloaded from nexus site through Vortex and those manually added to Vortex through Import, just chose that one as an easy example.

Hopefully there is a solution other than needing to uninstall and completely delete all Vortex related directories and then rebuild from scratch.

[metalheadhr]

@Pickysaurus After doing more testing, it is still occurring. I even went and uninstalled, deleted the Vortex folder in AppData\Roaming\Vortex, then reinstalled leaving the previous download, staging, and deployment directories untouched other than using the Purge function on my Skyrim SE profile prior to uninstalling.  The only other thing I can think of to do is to completely uninstall, wipe those directories and completely rebuild from scratch. Any suggestions would be helpful because at this point I think only a complete rebuild will fix it.

 

Edited 12/22/2024 @ 16:55

Some more testing and I am now able to get it to display on Plugins screen the correct mod for the loaded plugin through the following steps.

1. Start Vortex

2. Check Mod screen

3. Check Plugins screen

4. Run Deploy Mods

5. Check Plugins screen to see if it shows it correctly (which it doesn't)

6. Check Mod Conflict Rules and Save

7. Rerun Deploy Mods

8. Check Plugins screen and verify that it is now showing the correct mod for the plugin file (which it usually does)

9. if it doesn't restart Vortex and restart the list of steps

Edited Sunday at 09:55 PM by metalheadhr
Added more info about issue

[Nagev]

Hi there @metalheadhr

First of all, thanks for bringing this to our attention, your tests are appreciated and did indeed highlight a bug.

After running some tests on my end, this appears to be a visual bug in the plugins page.

As you can see in the snippet above, although the plugins page is defining the LOOSE version as the source, the deployment manifest itself is using the correct source. You can double check this yourself on your end - open up your "vortex.deployment.json" file and look for the ".esp replacer" source. (Searching by "SofiaFollower.esp" will match too many entries from the original mod)

This will be fixed in Vortex 1.13.4 which will be released sometime in the new year.

P.S. In the future please report any such issues on our issue tracker as it offers better visibility: https://github.com/nexus-mods/vortex/issues