New Collections disable plugins for previous Collections. Am I doing something wrong?

[showler]

I'm playing around with SSE Collections. I added a large one, and then added two "add-on" Collections for the big one. Each time I install a new Collection, all the existing plugins from the previous one(s) seem to get toggled to "disabled" and I need to Ctrl-A and re-enable them.

 

Have I missed a setting or misunderstood something along the way?

[jaydawg55]

What Collections are you referring to?

 

EDIT:

 

Or maybe it is more correct to say, "Which Collections are you referring to?"

 

Is it possible that the Add-ons are supposed to disable other mods in the previously installed base Collection? I can tell if you don't tell me which collections you are trying to work with.

Edited August 27, 2022 by jaydawg55

[showler]

Immersive and adult, I&a exploration add-on, I&a companion add-on.

[Krocx]

I have installed a few small collections and every time I start a new collection even if it has nothing connected to a previous one vortex auto disables every plugin outside the new collection. While it is a massive pain to have to enable every disabled plugin after I finish installing a new collection so I can test how the work in game before adding more mods.......it is still a small price to pay for the convenience of the shear amount of time it saves. Just for reference I installed Arthmoor and when I installed JS textures it disabled Arthmoor, then after testing I installed JK's interiors and vortex disabled both Arthmoor and JS. So out of 9 collections so far where a total of six mods have been shared between 142 plugins every new collection disabled every plugin.

[Pickysaurus]

I can confirm this is a bug. I've raised a ticket internally to address it.

[mac2636]

I can confirm this is a bug. I've raised a ticket internally to address it.

 

This has not been corrected as of yet correct? Only asking as a precaution before making some changes.

[Pickysaurus]

We've got a couple of internal builds in testing where it has been fixed. I'm not sure when it'll be part of the public release. Potentially the next update. We had to quickly update for the GOG Skyrim release so some of the bugfixes didn't make it into 1.6.13.

[mac2636]

We've got a couple of internal builds in testing where it has been fixed. I'm not sure when it'll be part of the public release. Potentially the next update. We had to quickly update for the GOG Skyrim release so some of the bugfixes didn't make it into 1.6.13.

Thanks so much for the update and the continued work. So much appreciated!!!