Absolute joke so the update deleted the custom controller setups that people had spent time making.Then so people could play the game people had to make new setups hoping the fix would come only to find out you were meant to not both playing the game until the fix come out .Why could it not be hot fixed that the custom setups were reset no matter if you had made new setups
@Ghost-72_uk wrote:Absolute joke so the update deleted the custom controller setups that people had spent time making.Then so people could play the game people had to make new setups hoping the fix would come only to find out you were meant to not both playing the game until the fix come out .Why could it not be hot fixed that the custom setups were reset no matter if you had made new setups
Because they are not cloud saved and were overwritten locally. This has already been asked and answered in this thread if you'd have read it.
It was not the intention of the developer to create this situation, but it does mean that people that update without a backup or fall back position are in this position. I'm not excusing the update and what it did, but blindly updating always carries a risk. The monolithic save file was a developer decision back in the day. It's failed repeatedly (lost or corrupted save scenario) and yet I think the main reason is for anti-tamper. Some part of the progress is saved in cloud (online services) but I feel this is more motivated by the monetisation angle than it is player convenience.
Retrospectively, the latest hotfix could only do what it did, update the game from the place where it did work properly provided it had not been launched with auto-updates enabled. I can now only speak from a position of understanding the Steam cloud save process (as that is my platform), in that it is very crude. It is a one way transfer, with local or cloud files having priority depending on timestamps (yes I'm aware of Steam updates that can inject / replace target code in binaries to reduce download sizes, but it essentially remains the same crude method to the end user). The only possible way of 'winding back' an update is to use the beta branch feature and make all updates beta. The issues with that are also manifold, game versioning for online play would desync, when would a patch be presumed to be final (you'd have to say at the release of the next patch), progress made in the branch would be lost if the game was reverted, yet it could interact badly with online services, etc. So, on balance I don't think it would help.
So that's your answer.
