Overview - Intro To The Entity Component System And C# Job System 1/5

Рет қаралды 89,935

Күн бұрын

Join our next online user group: ole.unity.com/olug_june27
In this presentation, Unity Evangelist Mike Geig explains how to convert a project from Monobehaviour style code to code which uses the C# Job System and then code which uses that and the Entity Component System and Burst Compiler.

Пікірлер: 49

@0x8080 4 жыл бұрын

No wonder Mike Geig is such a fantastic instructor, he was a university educator! I'm loving the new ECS, I feel much more in control of optimization and actually understanding how my data and functionality are executing. I also really love the Entity Debugger, and how I can view executing code as machine code. Really nice work, thanks to everyone on the Unity team!

@reaktorleak89 5 жыл бұрын

You guys are making history. This looks like the single biggest shift in videogame programming that I've ever seen.

@jonassandstedt 4 жыл бұрын

Well to be fair, its old history. Data Oriented Programing has been used for many years in AAA studios. Buy Unity makes his available for the ”public”.

@sass00n1 2 жыл бұрын

This thing has existed at least 20 years ago, and Unity just "democratized" it. It can also be used by ordinary people other than 3A manufacturers.

@tapesmalad1679 6 жыл бұрын

More of this guy, it really helped me understand, would easily listen to an hour of this...

@batchprogrammer108 6 жыл бұрын

Unity you are the best!!!! Really empowering developers to a whole new level, and you're absolutely free. I commend the Unity team for being such amazing developers, I have been waiting for this feature for a long time. :)

@OtakuDYT 6 жыл бұрын

These really need to be released all at once, else when I view the next one I probably will need to rewatch the first to catch up.

@unity 6 жыл бұрын

We released all 5 together, we only notify subscribers for part 1, the playlist is here: kzbin.info/aero/PLX2vGYjWbI0S4yHZwjDI1boIrYStpBCdN

@OtakuDYT 6 жыл бұрын

Appreciated, thanks!

@federicodebona2842 6 жыл бұрын

I can't wait all the series!!

@m1croN1337 6 жыл бұрын

Thank you so much for these videos. Very informative!

@themastermind5817 6 жыл бұрын

So this is why Unity is creating a Visual Scripting feature! Honestly though, I am happy that Unity is giving this type of features more attention, as compared to terrain and input system. As a programmer, I am more interested in how well the core/scripting API of an engine performs and less in all other things. I have experienced a fair bit of problems that will benefit my abandoned projects.

@MeanYellowMachine 5 жыл бұрын

The Mastermind I'm curious where did you hear that?

@themastermind5817 5 жыл бұрын

Hear what?

@MeanYellowMachine 5 жыл бұрын

The Mastermind that unity is building a visual scripting tool for ecs

@themastermind5817 5 жыл бұрын

They are working on a visual scripting tool. They released a video about it a while ago. But it definitely won't replace ECS. That was just a joke.

@MeanYellowMachine 5 жыл бұрын

The Mastermind hmm just to clarify you're not talking about bolt?also if they do come out with a visual scripting tool wouldn't it be to script in ecs and jobs instead of the old code

@shroomedup 6 жыл бұрын

Thank you so much for this!

@petter9078 6 жыл бұрын

About time!

@tenki330 6 жыл бұрын

they were rendering the video on single core thats why it took so long

@petter9078 6 жыл бұрын

Hahah!

@FrostyChilli 5 жыл бұрын

Other than the learning difficulties and more time spent on developing the same product with ECS, rather than the "classical" why, are there any other disadvantages to using ECS that does things magically for us? Is there something I could do better if I wanted to write multithreaded code and not use ECS? Does ECS limit us in any way?

@tigerspidey123 Жыл бұрын

It's cool that job systems handle ordering, but is the determinism guaranteed on cross platforms? From my tests, i was able to get deterministic results if everything was in burst compiler.

@markd1612 6 жыл бұрын

Would you want to use the ECS and job system for a game that is not intensive at all? I.e is it a good time to get away from using monobehavoirs for data/processing in general?

@angelrdev 6 жыл бұрын

This way is expected to take longer to do things than monobehavior way. I wouldn't go this way for an small game unless it is for learning purposes, which starting with an small game is the best. Anyways, I would wait for later versions.

@themastermind5817 6 жыл бұрын

I've never experienced a performance problem with the 'Classic' way of programming in Unity. In fact, I've written my own fairly complex pathfinding solution in C# and never had a performance problem. I guess this is good enough for games that are highly complex.

@Rennan24 6 жыл бұрын

My 2 cents on this issue is that ECS is something you should learn, even if it is a small game (In fact it's better to start off with a small game to experiment with things) Since ECS is going to be the way Unity ultimately switches to once the amount of people using the "Classic" way switches to ECS. Just look at the way Unity is handling UnityScript, they are completely dropping support of it in the coming years, so unless you want to be left behind on older version of Unity in order to stick to the "Classic" way of doing things, I would take this time to learn ECS. In my experience, Data Oriented Design and ECS makes making games so much easier once you realize how to use it correctly, and this is coming from someone that was taught Object Oriented Programming from the beginning and has been using Unity's "Classic" system for a while. The trick I learned is to think of it as a separation of Data and Behaviour instead of this crazy new technology. MonoBehaviours had both Data (Fields/Properties) and Behaviours (Methods) while ECS separates the two into Data struct containers (Position, Heading) and Systems (MovementSystem) which operates on the Data. TL;DR, It'll take a little bit to get used to this new paradigm of programming but it's better to stay with the trends than to be left behind.

@person8203 6 жыл бұрын

I 2nd what Rennan said. Data oriented design is something to learn and adopt anyway as it's a better way of doing things and will give you a head start for when Unity fully supports ecs and jobs. You don't have to go all in just yet though, start by separating data and logic to get a feel for it. I like to hold data, such as settings, in a scriptable object.

@fordgt500ss 5 жыл бұрын

Is this code available to share with us? It would be great to help learn from.

@shuyongbey8372 5 жыл бұрын

instead of position component, they called it position/transform/rotation/scale proxy to reduce confusion when trying to communicate, eg; "under the transform component add the position component", but they are also other underlying reasons, thats why they are called proxies now. you would also need an extra script for the proxies to work, pls refer to the forum and download the new sample and understand from there.

@Chris-nc3xv 4 жыл бұрын

Impressive stuff! Can the project be download, as it would be helpful to really look at how to convert between the different systems?

@yggdrasilthousandsand3124 6 жыл бұрын

this is the important shit for the next 10 years guys ;-)

@karenhovhannisyan9193 4 жыл бұрын

ECS also excellent architectural solution, and if you understand its easy

@slysynthetic 6 жыл бұрын

Man, I have the same version of unity as you, "2018.1.0b12" but I'm having some serious trouble getting this to work. I really wish you had gone through the process you used to get ECS / Burst Compiler working. That would have been a great first or 6th video.

@slysynthetic 6 жыл бұрын

Nevermind, for anyone else having trouble, Unity has TWO versions of "2018.1.0b12" - lol. Make sure you get the right one.