Weir Problem With AC Variable (Vector3)
Hello, currently using AC version 1.74.2, the problem im having is that i have a vector 3 variable declared on an object with the "Variables" component, that variable is being used to record the position of an object when saving, and loading the position from those values when loading, the problem is that when saving and loading that variable, it gets set to "0,0,0" but this shouldnt happen because nothing else affects that variable, after further inspection we noticed that it was only saving INT values not FLOATS, if we set the variable manually with only INT values, and save and load the game, the variable gets saved and loaded correctly, but if we use FLOATS it gets set to "0,0,0" after saving and loading, and the weird part is that this is happenning only for my local version of the project, 4 team members tested it and for them the logic works because the game is saving the FLOAT position values correctly in the vector 3 variable, for me it happens in 2 out of 3 computers, so i dont know what may be the problem, i alredy uninstalled unity and cloned the project repo from scratch, but it did not solve it, help!
Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Comments
How does the data appear in the Save-File Manager, and how does each computer's location/language differ from those that work vs those that don't?
I'm wondering if it's related to a (now solved) issue that was causing float data to be saved using the system's own culture. In recent AC versions, a Use Invariant culture for saving? option in the Settings Manager's "Save games" panel avoids this.
If you want to implement this in an older release, it essentially runs this code:
Does placing this at the top of the KickStarter script's Initialise function resolve it? If not, are you using save-threading?