|
Hello, I've written a custom inspector for GameObjects that can serialize/restore data changed at runtime (I can save the values I've changed at runtime, so they don't revert after playmode is stopped). However, most Unity types can't be serialized using the code from System.Runtime.Serialization. For example, I'd like to serialize Vector3 etc. (seems simple enough.) Does anyone know of a work-around? Right now I can only operate on basic types; bool,string,float,int etc.
(comments are locked)
|
|
We use ISerializationSurrogate to serialize Unity objects and scripts. http://msdn.microsoft.com/en-us/library/system.runtime.serialization.iserializationsurrogate.aspx Could you be a little more specific?
Apr 12 '12 at 05:22 PM
chuckrussell
yes, I would like to know more about this too!
Aug 19 '12 at 01:17 AM
numberkruncher
(comments are locked)
|
|
This is an example of usage. http://msdn.microsoft.com/en-us/library/system.runtime.serialization.surrogateselector.aspx You just have to write a surrogate for every Unity type that you want to serialize. GameObject, Transform, etc. Our implementation for a GameObject surrogate sucked. Need to rethink that one. :) Hope this helps How are you registering this with the Unity serializer? The serialization mechanism (including a surrogate selector) are implemented privately within the Unity library.
Aug 21 '12 at 12:21 PM
numberkruncher
(comments are locked)
|
Well, there's a surprising amount of abstracted information that you can store just with primitives! If your classes derive from Unity's 'Object' class, they will hook in nicely to Unity's inbuilt serialization, but that isn't really good enough if you want to use it for player-made levels and other such custom content. I have a generic Object Loader script which I've been using to pass level setup files between my level designers- but I'm not actually sure if it'd be good for anything more than primitives and classes which only contain primitives.