Syncing the serialization to a TextAsset could be possible as an option and it should work. I can take a look at adding this as an option to reference an external TextAsset wherein the serialization string will be stored (in prety json of course). The way I foresee it, it will basically write to that file on every graph serialization callback. Due to backwards compatibility though (and probably for extra safety as well), the json string will also be serialized in the graph object as it does right now, so this might create some redundancy. Of course, this way, there will also be two files instead of one (as far as asset graphs go at least), but only the actual graph asset will be critical and the other (the Text Asset) will only exist as an extra and no problem will be issued even if that is deleted.
Let me know what you think.
Thanks!
Join us on Discord: https://discord.gg/97q2Rjh
Login
Register
By registering on this website you agree to our Privacy Policy.