You can make a 'partial' workaround, following that blog-post, but due to OTHER problems in Unity Serialization (which the blog post ignores completely!), the workaround fails. I am full of hate for the current implementation, but not the people: I sympathize with this problem (been there, experienced that on big projects myself :( ). REALLY REALLY read the subsection “No support for null for custom classes”: this is some crazy, broken, crash-creating “default behaviour” built-in to Unity, due to bugs in the Serialization systemĪLSO IMPORTANT: Unity Serialization is broken they know this they have tried to fix it it is too difficult given how much of Unity relies upon current behaviour. Guys - how hard is it to check that your link works before publishing the doc? In fact, the docs are actively wrong, and have a broken link to a non-existent class (“INotifyOnSerialization”). But only partly! Some of the best bits are missing from the docs still. Wrote a blog post that (after some encouragement) got partly copy/pasted into the official Unity 4.5.x docs. Want some more? How about writing your own Garbage Collector, just to workaround the bugs in Unity Serialization? Think I’m kidding? Read this: This leads to absurd, hacky workarounds such as: Other bugs: this sometimes loses data if you quit Unity editor. Why? Because Unity converted all references to the object into “pointers” instead of “actual object-data”. BUT IT’S A LIE!Īny Objects in an array, or a List (beware! in some places, Unity Serialization “works” with one of these, but not the other). Problem solved (according to Unity docs). why? Because Unity’s horribly broken Serialization reads “System.Serializable” incorrectly, and embeds copies of the data instead of serializing the data. Or when you reload source (because you saved ANY script ANYWHERE). references to things of the same class) then those ARE lost when you close Unity and re-open. HOWEVER: if it contains other Class/Struct instances (e.g. (ever wondered why duplicating a Terrain in Unity corrupts your original one? Welcome to the world of Unity 'doesn't actually work' Serialization.) It's not about 'saving the game', it's about 'Unity's GUI is internally implemented using this stuff - and it CORRUPTS your game-data!'. because Unity does invisible serialization HUNDREDS OF TIMES A SECOND, every time you click on things, move the mouse, all sorts of stuff. Tl dr: According to Unity staff, these major internal bugs have been de-prioritized for the next couple of years (not important enough), but as far as I can tell: they break every non-trivial Unity project. The larger the project, the more often you get bitten.īefore I walk away, here's the results of my extensive testing: This is the root cause of many (possibly 'all') data-corruption bugs I've experienced in Unity. Unity's serialization is fundamentally broken, and - according to Unity staff - too difficult/expensive to fix, at least until 'late' Unity5 (they're not going to even try and fix it until the IL2CPP stuff comes in).

I've wasted weeks on this, over the past year. Reddit Logo created by /u/big-ish from /r/redditlogos! Long series.ĬSS created by Sean O'Dowd, Maintained and updated by Louis Hong /u/loolo78 Favors theory over implementation but leaves source in video description. Normally part of a series.Īlmost entirely shader tutorials. Lots of graphics/shader programming tutorials in addition to 'normal' C# tutorials. Using Version Control with Unit圓d (Mercurial) Related SubredditsĬoncise tutorials. Unity Game Engine Syllabus (Getting Started Guide)ĥ0 Tips and Best Practices for Unity (2016 Edition) Lots of professionals hang out there.įreeNode IRC Chatroom Helpful Unit圓D Links Use the chat room if you're new to Unity or have a quick question. Please refer to our Wiki before posting! And be sure to flair your post appropriately. Remember to check out /r/unity2D for any 2D specific questions and conversation! A User Showcase of the Unity Game Engine.

Invalid Serialized File Header Unity