In Skyrim Vortex, the wrong body reappears with body slide in the past

[kloriss]

I was surprised that the body that I had ruined by touching the Skyrim body slide by mistake in the past floated again.

Other people's opinions say that there is a path that is stored in the vortex.

Do you guys know??

I'm trying to find that folder and delete it.

I reinstalled windows on the ssd, installed a new vortex, and installed a new mod, but I was surprised that the body came out before.

This is the body before installing windows.

[kloriss]

Mode Organizer deletes the app and re-installs it, and all the mode memory disappears, but Vortex remembers all the previous modes even if you reinstall the app.

So, in case you remember even the smallest details of the mod, I posted a question.

[showler]

The files Bodyslide creates are in the games data directory, not the Vortex staging directory, so Vortex doesn't manage them. You need to manually delete them yourself.

[rmm200]

FNIS has a cooperative arrangement with Vortex, and it's output is stored as a mod. You will have one unique FNIS Data mod for each profile. This is good.

 

Bodyslide runs as an independent application outside of Vortex control. This is not so good. As near as I can tell, you should really re-run Bodyslide every time you change profiles.

Otherwise the sliders and outfits you use for one profile will bleed over into other profiles.

 

SSEEdit likewise runs as an independent application that can modify mods under Vortex control. Vortex should catch these and offer you the confusing choice of latest or revert.

 

As always, I am open to correction. This is just what I have observed as a user.

Edited March 27, 2023 by rmm200

[showler]

It's fairly easy to tell Bodyslide to write to the deployment folder and have Vortex recognize it as a mod. Basically, manually doing what they automated for MO2.

[rmm200]

Expand on that a bit please. I don't see how anything writing to the mod staging folder (deployment folder) other than Vortex will ever turn out well.

I think Vortex maintains a catalog of what is in the mod staging folder.

Bodyslide would have to write it's output files to a unique folder within the mod staging folder and then trigger a Deploy. How?

Edited March 27, 2023 by rmm200

[showler]

It's been a while since I've done this.

 

If you make a folder in the deployment folder called something like "Bodyslide Output Profile 1" and have Bodyslide write the meshes it creates to that folder (making sure you have the proper folder structure..you might need to make some subfolders as well) then the next time you have Vortex open it will have a new, "never enabled" mod called "Bodyslide Output Profile 1" listed in the mods tab with a type "user-generated". I think it may come up with the "external files changes have been detected" dialogue and you just have to accept the new files. Then you can just activate the mod. You can even do the same conflict resolution as with any other mod.

 

You should be able to make a folder for every profile you have and simply have that mod be activated with the profile.