Unity DOTS: Components And Systems 

Among thousands of people that make Unity tutorials, about 95% don't teach anything beyond the basics, and 40% really don't teach anything at all, usually just showing what they've acomplished and being more of an entertainment than actuall advice. You, with the Udemy, RU-vid and blogs, are in the top of those 5% that teach what others don't. Thank you

God Tier channel.

40,000 brick cubes looks like a tornado, or a hive of wasps. i spent fifteen minutes just admiring the beautiful chaos . Tried in object oriented and I was able yo 30 cubes lol, oh gawd the games I'm going to make.

great series so far, I've had no problems following along

Finally a great tutorial! My thoughts on the topic: TLDR; If you're not an experienced programmer in C# and Unity, playing with and learning DOTS is OK because it's the future, but it is advised to wait until DOTS come out of preview phase. Well, DOTS is ok for experimenting, but for me it is still a no go, because it solves one problem (performance), and introduces a tons of other problems. My main point is frustration and development time. Just to name a few problems that makes me climb up the wall: - no real time tweaks in play mode. This is a big problem for me. Given the above tutorial - currently you can't tweak the speed and offsets while in play mode, which leaves you with re-entering play mode A LOT, which brings us to the next problem: - creating a script, compiling and entering play mode takes ages - when 30-40% of development time is waiting for the editor to load, it's not a pleasant experience - learning curve - completely new paradigm - this alone makes it hard to pick up, and also very few good docs and videos exist, mainly because it's in preview stage since 2016(!). Also, the packages that implement this new paradigm, is written by Unity which means you will need to learn how Unity thinks it should work. For every package! (Physics, rendering, etc.) - Lot of editor functionality and built-in features don't work with DOTS yet, or in very early stages, meaning you will have to use workarounds for basic things, or work with preview packages that change a lot, and probably wont work perfectly on all platforms. For example, the Hybrid renderer V2 which supports URP and HDRP basic materials is not even verified for mobile platforms (as of this post)

Awesome, looking forward for the Job tutorial as well !! A_A

great series.1st dots tutorials which make sense.and .please continue this slow style..

I am halfway through this and you have already delivered more practical knowledge than the last six I watched elsewhere. So far, so good!

i know im a little late to the video series, but i'm going to watch and re-watch to soak in as much as i can. Seriously thank you, i will definitely buy any ECS content and recommend it to some as well

it's been said before, but what a great tutorial series. Thank you so much for the great content.

It was a very useful video. Thank you.

The most useful ECS tutorial I have seen so far. Keep it up.

Thanks for the video man! Excellent as usual! Keep the same pace. One note though - in your lambda function you should use in type for Move and Wave data components, since they both are read only.

very nice video! thank you!

Unity needs to hire you to do their tutorials!

just too damn cool

Thanks for tutorial.

Really nice explanation and tutorial. Is it possible to adjust the frequency (or a related parameter), so the sine wave is an event, just a single wave ripple, rather than a repeating sequence of wave ripples?

I'm always impressed with your presentation - what kind of software do you use to edit and highlight your videos and do the animations? :)

Thanks! Please create video how to change behavior of entities on runtime. For example, when presser R half of cubes are red and if pressed W half of cubes rotatea other side

At 2:20 you said the reason why they allowed only non-reference types is because of packing is not totally correct. The actual reason is to cache the components more efficiently.

I know this is an old video but I'll still ask : Wouldn't it make more sense to have the WaveData and speed attached to the spawner object? If I spawn 100 000 entities, why should repeat the same data 100 000 times in memory? Correct me if I'm wrong but the only thing that is unique to each entity is their transform component. Also, just for fun, I tried coding a MakeEntityGrid() function with the MakeEntity() function you showed at the beginning of the video. Everything works great except the renderer stops rendering entities as soon as a part of it is out of viewport instead of all of it. Very funny looking behaviour. Any clue as to why?

so cool videos, everything is well explained step by step, if you have a tipee i will give a tip to you :D

I am doing a feasibility study for a demo and the following is crucial for it to work. Is it possible to have the NavAgent component and the full A* pathfinding in ECS? This is without having to rewrite everything yourself ofc .

I just started to learn ECS. And I would like to know if it is possible to change the value of the material individually for each entity. I usually used Material Property Block. Is there something like this in ECS? And you can please with an example code.

With the 'old' way of thinking, i tried to figure out where or how to add or instantiate a Component System like one would do with MonoBehavior Components. However Systems are always around... what makes me wonder how to restrict a System to a Scene or a single Entity. Is this a thing or is ECS simply not supposed to used that way?

Great tutorials! Really clear and easy to follow, and so good someone is covering all the new features in a decent way! I get an error when i add "ref WaveData waveData" as a third parameter in the For each. Suddenly It doesn't accept the MoveSpeed anymore, and i get told "The type MoveSpeed must be a reference type in order to use it as a parameter. If i remove WaveData error is gone. Anyone knows what's going on?

When initializing component variables I tried setting it up using a ForEach() loop in a OnCreate method in a SystemBase but I think entities don't exist when OnCreate is called. Where should I be initializing component variables? (This is for thousands of cubes so doing it in the Inspector wouldn't make sense)

how would you use the speed as a scriptable object in ecs instead of attaching it to each prefab?

Would it be common to have a project where I combine GameObjects and Entities? For example, have my player as a GameObject since it's easy to work with and I only have a single instance per scene, while have all the AIs as Entities since I might have a lot of them each running AI code. Or should I try to have a "Entity only" architecture if I choose to go with ECS?

Wilmer Lin?? How many accounts do you have? Thanks for this tutorial though.

Does changing the authoring script values during runtime effect things?

How did you enable the quickfix in VSCode?

hi! i need help((( i use unity 2019.4 LTS and entities p4 0.11! and cant add WaveData, GenerateAuthoringComponent not work, i have all time error (cant add script component WaveDTA:Authoring... class cannot be found). i dont have errors in editor, how to do that?

Everything is cool! really! but .. "char" must be pronounced as "chaa" not a "car" :D