cydonianknight21

The staging folder is set to C:\ProgramData\Vortex. This is to avoid the unique directory that comes with having the staging folder under your username. Vortex has a setting which lets you set a staging folder at this location (the setting is called shared mode) so that you can share your vortex instance across different windows profiles on the same machine, but if you set up your vortex install a certain way on a secondary drive you can take advantage of that setting to move it all rather painlessly to another machine. As it stands, it worked in my test instance but when I first opened vortex on the second machine it built a new (unnecessary) staging folder under the user profile. When I set it back to shared mode and rebooted the program, it found everything as intended and was like opening exactly the same vortex as on the first pc. I could let it create that extra instance of a staging folder and just write an extra step into the procedure (open vortex, change to shared mode, reboot) but it leaves those files there untouched which is a bit messy so I'd rather be clean if I'm sharing this method with people. Thats all

I just want to know how to boot the program into shared mode without having to open it and change the settings the first time

Thanks. Ive done it already, transferred my entire vortex install with modlist exactly as I had it from my gaming pc to my laptop, as a test. I still need to impliment the uninstall key being written into the registry but I know how to do that. The thing is, to do this you need vortex to be in shared mode so that the directory doesnt include your unique windows profile username. I could write up how I did it and let you guys just deal with having the extra files from vortex's default profile mode if all else fails. Its pretty terrifying when you are setting it up though, theres several moments during the process where it seems like youve lost your modlist entirely. Until youve successfully pointed vortex to the files. But at least this method doesnt involve vortex freaking out and losing the metadata on the mods, or saying the mods were changed outside of vortex. When you're finished with my method and you open vortex it looks exactly the same as it did on the old pc. Enabled/disabled and mod rules included.

Hi all, I've been working on a little project to make vortex portable. I plan to share it with everyone when its done. I've got it mostly done but I'd like to elimate a step. Is there a way I can force vortex to boot in shared mode (creating the data in c:\ProgramData\Vortex instead of under the windows user profile) without opening the program, changing the setting under vortex settings, and then rebooting the program? I am trying to avoid vortex automatically creating a redundant set of data files at c:\users\[username]\AppData. The way the portable convert is implimented right now is functional but those files are unnecessary bloat that would never be used by the portable version. If i can get this done and write it up for you guys, this will also make transferring your existing modlist to a new computer a lot less painless. The current suggested method is to start the list from scratch but I have discovered it doesn't have to be this way. Thanks for your help

I tried to download a mod from nexus while vortex wasn't open without realising, and when vortex opened something went wrong. According to the vortex log file I'm looking at, it changed the staging folder and moved logging all to C:\ProgramData\Vortex AV didn't do anything and I don't have any kind of cleaning bloatware on my pc. It wasn't a deletion of the directory at all. The log files I have show when it was working and exactly when it reset, and after it had reset. All in one log. Shortly after that, the log moves itself to the above folder and starts a new file there. There is also about 3 other log files in the appdata folder documenting the last week or so. Those wouldn't be there if the directory was deleted. I copied the appdata folder to desktop before restoring it so I could investigate it further but these log files prove that it wasn't a deletion. Theres a bunch of other files in there like preferences that had last modified dates well before 17/06 Without posting my whole load order and all the other stuff heres the end of the last time it worked and the beginning of today from the single file

Well thankfully you've saved me for now. I was able to go into the properties of that folder and use a system restore point from two days ago, which has fixed my vortex. Major, heart wrenching crisis averted. That was literally hours and hours of work I thought I'd lost. However, and perhaps more seriously, I still didn't delete or change anything to cause this in the first place. I didn't even know that folder was there, I thought the point of installing vortex on Q: drive was that it would be self contained to that drive. I haven't been into appdata folder for a long long time. This begs the question what could possibly cause such an issue to happen, if not me manually moving something? My next guess would be an issue with a windows update however the computer has remained on the entire time. I'm worried it could happen again and something could go wrong with my restore points and I really will lose everything

Sorry for my somewhat upset first post. Here is how everything has happened so far: I've got vortex installed in a custom directory (with another custom directory beside for my mod staging which is safe but no longer linked to the app)The PC has not been turned off or changed in days, the last time I opened vortex was two days ago (17/06) and everything was fine at the timeI didn't touch anything since vortex was last open and workingBuilding the stable load order for Fallout 4 has been an ongoing project I have been working on for a few weeks, enjoying vortex without any issues. The last thing I did was install a mod, test it, close the game, close vortex and go to bed. Today I've gone to open vortex and as you've said it seems in-app like the appdata folder has been deleted. For reference everything is on a custom drive so my file structures are as follows: (Q:)Bethesda\SteamGameData\steamapps\common\fallout4 (game data) (Q:)Bethesda\Vortex (this is the appdata folder) (Q:)Bethesda\VortexModStaging Looking at my custom appdata folder, windows says it was last modified 11/06 and it still includes the vortex and uninstaller exe, a bunch of dlls and some other program files, and three folders: locales, resources, swiftshader Now if we go to C:\ProgramData theres a brand new Vortex folder with dictionaries, downloads, fallout4, plugins, state.v2, temp folders. Logs, and installer.exe I must reiterate that I did not delete anything or touch the PC between when it was working and when I opened it to this. I signed back in to nexus through vortex upon opening and seeing that it wasn't signed in, saw that all my data was still missing. I set it to manage fallout 4 and saw that all my data was still missing. I tried to set the staging folder back and of course it gave me the error of needs to be empty folder, so I stopped messing with it and came here. UPDATE: In ProgramData\vortex\fallout4\profiles\skTRlO0Nj sits loadorder.txt and plugins.txt which are correct for what I had installed so far. I'm wondering if its a matter of moving files to directories to get everything hooked up again, but I would need further advise on what to move where.

I've just opened vortex and it's like opening it for the first time. I wasn't signed in to nexus, all my mods and game data are gone, and the settings are reset to standard. I've made sure my mods are in a seperate folder to Vortex data so they haven't been deleted in windows however I was in the middle of building a stable load order for Fallout 4. I can't link it back together. Restoring from backup is worthless as the only backup showing is since the data loss. If i try to set it up again it tells me that the mod staging folder has to be empty, which it is not because it has the data FROM VORTEX in it. Have I really lost weeks worth of work? what caused this? another update? please help. please. I've spent so long working on this. Please.