Jump to content

An update on Vortex development


Dark0ne

Recommended Posts

  • Replies 443
  • Created
  • Last Reply

Top Posters In This Topic

In response to post #54943263. #54946513, #54952193, #54952693, #54954443, #54955813 are all replies on the same post.


  Reveal hidden contents


Speculation aside, I never suggested mod authors "needed" anything from their mod manager. I even listed a few work-arounds I've been using to make things work. And it does work.

I never even suggested mod users technically "needed" anything from their mod manager. Modding existed before mod managers and it worked. That doesn't mean the experience isn't objectively better because of it.

I'm not saying mod author's won't manage without it. I'm saying that things could be a lot better for the experience of mod creation, and I haven't seen any evidence to suggest that's even been a consideration. And even if the user's experience is all you cared about, given how the line between use and creation has been blurred with people cleaning their own plugins with xEdit, bodyslide mesh creation, etc., I think it deserves at least a little consideration.
Link to comment
Share on other sites

In response to post #54957218. #54958828 is also a reply to the same post.


  Reveal hidden contents


If you scrolled down just a tiny bit you'd see Tannin answer this question. He's also said before that it won't touch your existing installation, so you can safely test your installation on Vortex and still go back to your already working installation if Vortex doesn't quite get everything.
Bear in mind that you'll probably be using a metric buttload of disk space until you pick one and get rid of the other though.
Link to comment
Share on other sites

In response to post #54959113. #54959528, #54959868, #54960743, #54961303, #54963573, #54963743 are all replies on the same post.


  Reveal hidden contents


  Quote
The ability to instantly find conflicting files etc were its biggest draw for me.

The vast majority of the "conflicts" reported by MO are false positives, so much so that as a conflict management tool, MO is completely useless.

I posted the following in 2014 on a forum that Tannin frequented. He wasn't interested in fixing the problem.
  Quote
I have installed a number of location mods that appear to have conflicting assets.

- Heljarchen Farm
- Immersive College of Winterhold
- Morskom Estate
- Vjarkell Castle
- Windstad Mine

I extracted each BSA and generated MD5 hashes for every file in each directory.

I imported the results into a spreadsheet and confirmed that the totals below match Mod Organizer's results.

- Heljarchen Farm has 74 conflicts with the other mods.
- Immersive College of Winterhold has 49 conflicts with the other mods.
- Morskom Estate has 151 conflicts with the other mods.
- Vjarkell Castle has 2 conflicts with the other mods.
- Windstad Mine has 130 conflicts with the other mods.

Mod Organizer finds a total of 406 conflicts between these mods but most of these conflicts aren't meaningful.

When I removed the duplicates and filtered for actual conflicts (same file names, same file paths, different MD5 hashes), there was a dramatic difference in the number of conflicts.

- Heljarchen Farm has 6 actual conflicts with the other mods.
- Immersive College of Winterhold has 14 actual conflicts with the other mods.
- Morskom Estate has 16 actual conflicts with the other mods.
- Vjarkell Castle has 2 actual conflicts with the other mods.
- Windstad Mine has 10 actual conflicts with the other mods.

Only 48 (24 vs. 24) of the 406 conflicts reported by Mod Organizer are actual conflicts that could impact the player in the game.

Duplicates should be removed from conflict detection and the Conflicts tab.

I later wrote a script to test more mod combinations. The false positive rate averaged 90%. Only 10% of conflicts reported by MO are actual conflicts. Edited by fireundubh
Link to comment
Share on other sites

In response to post #54930713. #54932353, #54932553, #54932643, #54932878, #54934923, #54938668, #54945073 are all replies on the same post.


  Reveal hidden contents


Still has me a bit concerned given how NMM 0.63.1 nuked many users' games, including the majority of the SOT Team. Fortunately, I was able to navigate around the issue via a simple back-up of the plugins.txt file & Data folder (Skyrim). I'll likely do that again whenever it comes time to make the switch from NMM to Vortex. After the disastrous NMM 0.63.1 "update", I will never fully trust an Import option/radical update like that again.
Link to comment
Share on other sites

In response to post #54957218. #54958828, #54968988 are all replies on the same post.


  Reveal hidden contents


After the disaster that was NMM 0.63.1, I still don't trust it. Things are bound to get screwy/go wrong given how NMM is being replaced in its entirety & I strongly advise everyone to back-up their plug-in.txt file(s)/Data folders for any games being managed by NMM/MO prior to making the switch to Vortex. This is far more than a mere update & the 0.63.1 NMM "update" was literally playing Russian Roulette with one's entire installation of whatever games they had mods installed/being managed by NMM.
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...