Right now, MPS checks if the provided pose is a custom pose or a game pose by checking if the pose filename begins with the directory where custom pose files are stored.
The issue with this method of checking is that custom poses use absolute paths. If the game were moved to another location, the base directory would not match despite the file retaining the same folder structure within the 'Custom Poses' directory. This results in MPS assuming the provided pose filename is a game pose, tries to load it as such and throws an error.
Checking that the pose is custom can be fixed by simply checking the PoseInfo's CustomPose member.
Getting the true path of the pose file would probably require a bit of cutting and concatenation of paths.
Right now, MPS checks if the provided pose is a custom pose or a game pose by checking if the pose filename begins with the directory where custom pose files are stored.
The issue with this method of checking is that custom poses use absolute paths. If the game were moved to another location, the base directory would not match despite the file retaining the same folder structure within the 'Custom Poses' directory. This results in MPS assuming the provided pose filename is a game pose, tries to load it as such and throws an error.
Checking that the pose is custom can be fixed by simply checking the `PoseInfo`'s `CustomPose` member.
Getting the true path of the pose file would probably require a bit of cutting and concatenation of paths.
Right now, MPS checks if the provided pose is a custom pose or a game pose by checking if the pose filename begins with the directory where custom pose files are stored.
The issue with this method of checking is that custom poses use absolute paths. If the game were moved to another location, the base directory would not match despite the file retaining the same folder structure within the 'Custom Poses' directory. This results in MPS assuming the provided pose filename is a game pose, tries to load it as such and throws an error.
Checking that the pose is custom can be fixed by simply checking the
PoseInfo'sCustomPosemember.Getting the true path of the pose file would probably require a bit of cutting and concatenation of paths.