❗❗ *Caution:* This video was made using an older version of Unity ECS. While the core concepts remain the same, some of the API and workflows have changed as of ECS version 1.0. I would recommend checking out my ECS 1.0 tutorial video for a good overview of the latest standards for Unity’s DOTS: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-IO6_6Y_YUdE.html Once again, the theory behind the concepts of this video are still relevant, however the API has changed. Stay tuned for further updated videos on this subject. Please let me know if you have any questions either here or in our Discord community: tmg.dev/Discord
I have a couple of Questions? If we do not change values of spawncapsuldata then does we need to do setsingleton and does we still need to do getSingleton inside onUpdated and why? if our plane has a collider but plane is in the main scene then does capsule entities which we are spawning have rigidbodies, then does these entites do not stop on plane when they fall insted they pass through them but if we drag the plane inside subscene then phaysics started working
Hello - good questions! The reason we need to do a "Set Singleton" operation is because the singleton component contains a "Random" type. I have another video on this channel going into more detail on the ECS Random type, but basically it generates a random number from an internal seed value, and each time a random number is generated that seed value needs to change so a new random number can be generated each time. Essentially us doing a Set Singleton operation will write that new seed value back to the Random type. Then we need to "Get Singleton" every frame to be sure we have the latest data for the Random seed value. As for the physics question - when a collider is in the main scene, it uses the default Unity physics engine and when a collider is in a subscene it will use the DOTS physics package. Colliders in each of these physics systems will only be allowed to collide with other colliders in the same physics system. Essentially yes, that means that a plane in the main scene will not stop colliders in the subscene from falling through. Hope that helps!!
Is the SpawnCapsuleData data component a separate script or a built in ECS variable? If so, can you start including all scripts that are a part of what you are doing? These videos helpful but I am trying to add to what I learned off other videos where I establish a struct that derives from :IComponentData. From those tutorials they make it very clear, but with this I am unsure of where the SpawnCapsuleData is coming from.
Yes, SpawnCapsuleData is an IComponentData I created. And I do include all relevant project files and code from my tutorial videos in the description! The first link gets you all the project files and the second one is a link to a GitHub gist page with all relevant code. Hope that helps you understand how this is all working 😊
@@TurboMakesGames Well then.. I almost always look there first to see if there are files, but for some reason I didn't this time. I guess that is on me, lol.
Pretty surprised to know that they actually developed an API for Singleton specifically since it's such highly disregarded pattern in high level programming. What exact real-world use case would you recommend for this? I'm thinking of using this for global systems such as a day-night cycle, do you think it'd work?
Although it is highly disregarded in high level programming, there is no denying its usefulness in game development - sure there are alternatives but it is still widely used in game development. Funny that you bring up a day-night cycle as a real world use case - Unity released some ECS best practice guides and the example they give for the singleton pattern is a system that runs alongside a day-night cycle. In their example, during the daytime all sunflower entities point towards the sun as it moves across the sky during the day and at night the system does not run as there is no sun to point at.
Firstly the singletons in ECS are not really singletons in the traditional sense. ECS is not Object Oriented, a singleton in ECS is data that we ensure there is only one instance of within the context of the world. A singleton in OOP however is a class which ensure there is only one instance of in the entire program. A true singleton is global, and ECS singleton however is scoped to a world. Singleton is a bit of a misnomer here, really these are world state data.
@@TurboMakesGames Question - How is the singleton entity created, and what prevents multiple singleton entities from being created? Also where are the ECS best practice guides published?
@@TurboMakesGames Thanks for replying and yep that was exactly my thoughts. I'm working on an ecosystem for a DOTS game and my ideas are animals behaving differently depending on the day/night cycle. I'm gonna look up this best practices article later.
![How to Use SINGLETONS in Unity ECS - Unity DOTS Tutorial [ECS Ver. 0.17]](/img/logo.svg){kind=logo}
