Khumak Posted April 24, 2018 Share Posted April 24, 2018 I'm not sure how I've managed to do this, but Vortex seems to think some of my files are hidden. I think this happened when I selected a bunch of them and told it to remove the files but not the archives. I was basically looking for a way to uninstall all of my mods as a batch instead of only disabling them. Now the only way it finds those files is if I install from a file using the file manager. If I copy it into Vortex's download directory it doesn't see it. Is there some way to completely reset Vortex? I moved all of my install files to a back up directory and then completely deleted both the download directory and the mod directory and also deleted all of my Skyrim SE profiles so Skyrim SE was no longer a managed game. Then I managed Skyrim SE again and it showed zero mods installed so I copied my mods back again but only about half of them show up. Very confused... Link to comment Share on other sites More sharing options...
Khumak Posted April 24, 2018 Author Share Posted April 24, 2018 Ok Vortext sees my files again now. I have no idea what changed. But now I'm getting errors when I try to install mods. I get a message that says failed to determine conflicts. There are no conflicts because this is the very first mod I installed... ENOENT: no such file or directory, scandir 'D:\Games\Vortex\skyrimse\mods\Unofficial Skyrim Special Edition Patch-266-4-1-3'Error at Object.res [as readdirAsync] (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\util\fs.js:45:23) at Object.walk (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\util\walk.js:9:15) at Promise.map (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar.unpacked\bundledPlugins\mod-dependency-manager\index.js:10332:34) at tryCatcher (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23) at MappingPromiseArray._promiseFulfilled (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\map.js:61:38) at MappingPromiseArray.PromiseArray._iterate (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise_array.js:114:31) at MappingPromiseArray.init (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise_array.js:78:10) at MappingPromiseArray._asyncInit (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\map.js:30:10) at Async._drainQueue (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:138:12) at Async._drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:143:10) at Async.drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:17:14) at <anonymous> Link to comment Share on other sites More sharing options...
Khumak Posted April 24, 2018 Author Share Posted April 24, 2018 I think there must have been some messed up hard links or some other remnants of my previous installation saved in Vortex somewhere. I just uninstalled all of my mods again, did purge mods, then deploy mods, and now I can install the unofficial patch without getting that conflict error above. Will see how the rest of my installation goes. I think maybe there needs to be some additional button that allows you to clear everything related to the game you're managing and reset it to whatever condition it would be in for a newly managed game in case something like this happens. Link to comment Share on other sites More sharing options...
Khumak Posted April 24, 2018 Author Share Posted April 24, 2018 Ok I thought my problem was cleared up but it's not. My mods do show up in my download directory and my mod directory within Vortex now, but I still get that conflict error mentioned above when I try installing certain mods. If I uninstall everything, move all of my mods out of my dowload directory, purge mods, deploy mods, and then go verify that my Skyrim SE Data folder only has vanilla files in it, the dashboard still says I have 15 active mods. Link to comment Share on other sites More sharing options...
Khumak Posted April 24, 2018 Author Share Posted April 24, 2018 Ok I think I finally found a way to fix my problem. I enabled profiles, created a new profile and deleted the default profile. The new profile showed up with zero mods in the dashboard and so far I haven't gotten any more errors when instaling mods to that profile. I think my default profile was irretrievably hosed. Link to comment Share on other sites More sharing options...
Tannin42 Posted April 25, 2018 Share Posted April 25, 2018 I'm not a big fan of the "dump everything, restart from scratch" approach to solving problems. If Vortex was somehow responsible for causing the problem, how are we going to figure out when and how things went wrong if it was solved by "deleted everything, started fresh"?It may solve your problem right now but it does nothing to improve Vortex and help avoid the problem in the future. That's why I prefer to investigate problems first.Like for example: When Vortex says "ENOENT: no such file or directory, scandir 'D:\Games\Vortex\skyrimse\mods\Unofficial Skyrim Special Edition Patch-266-4-1-3'", was it right that this directory didn't exist? Link to comment Share on other sites More sharing options...
Khumak Posted April 25, 2018 Author Share Posted April 25, 2018 I'm not a big fan of the "dump everything, restart from scratch" approach to solving problems. If Vortex was somehow responsible for causing the problem, how are we going to figure out when and how things went wrong if it was solved by "deleted everything, started fresh"?It may solve your problem right now but it does nothing to improve Vortex and help avoid the problem in the future. That's why I prefer to investigate problems first.Like for example: When Vortex says "ENOENT: no such file or directory, scandir 'D:\Games\Vortex\skyrimse\mods\Unofficial Skyrim Special Edition Patch-266-4-1-3'", was it right that this directory didn't exist? No, that directory did exist, but it didn't show up if you looked at the mod folder in Vortex. If you used the windows explorer to look at the directory outside of Vortex it was there though. I haven't run into any similar issues since then and I spent all day redoing my mods from scratch, including disabling and re-enabling a bunch of them and reinstalling some of them as I tweaked my patches and merged some of the mods. I did not try doing remove file but not archive again though. I did remove both the file and the archive for a bunch of things without issue. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.