Shows empty Outfit/Body/Presets when run in Proton

[yhanruzai]

Description
I moved to Linux trying and was trying to mod Skyrim SE and it seemed normal until installing BodySlide. For some reason, users on this version suffer from a bug on trying to run it on Proton 9.0-4 (seems to happen on all versions, tested latest commit and still happens) which does not find any outfit/body or preset despite them being installed normally with no known workaround so far. Some users reported the same issue on some of the nexusmods forum posts.

How to reproduce

1. Install Mod Organizer 2 on Linux, running it with Proton (using this script
2. Add Bodyslide to programs list
3. Run it
4. Should be able to select data and build mods (expected behavior)
5. Instead it shows an empty Outfit/Body/Presets as shown below.
   

Running it on Arch Linux official Steam version, through which Skyrim SE was installed.

[ousnius]

@yhanruzai I don't have any experience with Proton and no way to test this.
The way BodySlide finds the files to show in the dropdown is the following:

std::string BodySlideApp::GetProjectPath() const {
	std::string res = Config["ProjectPath"];
	return res.empty() ? Config["AppDir"] : res;
}

wxDir::GetAllFiles(wxString::FromUTF8(GetProjectPath()) + "/SliderSets", &files, "*.osp");

Does it work if you set an explicit "project directory" in the settings of BodySlide instead of relying on where the app is installed?

[yhanruzai]

By setting the explict project directory i assume you mean just selecting the mods that contain bodyslide files on the advanced settings page right? In any case, that does not seem to result in any change (other than if that worked i'd be a major hassle having to do that for each cloth/body begin built). I don't have much experience with C++ either, but it seems that for some reason the app is not seeing any body config which is weird considering nothing is closed of or being run from a sandbox.

Sidenote: OutfitStudio seem to work just fine under it, so it is only affecting bodyslide in pretty much any proton version from Proton 9 onwards.

[ousnius]

By setting the explict project directory i assume you mean just selecting the mods that contain bodyslide files on the advanced settings page right? In any case, that does not seem to result in any change (other than if that worked i'd be a major hassle having to do that for each cloth/body begin built). I don't have much experience with C++ either, but it seems that for some reason the app is not seeing any body config which is weird considering nothing is closed of or being run from a sandbox.

Sidenote: OutfitStudio seem to work just fine under it, so it is only affecting bodyslide in pretty much any proton version from Proton 9 onwards.

No, when you open "Settings" in BodySlide, under "Advanced" there is a setting for project directory. Select the folder your BodySlide installation is in there.

[yhanruzai]

Tried doing just that... no success. It still doesn't show any information.
Sidenote: I'm running it through Mod Organizer 2 already.

[Bereim]

This might be a deeper problem, as I am having this issue with a native build I compiled.

[IcyTea31]

I have the same issue, but found a workaround. The code does correctly pick files up from /SliderSets etc., but it appears blank because there aren't files there by default. Something goes wrong when it should look those files up from your body and outfit mods. If you manually copy the files under each mod's /CalienteTools directory to BodySlide and OutfitStudio's directories, they will start working.