Joel wrote: ↑Sat Oct 30, 2021 10:56 am
I've been having an experiment today and this is indeed possible, and will be added in the next update. In the meantime I'll private message over an update the update, which includes a Save Multiple and Load Multiple action.
Hey! Not sure if I'm doing it right but I tweaked your Load Multiple action by adding an additional value.GetValue().
So the main part looks like this:
this way it will not stop the whole FSM with an error if there is no such key in the file but will just use the current variable value instead. I believe it's much more convenient than assigning additional "Default Value" (as it was made in Load action). And definitely better than just getting an error that stops the FSM. What do you think, is it an acceptable solution to include it in official ES3?
Joel wrote: ↑Sat Oct 30, 2021 10:56 am
I've been having an experiment today and this is indeed possible, and will be added in the next update. In the meantime I'll private message over an update the update, which includes a Save Multiple and Load Multiple action.
Hey! Not sure if I'm doing it right but I tweaked your Load Multiple action by adding an additional value.GetValue().
So the main part looks like this:
this way it will not stop the whole FSM with an error if there is no such key in the file but will just use the current variable value instead. I believe it's much more convenient than assigning additional "Default Value" (as it was made in Load action). And definitely better than just getting an error that stops the FSM. What do you think, is it an acceptable solution to include it in official ES3?
Hi there,
There are very common situations where it is necessary for people to be alerted that the file does not exist (using the Error state) so that they can perform initialisation, and specifying a default value by default would prevent customers from being able to do this.
NoPants wrote: ↑Sat Dec 31, 2022 8:01 pm
Could I get ConcurrentDictionary added as a supported type?
Hi there,
ConcurrentDictionary is already supported as it implements IDictionary. However, be aware that it's not possible to serialize the concurrency level at runtime as C# provides no way to get the concurrency level of a constructed ConcurrentDictionary, so any loaded ConcurrentDictionaries will have the default concurrency level.
Ok weird. I'll try something else, but I'm getting this error.
NotSupportedException: Generic type "System.Collections.Concurrent.ConcurrentDictionary`2[Assets.Scripts.Enum.ResourceType,CodeStage.AntiCheat.ObscuredTypes.ObscuredDouble]" is not supported by Easy Save.
NoPants wrote: ↑Wed Jan 04, 2023 1:34 am
Ok weird. I'll try something else, but I'm getting this error.
NotSupportedException: Generic type "System.Collections.Concurrent.ConcurrentDictionary`2[Assets.Scripts.Enum.ResourceType,CodeStage.AntiCheat.ObscuredTypes.ObscuredDouble]" is not supported by Easy Save.
Hi there,
Is the CodeStage.AntiCheat.ObscuredTypes.ObscuredDouble a supportable type? I.e. do you get the same error with a ConcurrentDictionary<int,int>?
Sorry for the delay. Ya, I'm still getting the same error.
"NotSupportedException: Generic type "System.Collections.Concurrent.ConcurrentDictionary`2[System.Int32,System.Int32]" is not supported by Easy Save."
NoPants wrote: ↑Thu Jan 12, 2023 2:57 am
Sorry for the delay. Ya, I'm still getting the same error.
"NotSupportedException: Generic type "System.Collections.Concurrent.ConcurrentDictionary`2[System.Int32,System.Int32]" is not supported by Easy Save."
Hi there,
First, please ensure that you're using the latest version of Easy Save. If updating doesn't resolve the issue, please could you contact me via the form at moodkie.com/contact with a link to a new project with a simple scene which replicates your issue.