Application freeze when syncing with spreadsheet
8 years 6 months ago #1077
by Frank
Are you
Give I2L
5 stars!
Are you
Please lets us know how to improve it!
Replied by Frank on topic Application freeze when syncing with spreadsheet
Hi,
All the localization data is stored in the i2Language.prefab. To avoid losing the data it contains, export it into CSV or to a Google Spreadsheet. Then you will be fine to delete and install the new version.
Its a good idea to also make a copy of the I2 folder. If for some reason, you need to go back to the previous version, you should just copy the I2 folder back to the original location and everything will work normally.
No, the downloaded data will still be saved into PlayerPrefs. But its now using a custom format, not JSON. Parsing this format its far faster/memory efficient than dealing with all the JSON structure, so it loads faster.
Problem before, was that it was building the dictionary on Awake, then getting the data from the PlayerPrefs JSON, parsing it and creating the list term, then redoing the dictionary. And if after contacting google, there was a newer spreadsheet, then the process was repeated for the downloaded data.
Now, it only rebuilds the dictionary once (either from the original data or the PlayerPrefs data) and parsing the saved data its faster than parsing the JSON. So its quite a lot of performance gain.
Dynamic fonts are great, but they create a lot of lag, especially when switching to a language with different character's set or when you have lot of different font sizes.
Unity will be rebuilding the font's texture as it encounters more texts/font sizes, and that could make the texture to regenerate several times.
The ideal solution its to move out dynamic fonts altogether. Use Unity bitmap fonts, textMesh pro or anything similar. But that could be a problem for you if your deadline it tomorrow!
There are a few things I had used to decrease the lag caused by dynamic fonts.
For instance, you could create a script in your loading scene that for every font you use, calls Font.RequestCharactersInTexture with all the characters and sizes you are using. That will trigger only 1 texture rebuild instead of multiple ones as Unity finds more characters.
something like:
Just make a term in your source containing all used characters in each language:
UsedCharacters = "abcde.......
Similarly, you can add a hidden text (behind your loading screen sprites) containing all the used characters. So that you don't have to do the script. That will trigger rebuilding the font texture only once as all the text its included in a single object.
Nonetheless, the approach that will give you a lag free solution its to move into bitmap fonts.
Hope that helps,
Frank
All the localization data is stored in the i2Language.prefab. To avoid losing the data it contains, export it into CSV or to a Google Spreadsheet. Then you will be fine to delete and install the new version.
Its a good idea to also make a copy of the I2 folder. If for some reason, you need to go back to the previous version, you should just copy the I2 folder back to the original location and everything will work normally.
3- If a new version of the spreadsheet is found, then the resulting JSON is saved into PlayerPrefs and used from that point on, (even when disconnected as that's supposed to be the most up to date data), however, the dictionary was rebuilt twice if there was a JSON in the PlayerPrefs.
Does this mean in 2.6 that any previous changes will not be remembered if booting without internet? This is quite an important feature as the password to load the app is controlled from the spreadsheet.
No, the downloaded data will still be saved into PlayerPrefs. But its now using a custom format, not JSON. Parsing this format its far faster/memory efficient than dealing with all the JSON structure, so it loads faster.
Problem before, was that it was building the dictionary on Awake, then getting the data from the PlayerPrefs JSON, parsing it and creating the list term, then redoing the dictionary. And if after contacting google, there was a newer spreadsheet, then the process was repeated for the downloaded data.
Now, it only rebuilds the dictionary once (either from the original data or the PlayerPrefs data) and parsing the saved data its faster than parsing the JSON. So its quite a lot of performance gain.
Regarding the Dynamic text, I originally misunderstood what you meant by this term, but from what you have since said - yes it seems I am using it after all, all my translated text is - 'Target - UGUI Text', and as soon as it hits a scene with one of these in, it freezes to sync.
Dynamic fonts are great, but they create a lot of lag, especially when switching to a language with different character's set or when you have lot of different font sizes.
Unity will be rebuilding the font's texture as it encounters more texts/font sizes, and that could make the texture to regenerate several times.
The ideal solution its to move out dynamic fonts altogether. Use Unity bitmap fonts, textMesh pro or anything similar. But that could be a problem for you if your deadline it tomorrow!
There are a few things I had used to decrease the lag caused by dynamic fonts.
For instance, you could create a script in your loading scene that for every font you use, calls Font.RequestCharactersInTexture with all the characters and sizes you are using. That will trigger only 1 texture rebuild instead of multiple ones as Unity finds more characters.
something like:
public void Awake()
{
var Characters = ScriptLocalization.Get("UsedCharacters");
Font.RequestCharactersInTexture(Characters, 14); // one for every font size
Font.RequestCharactersInTexture(Characters, 32);
//etc
}Just make a term in your source containing all used characters in each language:
UsedCharacters = "abcde.......
Similarly, you can add a hidden text (behind your loading screen sprites) containing all the used characters. So that you don't have to do the script. That will trigger rebuilding the font texture only once as all the text its included in a single object.
Nonetheless, the approach that will give you a lag free solution its to move into bitmap fonts.
Hope that helps,
Frank
Are you
Give I2L
5 stars!
Are you
Please lets us know how to improve it!
To get the betas as soon as they are ready,
check this out
Please Log in or Create an account to join the conversation.
8 years 6 months ago #1081
by Frank
Hi,
Its great that its working now!!
My bet about the builds not picking the PlayerPrefs correctly, its that the Key value remained the same, but the content saved in the PlayerPrefs changed (its not a JSON any longer).
So, maybe your devices had the previous downloaded data and they were unable to extract it correctly when only reading from the playerPrefs (offline) but was downloading and extracting correctly when connected. If at some later point, you changed the spreadsheet content, then the editor imported the new data and incremented the version number. So the PlayerPrefs was overridden, and the game was able to understand its content.
But again, Its great your project is working now!!
BTW, When you release your game, feel free to make a post in this forum about it, it could help with visibility and I will love to check it out!!!
Thanks,
Frank
Are you Give I2L
5 stars!
Are you Please lets us know how to improve it!
Replied by Frank on topic Application freeze when syncing with spreadsheet
Ok now the player prefs is working fine and correctly recovering the last change if I am offline. Not sure why it wasn't before, every build I made had the problem, but the last 2 have been fine
Hi,
Its great that its working now!!
My bet about the builds not picking the PlayerPrefs correctly, its that the Key value remained the same, but the content saved in the PlayerPrefs changed (its not a JSON any longer).
So, maybe your devices had the previous downloaded data and they were unable to extract it correctly when only reading from the playerPrefs (offline) but was downloading and extracting correctly when connected. If at some later point, you changed the spreadsheet content, then the editor imported the new data and incremented the version number. So the PlayerPrefs was overridden, and the game was able to understand its content.
But again, Its great your project is working now!!
BTW, When you release your game, feel free to make a post in this forum about it, it could help with visibility and I will love to check it out!!!
Thanks,
Frank
Are you
Give I2L
5 stars!
Are you
Please lets us know how to improve it!
To get the betas as soon as they are ready,
check this out
Please Log in or Create an account to join the conversation.
8 years 5 months ago #1089
by jimmyt3d
Replied by jimmyt3d on topic Application freeze when syncing with spreadsheet
Hi Frank,
Yes all is working well, it does seem to occasionally not remember the updated data when offline, but works a high percentage of the time which is good.
Unfortunately the application isn't for release to the public, it is for my client's internal company use only. However they are currently working on a promotional video for it which will be released online and a 'public' version may be available too, when that happens I'll definitely stick a link on here so you can check it out!
I have another project in the pipeline, which will definitely be made public when finished and will definitely make use of your plugin
Thanks again for all your help, your customer service has been outstanding!
Yes all is working well, it does seem to occasionally not remember the updated data when offline, but works a high percentage of the time which is good.
Unfortunately the application isn't for release to the public, it is for my client's internal company use only. However they are currently working on a promotional video for it which will be released online and a 'public' version may be available too, when that happens I'll definitely stick a link on here so you can check it out!
I have another project in the pipeline, which will definitely be made public when finished and will definitely make use of your plugin
Thanks again for all your help, your customer service has been outstanding!
Please Log in or Create an account to join the conversation.
Time to create page: 0.141 seconds