Jump to content

Plugins getting disabled when cloning to a new profile


Deleted821989User

Recommended Posts

Description of behavior:

Hi, whenever I clone a profile, and then enable it, several plugins get disabled. Which plugins get disabled seems somewhat sporadic, but possibly influenced by how recently they were installed and/or whether I've launched the game since installing them. Mods have no issue, just plugins.


Manually re-enabling the plugins works fine. Once I re-enable the appropriate plugins, switching back and forth between profiles works as expected. It only happens with newly-cloned profiles, so it's not a big deal, as I only have to do it once per profile, but it's something I have to remember to do. It's probably just more disruptive to me as I tend to use profiles a lot as "stepping stones" while installing mods (i.e. install some mods, test, clone profile, switch to new cloned profile, repeat).


I can try to provide a video of the behavior if necessary, or logs if told what to provide.



Expected behavior:

When switching to a newly cloned profile, all mods and plugins remain in the state they were in in the profile that was cloned.


Misc. context:


I have touched a few settings, such as turning the "Deploy Mods when Enabled" setting on and off depending on the circumstance, but that hasn't seemed to change anything about the problematic behavior. Vortex is in "Per-User" mode on the "Stable" update branch. Using hardlink deployment.


As far as I know I don't have any unresolved conflicts, or load order issues. There are no error messages presented. I have no suppressed notifications. The last time I played Skyrim or used Nexus at all was many years ago, so I am going with the flow and using Vortex exclusively. It's had a learning curve, but has generally been great otherwise. The only mod I installed outside of Vortex was SKSE I believe.


Any idea what's going on here? I've seen many posts about plugins getting disabled on the forums, but none of them mention anything about profiles. It doesn't happen to me any other time. Perhaps I'm just not doing something right, or am misunderstanding the intended behavior.


Thanks for any insights.


Specs:

Vortex version: 1.3.13

I'm using the custom install location version. I have corrected the staging/downloads locations in the settings. Everything is on the same (separate) SSD, which is not particularly full.


Game being modded: Skyrim VR (1.4.15.0)


Number of mods: Currently at 135 mods, with 113 plugins. This has been happening since I noticed it back at around 20 or so mods.


Environment: Windows 10 x64 2004 19041.572

Link to comment
Share on other sites

I see. If I'm not mistaken Per-User is the default setting. at least I don't remember touching it. But I have no reason to use it as this isn't a shared machine, so I'll try changing it and see if that solves the issue.

 

Thanks.

 

P.S. Generally being a power user and working in IT, I've been on the receiving end of bad support requests for 12 odd years, so I've learned /shrug

Link to comment
Share on other sites

Well that was a big mistake. I didn't realize that Vortex would basically wipe itself when switching modes. At first I thought maybe I could just copy over the content into the new staging and downloads folders, but it's certainly not that simple. Thankfully I backed up the important stuff before letting Vortex do anything crazy. In the end I switched back to Per-User mode.

 

I didn't stay in Shared mode long enough to see if it fixed the problem, mainly because I initially freaked out when I thought I might have lost my last week of modding work. Also I didn't have my profiles to switch between anyway, and I wasn't about to rebuild everything just to try.

 

I would consider trying it again if someone can tell me how I can transfer all my mods, plugins, profiles, tools, etc. over to shared mode without reinstalling and reconfiguring it all. Otherwise, I'll just deal with the cloned profile issue. It's not worth redoing everything to fix :/

Link to comment
Share on other sites

So, I haven't ventured to try switching back to Shared mode, but one thing I did try which has worked (only tested once so far), is exiting and restarting Vortex before cloning the profile. Once I did that, cloned the profile, and enabled it, I didn't see any plugins disabled which were not supposed to be disabled.

 

My initial suspicion is that whatever data source the cloning operation is pulling from to determine the state of the plugins is not guaranteed to be up to date until Vortex is restarted. Like perhaps it's not getting written to disk or something like that. It might be possible that one of the advanced buttons on the mods or plugin pages would also work to update whatever cache is being read, such as "Sort Now", "Reset masterlist", "Purge mods", "Reset to masterlist", etc. However as I'm not wholly familiar with what these functions do, I don't feel inclined to test that, especially when a simple restart seems to prevent the issue.

Link to comment
Share on other sites

Well, I'm glad you keep pushing forth with this, I'm really hazy when it comes to the SHARED vs PER-USER thing myself, I do know that everything gets stored in a different location if you have it set to SHARED

For instance, on my computer (set to SHARED), all of my Vortex stuff is in C:\ProgramData\Vortex rather than the appdata\roaming\Vortex folder

So, I assume with PER-USER you'd get different C:\users\NAME PER-USER\appdata\roaming\Vortex\ folder for each person, whereas you only get ONE C:\ProgramData\Vortex folder with the settings for all users

Which I believe is why your Mods "Disappeared", because the info is still there if you switch back to PER-USER, because your switch to SHARED, switched over to C:\ProgramData\Vortex

Link to comment
Share on other sites

Well I made it more complicated in my case, since I use the custom install location version of Vortex. That means I have to manually specify the downloads and staging directories to be on the same drive (everything is on G: for me). This is presumably a limitation of the hardlink deployment method (since hardlinks cannot span drives). I also botched it when I thought I might be able to just copy content from the old locations used by the Per-User mode to the new locations used by the Shared mode. Vortex really didn't like that.

 

When I stop to think about it, it does make sense that nothing would carry over. Moving from a Per-User installation to a Shared installation should probably be no different than moving from one Per-User installation to a different Per-User installation (i.e. nothing would be shared).

 

It would be nice to see a feature that allows for a "Per-User profile" (I use profile in quotes to distinguish from the mechanism that Vortex already calls profiles) to be one-time copied to a different "Per-User profile". But I understand that that would probably not be a popular enough use-case to be worth implementing. But maybe there's already a way to export/import that I just haven't learned about yet.

Link to comment
Share on other sites

Well I made it more complicated in my case, since I use the custom install location version of Vortex. That means I have to manually specify the downloads and staging directories to be on the same drive (everything is on G: for me). This is presumably a limitation of the hardlink deployment method (since hardlinks cannot span drives). I also botched it when I thought I might be able to just copy content from the old locations used by the Per-User mode to the new locations used by the Shared mode. Vortex really didn't like that.

 

When I stop to think about it, it does make sense that nothing would carry over. Moving from a Per-User installation to a Shared installation should probably be no different than moving from one Per-User installation to a different Per-User installation (i.e. nothing would be shared).

 

It would be nice to see a feature that allows for a "Per-User profile" (I use profile in quotes to distinguish from the mechanism that Vortex already calls profiles) to be one-time copied to a different "Per-User profile". But I understand that that would probably not be a popular enough use-case to be worth implementing. But maybe there's already a way to export/import that I just haven't learned about yet.

 

 

No matter WHERE you install Vortex, there's always going to be a C:\users\YOURNAME\appdata\roaming\Vortex\ folder for someone who is using Per-User, and a C"\ProgramData\Vortex folder for someone who is using SHARED

 

 

By the way, I forgot to post this, this is the text box that pops up for the Shared/Per-User tool-tip

 

 

 

 

 

Shared-Per-User.jpg

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...