I'm sorry to hear that the problem still persists.
DoubleLoopAndy a écrit
Can this file safely be removed from version control altogether?
Basically yes, you can safely remove this file from version control and let every local user choose her own preferences. As it contains default values that are used upon import and options whether warnings are shown or hidden, it doesn't break anything if it's not in version control.
Nevertheless, we would like to fix this issue properly. We have created an issue ticket here:
https://github.com/EsotericSoftware/spine-runtimes/issues/1895
Unfortunately we could not yet reproduce this problem locally, we could not get the setting to reset to an empty string in the saved asset file.
Nevertheless, a commit has just been pushed to both 3.8 and 4.0-beta branches, which hopefully fixes the problem. Please let us know if the problem still persists after installing the latest unitypackages from here:
Spine Unity Download
Please also double-check if the PMATexturePreset.preset
file exists on the machines of your windows users (where it is saved as the empty string). It would also be interesting to know whether there are multiple SpineSettings.asset
files present on your user's machines when the preference property it is saved as the empty string.
Possible bug is if you use Path.Combine and then File.Exists.
I'm afraid I can't quite follow what exactly is problematic with this combination, could you please describe it in a bit more detail?