lister1911 Posted February 4, 2019 Share Posted February 4, 2019 I've been using Vortex for a while now with Fallout 4 and overall have been very pleased with this mod manager. Today I updated to the 0.17.1 Testing version while likewise deciding to manage Fallout 3 and SkyrimSE. It probably wasn't wise to update the version immediately before doing so, but that's what my dumb ass did. I'm on a Windows 10, 64-bit machine, 64GB RAM, DDR4, NVidia 1070 SLI, games are on a separate SSD, MSATA1 Samsung SM961, 512GB. And to be clear, my Steam install, games, mods, everything associated are on the same SSD, the D: drive. The only aspect that's on C: is the default AppData\Roaming\Vortex\{game}\masterlist folder and profiles folder and userlist, though until I can get Vortex to accept the new file path to my D: drive, it wants to put mods in that same C: path (which is why this isn't working and I have no deployment method available). Anyway, when I added each game, I immediately received the "Mods can't be deployed" notification. That was expected as I needed to setup the path for the Mod Staging Folder. However, once I add the correct path, which is the same as I use for Fallout 4 (other than the final folder name, obviously), Vortex gives me the "Moving" popup window and then hangs up. At that point, Vortex is nonresponse and the only way to close it is via the Task Manager. And after I have to kill Vortex that way, the next time I try to launch I usually get an "Access denied" message because Vortex is trying to access the user list but doesn't have permission. I don't think that is significant and is probably the result of the Task Manager shutdown, but I thought I'd mention it just in case. I have the same issue whether trying to manage FO3 or SkyrimSE. These are my paths for the Download tab and Mod tab: Downloads D:\Game Tools\Vortex\Downloads Mods D:\Game Tools\Vortex\Mod Staging\Fallout4 D:\Game Tools\Vortex\Mod Staging\SkyrimSE D:\Game Tools\Vortex\Mod Staging\Fallout3 Again, Fallout 4 works just fine but these new additions don't. I've tried using the FIX box, following the prompts that are part of the "Mods can't be deployed" notification, but it makes no difference how I try to enter the file path for the mod staging folder, nothing works. I also tried Vortex's suggested path, D:\Vortex Mods\{game}, and that didn't work either. It could be that I'm missing something obvious, or maybe this is a 0.17.1 bug, but I'm at a loss as to what to try next. I've attached a screen shot that shows the file paths and errors, in case my description wasn't clear. Any help is most appreciated! Link to comment Share on other sites More sharing options...
AugustaCalidia Posted February 4, 2019 Share Posted February 4, 2019 Thank you for providing some useful details. However, not meaning to be Captain Obvious, I have to ask: are your mod staging folders on the same drive as your games? (Or have I simply overlooked your answer to that question?) Also, in the Windows "Access denied" menu, what option did you select, and what was the result? Link to comment Share on other sites More sharing options...
lister1911 Posted February 4, 2019 Author Share Posted February 4, 2019 Thank you for providing some useful details. However, not meaning to be Captain Obvious, I have to ask: are your mod staging folders on the same drive as your games? (Or have I simply overlooked your answer to that question?) Also, in the Windows "Access denied" menu, what option did you select, and what was the result? Steam is also on my D: drive so yes, games and mods are all on the same SSD. I mentioned that my games were on their own SSD, but I wasn't specific to say that the mods were likewise on that drive, so good question. I'll edit my original post to make that more clear. As for the "Access Denied" popup, I typically "give permission" and it seems to work fine, but now if I get that error (it doesn't happen every time), I simply close Vortex again, and then re-open. I didn't want to take a chance that something might persist from that error and cause lingering issues. Regardless, I can't get Vortex to accept the Mod Staging file path no matter what I do. I thought it might have something to do with my original install, in that when I first downloaded and setup Vortex, there were 3 file paths requiring setup under the Mods tab, where now there is only one in this Vortex version (if you watch Gopher's video on Vortex installation, you'll see what I'm referring to). Other than that, I have no idea why FO4 works great, but no other games want to cooperate! Thanks for trying to help! Link to comment Share on other sites More sharing options...
BigBizkit Posted February 5, 2019 Share Posted February 5, 2019 How many mods were you trying to move and what made you think the "moving window" hung up? How long, approximately, did it take until you decided to forcibly close Vortex? Link to comment Share on other sites More sharing options...
Deleted8461535User Posted February 5, 2019 Share Posted February 5, 2019 Sorry if it it looks like I would try to steal this thread, but I've got the same issue as well. No mods, using the testing update, fresh Vortex on C drive, can't move the empty staging folders from C to D. Games are on D too. sat and looked at the "Moving...(And the wheel kept spinning)" window for around 15 minutes till I chose to shut it down. Fallout 4 and Skyrimse Link to comment Share on other sites More sharing options...
Silberwolf325 Posted February 5, 2019 Share Posted February 5, 2019 I had the same problem.I solved that by creating an empty text file in the directory, then I was able to change the directory in Vortex.the problem seems when the directory is empty Link to comment Share on other sites More sharing options...
AugustaCalidia Posted February 5, 2019 Share Posted February 5, 2019 I had the same problem.I solved that by creating an empty text file in the directory, then I was able to change the directory in Vortex.the problem seems when the directory is emptyThank you for this very helpful piece of information. Could you please spell out in more detail exactly what you did? Link to comment Share on other sites More sharing options...
lister1911 Posted February 6, 2019 Author Share Posted February 6, 2019 How many mods were you trying to move and what made you think the "moving window" hung up? How long, approximately, did it take until you decided to forcibly close Vortex? Hey BigBizkit, Thanks for stopping by! I wasn't trying to move any mods. I was simply trying to setup a new game (FO4 works great) by correctly defining the path for Mod Staging. Once I set that to D:\Game Tools\Vortex\Mod Staging\SkyrimSE, I get the "Moving" popup box and that's it. Vortex hangs and it just sits there with no increase to the progress bar. Silberwolf325 mentions creating a blank text file and placing it in a "directory" but I don't know if that means the default Mod Staging path or the new location, but I'll try both to see if that works and report back. Link to comment Share on other sites More sharing options...
lister1911 Posted February 6, 2019 Author Share Posted February 6, 2019 Ok, @Silberwolf325 was absolutely correct. The trick is to put a blank/empty text file (I used Notepad++ to generate a .txt file) in the default Vortex location for Mod Staging, which for me was C:\Users\name\AppData\Roaming\Vortex\skyrimse\mods. Once I put the blank text file there, then typed in the new path that I wanted to use for Mod Staging, again in my case it's D:\Game Tools\Vortex\Mod Staging\SkyrimSE, then hit apply, Vortex accepted the new path and switched the Deployment Method to Hardlink just like it should. This is an obvious bug/flaw with Vortex that should be fixed if possible. Thanks to all! Link to comment Share on other sites More sharing options...
BigBizkit Posted February 6, 2019 Share Posted February 6, 2019 Hey lister, Glad this solution worked for you. Our devs have already fixed this issue for the next/upcoming release. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.