unity store scene camera in scriptableobject

Richard Fine talks about it too in the video. STOP, DON'T DO THAT ANYMORE ! You have so many chances to get issues and time wasting to solve them with this kind of patterns. We could use a prefab that store the asset and put it in the scene. but if I want to use the same script in another project, you'll need to change that path another time. So, what can we do ? Use Resources.Load() ? Nope, we still need to write a path, and change it when the asset is moved. It means that the method Resources.FindObjectsOfTypeAll() works only for loaded resources, as explained in documentation :Ĭlick to expand.And resources in Resources folder are obviously not loaded 'by default'. Note that if you build the game and start it, you'll see 'Default' in the GUI box. Go to your Unity project, just click on the Demo Config asset. Now you could tell me 'but why the fuuf did it work the first time ?'. The Reload-proof singleton patterns is an answer to that. And if you're a regular consumer of singletons, you must have experienced null ref errors at hot reload. In the video, Richard Fine explains that the problem is about serialization processes when you reload your project with statics variables initialized at runtime. and that's why you see the 'default' DemoConfig asset name. It means that the object has to be loaded once, to be found in resources. But, it's not really the objective : this pattern is to make Reload-proof singletons. In forums, I saw that many people thought that this pattern is to make ScriptableObject singletons in their project resources. So, what's in the GUI Box now ? Are you still smiling ? In fact, the Reload-proof singleton pattern is not designed for this. Don't click anywhere but on the Play button. Save your scene, close Unity and reopen your project. Great, GUILog can access to the DemoConfig asset in project folder without referencing it in its properties or using a path to that resource.īut it's not that easy. You should see a little GUI box in the top-left corner of the Game View with the message ' Config : Demo Config'. Attach the GUILogger to the default 'Main Camera' (or anything else in the scene, of course).Create a 'Demo Config' asset in it (Assets > Create > Demo Config).Make a 'Resources' folder in yout project Assets.The same occurs in instances of scripts if they are derived from MonoBehaviour or ScriptableObject, which are both derived from UnityEngine.Object.

When fields reference something that is a UnityEngine.Object-derived class, such as public Camera m圜amera, Unity serializes an actual reference to the camera UnityEngine.Object. Unity serializes custom classes “inline” because their data becomes part of the complete serialization data for the MonoBehaviour or ScriptableObject they are used in. For more information, see documentation on ISerializationCallbackReceiver. This prevents Unity from creating multiple objects from object references. Instead, use ISerializationCallbackReceiver to serialize them manually. When you need to serialize a complex object graph with references, do not let Unity automatically serialize the objects. Then, when Unity deserializes the fields, they contain different distinct objects with identical data.

If you store a reference to an instance of a custom class in several different fields, they become separate objects when serialized. With custom classes that are not derived from UnityEngine.Object Unity serializes them inline by value, similar to the way it serializes structs. When might the serializer behave unexpectedly? */) Įach in their own script files with matching name (that part is very important for the serializer).Īnd then you would create instance of these via the Assets -> right click -> Create -> 'Conditional' for example and reference it into the according slots.Īlso note that these are now re-usable and you can simply reference the same item in various places, something that wasn't possible if you use a normal serializable class due to If((bool)condition.Execute()) trueBranch.Execute() Public Command condition, trueBranch, falseBranch Where Execute() is to perform the command at runtime, and Inspect() is to draw the inspector GUIs.Įvery solid type of command would be a derived class of Command, e.g. This one is only for illustrating the problem.Ĭommand.Inspect() would be called by a CustomEditor of CommandCarrier. There are several carrier classes in the real project, I've managed to express all executable instruction units-expressions, statements, control blocks-with a common abstract base class Command. Screenshot of command editor in unity inspector Hi fellow game developers, I'm working on a Unity project that allows level designer to edit instructions to scene elements of how they should act to events.

Unity store scene camera in scriptableobject