Jump to content

z9r

Premium Member
  • Posts

    2
  • Joined

  • Last visited

Nexus Mods Profile

About z9r

Profile Fields

  • Discord ID
    z9r.
  • Country
    Canada

z9r's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. When you're installing any collection with premium, on the install side of things, there are constant stalls. Doesn't matter the size of the collection. As an example, on the test version of my team's collection, which is ~500 megabytes: https://www.youtube.com/watch?v=DvsEh7MSsoc The install process with premium takes 17 minutes. If you close Vortex and restart it every time it pauses on a mod this is what happens: https://www.youtube.com/watch?v=vYi-gpdp7uA The install process takes ~6 minutes. This is a considerable difference and makes me think there's an issue on the Vortex side of things that could improve. Here's the same with the closing and opening parts cut out for real install time in Vortex: https://www.youtube.com/watch?v=MLxhamEJu3E Approximately 4 minutes. We're talking about 4 times less time to finish. Is this done purposefully or an issue in Vortex, and if it is an issue... can it be fixed? It seems to be a delay on the install side of things rather than downloading. (Just as a fun comparison, it takes 30 seconds to download with premium on wabbajack: https://www.youtube.com/watch?v=M5OQW5kSjXQ)
  2. The correct way to upgrade a collection from an older revision to the newest is to go to the Collections section, mouse over the collection image, and click upgrade. The issue that several users of my collections have run into is that they will intuit that they should just click add to vortex when they go to the collection page since it is a new revision. When they then go in Vortex and have it install, if they don't change anything, it installs to their current profile the new revision of the collection right alongside the already existing one, which breaks the collection as it loads multiple versions of the same mod. Demonstration of how this works folllows: Collection Same Profile New Revision Test I can't think of a situation where a user of a collection would want to install a new revision of a current collection they have to the same profile as the already existing collection. If this functionality was stripped or changed, it would prevent a lot of issues for collection users. Hope this helps!
×
×
  • Create New...