mtc44mag Posted June 10, 2019 Author Share Posted June 10, 2019 Note, if you only copies the downloads and not the Vortex settings in %appdata%\vortex to the new machine, Vortex will read all files in downloads and depending on how many and large the mod archives are this can take many minutes. Since disk will likely be maxed out you can't install any mods until process finished. A second process will contact Nexus for all mod archive, trying to find the correct mod on Nexus and if successful more information is added to Vortex. While Vortex is busy "talking" with Nexus, this can block Vortex from installing mods until finished. If on the other hand you copies the Vortex settings, Vortex don't need to re-create any of the information and you can immediately install mods. The new installation will be on an M.2 PCIe SSD so the time needed to parse will not be a major issue for me, and if I am reading that correctly, you're saying it will call out to the nexus to pull in the info and check for newer versions at the same time so having that occur would actually be preferable to me. Thank you for the information on this though. Link to comment Share on other sites More sharing options...
Rattledagger Posted June 10, 2019 Share Posted June 10, 2019 you're saying it will call out to the nexus to pull in the info and check for newer versions at the same time so having that occur would actually be preferable to me. Maybe I'm mis-remembering, but if not mistaken Vortex only checks for updates for installed mods... Still after Vortex has grabbed all available info on current mod-versions, checking for updates should AFAIK be very quickly done. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.