BBigBBruhMMoment Posted September 16, 2020 Share Posted September 16, 2020 (edited) As the title says my Vortex launcher has been stuck in what seems to be a loop trying to install DUST 2.0. Every other stage of the instillation process works fine. I have attempted rebooting Vortex, deleting and reinstalling the mod, and even updated the launcher. At this point I'm considering letting it attempt to install for several hours. Edit: This error seems to be specific to the installation of DUST Survival Simulator v2.0 Edited September 16, 2020 by BBigBBruhMMoment Link to comment Share on other sites More sharing options...
rmm200 Posted September 17, 2020 Share Posted September 17, 2020 (edited) Be sure you read the comments on that mod. It seems problematic for many.Any install that takes more than 5 minutes is unlikely to ever finish.You might try unzipping the archive manually, just to verify your archive is good. Edited to add another thought: After you cancel Vortex, look at the Vortex log. It may have useful information:AppData/Roaming/Vortex/vortex.log Edited September 17, 2020 by rmm200 Link to comment Share on other sites More sharing options...
Pickysaurus Posted September 18, 2020 Share Posted September 18, 2020 Hmm, I can replicate this issue, so I raised it on GitHub: https://github.com/Nexus-Mods/Vortex/issues/7469 Link to comment Share on other sites More sharing options...
rmm200 Posted September 18, 2020 Share Posted September 18, 2020 Hmm, I can replicate this issue, so I raised it on GitHub: https://github.com/Nexus-Mods/Vortex/issues/7469 With this specific mod? Does manual unzip work? Link to comment Share on other sites More sharing options...
Pickysaurus Posted September 18, 2020 Share Posted September 18, 2020 The mod/file is noted in the bug report rmm200 :smile: What it looks like is that FOMOD installer is being activated but then failing because the mod archive isn't a FOMOD. Link to comment Share on other sites More sharing options...
rmm200 Posted September 18, 2020 Share Posted September 18, 2020 That would point to a packaging error on the mod's part...The user could bypass the install error by repackaging the mod without the fomod. Does require knowing what he is doing. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now